diff --git a/rules/backlog-refinement-meeting/rule.md b/rules/backlog-refinement-meeting/rule.md index 4fc7c7a906b..9e3f81f7706 100644 --- a/rules/backlog-refinement-meeting/rule.md +++ b/rules/backlog-refinement-meeting/rule.md @@ -20,14 +20,8 @@ When a Scrum Team meets for Sprint Planning, they want to plan out the next week - **Potential Outcome 1:** Poorly defined PBIs being added to the Sprint causing problems with shaky estimates and later down the track when developers are unclear about the PBI details and how to implement them. - **Potential Outcome 2:** A lengthy Sprint Planning meeting with only a few people engaged. - - - - - - ## The Solution - Product Backlog Refinement meetings A Product Backlog Refinement meeting can help address these issues. In this meeting, the Tech Lead and another developer refine all the PBIs. This process involves refining the PBIs in the backlog and adding a "Ready" tag or status when the PBI has met the [Definition of Ready](have-a-definition-of-ready) @@ -56,6 +50,7 @@ Agenda - Call in the Product Owner to double check ::: +::: ## Benefits of Product Backlog Refinement