Creating Tasks from User Stories
Once user stories have been broken down and clarified, the team can proceed with task creation. The developers have the expertise to know what are the best ways to build and test, so the Product Owner can trust the team in coming up with the tasks needed to complete the user stories. The Product Owner can help verify if the development team understood the requirements well and clarify anything if needed.
Because Agile estimation takes work and effort, it’s important for everyone in the team to discuss the tasks needed for user stories. The different roles in the team give different insights on how a feature can be developed – QA engineers can derive from their testing experience, designers can give their point of view, and developers can give technical inputs. Knowing what to do for each user story helps the team understand the effort it would take to develop it, thus allowing teams to give better estimates. This also helps the Product Owner prioritize user stories better within the Product Backlog and Sprint Backlog.
It’s up to the scrum team how they’re going to estimate the work they need to do. Some teams estimate using time formats, such as hours, days, or weeks. Another way to estimate is by using story points, which score the relative effort needed to finish the work with a Fibonacci-like sequence (1, 2, 3, 5, 8, 13, 21, etc.). Typically, teams would take a user story, have a short discussion about it, then individually and mentally form estimates.
Recommended Further Reading
The following materials may assist you in order to get the most out of this course: