Tasks represent work that must be done by the Scrum team. Whether it is a new development, testing, or meetings, tasks are what the team must do to finish the project. While user stories come from the perspective of the stakeholders, tasks are from the perspective of the Scrum team. Any single task might not result in any functional change to the product. New features often require several tasks to be properly implemented.
Breaking Down and Refining User Stories
Another way to look at tasks and user stories is to determine how many people will be working on them. User stories may involve several people and roles to complete. Analysts look at the technical requirements, while developers write the code, and QA technicians make sure the feature works as designed. Tasks are the responsibility of a single person or role. Each part of the user story can be broken down into a distinct task.
Developer Role in Creating Tasks
With developers handling only tasks for writing and maintaining code, it may seem like they have no part in creating the tasks. However, the developer role has expertise that no other role on a Scrum team has. They can be valuable in making sure tasks are created properly, with logical divisions. The entire process of creating tasks benefits from the input of developers and other roles of the Scrum team.
Recommended Further Reading
The following materials may assist you in order to get the most out of this course: