Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix email template #6214

Closed
wants to merge 1 commit into from
Closed

Fix email template #6214

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 1 addition & 6 deletions rules/backlog-refinement-meeting/rule.md
View file
Open in desktop
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
Loading