Committing User Stories
The first step in the creation of tasks is committing user stories. As the product owner researches what stakeholders want, they add user stories to the product backlog. Once the product backlog has all the user stories that the stakeholders want, they must be prioritized.
Before the sprint begins, user stories are committed to a sprint. This locks down an estimate for which user stories the Scrum team believes they can finish before the sprint ends.
What does the developer role get from the committing stage? Being present in meetings about committing user stories gives developers a heads up about what they will be working on.
This gives them the opportunity to research the features, and analyze what needs to be done. When tasks are broken out and estimated, developers will need to know details. Getting an advance notice from the committing process allows developers to anticipate the next steps.
Recommended Further Reading
The following materials may assist you in order to get the most out of this course: