Product Backlog Prioritization
The backlog ceremony should have specific goals and objectives in mind that are introduced by the Product Owner and agreed to by all participants. The goal may be to refine the features and divide the deliverables into smaller epics and subsequent user stories. Prioritization takes place and during effective ceremonies, dependencies between features are highlighted. Identification of dependencies and risks can minimize technical debt that may negatively impact the Return on Investment (ROI) of a project. The artifacts used for the product backlog prioritization ceremony are the product backlog and estimation tools (i.e., story points, bucket system, or t-shirt sizes).
The Scrum Master will facilitate the ceremony by reminding all participants what the initial objectives are and facilitating feedback on agreement by the team members. The Product Owner should be the owner of the goals and objectives of the inputs having been received from the project owner and key stakeholders. If there are questions on any of these items, it is important that the Scrum Master facilitate team member understanding before moving forward with breakdown and estimation of features for delivery. The Product Owner then outlines each feature with a description and objective of the feature in the larger product design. Epics are then defined in order to group similar high-level deliverables together. User stories are high-level definitions of requirements under each epic.
Higher level estimates are defined based on the user story definitions. The reason that these estimates are high level relates to the fact that team members are asked to use estimation techniques such as Fibonnaci sequencing or relative estimation with only the title and description of a user story available. While not a detailed estimate, this will allow the team to refine the prioritization and scope of the effort. The Scrum Master is the facilitator to guide the team in discussions where scope, priorities, and dependencies may need to be adjusted. Early release planning is managed here and frequently throughout the life of a project as the product backlog is prioritized.
Approval of the estimates and the impact on the scope will be the responsibility of the Product Owner as the stakeholder liaison.
Recommended Further Reading
The following materials may assist you in order to get the most out of this course: