User Story Calibration
User stories are prioritized during at least two ceremonies in the life of a project. The feature backlog prioritization session allows the product owner to work with team members to identify dependencies within a scrum project, rank accordingly, adjust and manage risks and determine which set of features will be recommended for upcoming sprints. The sprint planning meeting takes the detail in the user story and evaluates for completeness without inhibiting the ability of the self-organising scrum team to develop state of the art code.
With multiple scrums evaluating features and subsequent user stories it is important to establish calibration sessions to manage user stories across the teams. Duplication can be quickly identified and eliminated. Also, dependencies are highlighted and user stories can be delivered in the most efficient manner possible. Technical debt can be minimized by evaluating areas where rework can be eliminated.
Chief Product Owners and Scrum Masters will be responsible for guiding the discussion between multiple scrum teams. Evaluating user stories in a holistic manner and with some facilitation of oversight, will enable multiple scrum teams to deliver the highest priority features and minimize risks and technical debt.
Recommended Further Reading
The following materials may assist you in order to get the most out of this course: