Prioritized - What should you work on next? The backlog should have highest priority items at the top, lowest priority items at the bottom. As new discoveries are made over time, include them in the backlog or its product risks becoming obsolete. It should be a fast-flowing river where new ideas turn into completed work, not a swamp where idle ideas sit and slowly decay. You can check your estimate against the actual, thereby improving future planning.Įmergent - The product backlog is a dynamic document of planned work that reflects real-time needs and priorities of the business. Estimating also offers a point of comparison. (We want to extract maximize value from a minimal amount of work). By estimating backlog items, we have an understanding of the cost to implement them, which is must-have information for prioritization. ![]() Common estimates are story points, hours, even T-shirt sizes (small, medium, large, x-large). It also ensures the development team has all the detail they need to successfully complete the items in their next sprint.Įstimated - Most backlog items should be estimated. This prevents waste (and confusion) that results from spending too much time breaking down backlog items that are irrelevant to an upcoming sprint. The acronym D.E.E.P., coined by long-time Agile advocate Roman Pichler, is commonly used to describe the ideal, well-managed backlog.ĭetailed Appropriately - Upcoming, high-priority backlog items should have more detail than distant, low-priority items. Whatever you do, make sure it’s D.E.E.P.!ĭetailed Appropriately, Estimated, Emergent, Prioritized Building a D.E.E.P. They also may include or adjust estimates for user stories. They may add user stories, split large user stories, or change priority of existing user stories. During these meetings, the product owner, in coordination with others, will look at existing user stories and remove those that are no longer relevant. ![]() But it’s common practice to hold meetings with relevant stakeholders on a regular cadence (every second week, for example). How do You Perform Product Backlog Grooming - Best Practicesīacklog grooming is an ongoing process. These stakeholders may include: business executives, the development team, and others, such as the scrum master. The process of refining the backlog is mostly managed by the product owner (in an Agile Scrum environment), who owns the backlog with the assistance of relevant stakeholders. ![]() It helps make sure that the team is completing the most important work, which improves both team motivation (“My work is important!”) and the long-term sustainability of the business. It ensures a relevant connection between what the market expects from your product and what your organization actually plans to deliver. Regular grooming is absolutely essential.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |