Blog: What Is Product Backlog Grooming (Refinement) and How Long Should It Take? This is the second blog post in the “How Much Time Should Each Scrum Practice and Meeting Take” series. This posting focuses on product backlog grooming. Product backlog grooming (sometimes called product backlog refinement) refers to a set of three main activities: creating and refining product backlog items (PBIs), estimating PBIs, and prioritizing PBIs. How much time teams should budget for product backlog grooming (refinement) As a general rule, the development team should allocate between 5 percent to 10 percent of its time each sprint to assisting the product owner with grooming activities. The team will use this time to help create or review emergent product backlog items as well as progressively refine larger items into smaller items.
Certified Scrum Product Owner Certified Scrum Product Owners® have been taught the Scrum terminology, practices, and principles that enable them to fulfill the role of Product Owner on a Scrum team. CSPOs are typically the individuals who are closest to the "business side" of the project. They are charged by the organization to "get the product out" and are expected to do the best possible job of satisfying all the stakeholders. CSPOs maintain the product backlog and ensure that everyone knows the priorities.
Scrum poster walkthrough Earlier this year, I released the complimentary Scrum Poster with the goal to give Scrum Teams around the world a medium to see the Scrum Guide in visual form. Beside the guide itself, many text documents and presentations have flooded the various platforms and I felt a picture can express so much more. I also felt transparency was best supported by shipping the actual paper version so show support of Scrum in a team area.
Scrum Backlog Grooming Posted by admin under Scrum Basics While backlog refinement (also called grooming) was not originally a formal meeting in the Scrum framework, Ken Schwaber, who founded Scrum, advises teams to dedicate five percent of every sprint to this activity. As with Scrum’s other meetings, the grooming should take place at the same time and place and for the same duration each sprint. Avoid the Pandemic: Save the World with Scrum Can your Scrum team save the world? Try this team-building exercise with the cooperative board game Pandemic. Diagnosis: A high-performing team One of the key responsibilities of the ScrumMaster is providing the necessary leadership to form a group of individuals into a high-performing team. Such a team consists of people who work together to attain a common goal and are able to achieve extraordinary results.
The Agile Museum I’ve been teaching the class Professional Scrum with Kanban (PSK) for the last year now and I strongly believe parts of its content will send some of our current practices and books to the Agile museum. Through the help of the cycle time scatter plot diagram, I believe our decks of poker planning will end up in the Agile museum. Between our actual estimation techniques and the #noestimate movement, I believe the Kanban (or flow) metrics offer a historical perspective based on actual data. Kanban metrics such as throughput avoids the confusion about story points and velocity when we explain these techniques to our customer.
Product Backlog Refinement Ongoing Product Backlog Refinement (PBR) is needed within each Sprint to refine items to be ready for future Sprints. Key activities of PBR are (1) splitting big items, (2) clarifying items until ready for implementation without further “what” questions, and (3) estimating size, “value”, risks, and so forth. In short form: split, clarify, estimate.
Coaching Scrum Teams Through Conflict Navigation and Effective Communication Strategies Internal conflict can have a major impact on Scrum team dynamics and cohesion. As a ScrumMaster, learning how to deal with these conflicts can become a major part of your everyday job. On the other hand, conflict is natural in any vibrant Scrum team. A fear of conflict in a Scrum team is not a good sign and can signify team apathy. Product Backlog Refinement - Scrum Inc A crucial guideline in Scrum is that five to ten percent of every Sprint must be dedicated to Backlog Refinement. As the slides illustrate, this includes:detailed requirements analysissplitting large items into smaller ones (epics to User Stories)estimation of new itemsre-estimation of existing items Product Backlog Refinement is not for PBIs selected for the current Sprint; it is for items in future Sprints. A good practice is to have at least two Sprints worth of work ready to go in the Product Backlog. Sprint Planning becomes relatively simple because the Product Owner and Scrum Team start the planning with a clear, well analyzed and carefully Estimated set of stories.
Task: Refine Product Backlog Synopsis The Product Owner reviews the Product Vision with the team and they update the Product Vision, as needed. The team then refines the Product Backlog to ensure that they all have an up-to-date ranked list on which to base their Release Planning. Value Product Backlog refinement ensures that the team focuses on capabilities that provide the most value for the investment.