Skip to content

Commit

Permalink
Fix email template
Browse files Browse the repository at this point in the history
  • Loading branch information
bradystroud authored Aug 1, 2023
1 parent a157669 commit 2dd4376
Showing 1 changed file with 1 addition and 6 deletions.
7 changes: 1 addition & 6 deletions rules/backlog-refinement-meeting/rule.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.



<!--endintro-->





## 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)
Expand Down Expand Up @@ -56,6 +50,7 @@ Agenda
- Call in the Product Owner to double check

:::
:::

## Benefits of Product Backlog Refinement

Expand Down

0 comments on commit 2dd4376

Please sign in to comment.