Refinement
Meeting to discuss product backlog items
Favara Vincenzo
About me
Refinement
Backlog grooming is the pre-planning
and it should take 5 or 10% of the sprint
Prioritise backlog assigning user value
score (useful for Matrix)
It is not a formal ceremony of the Scrum
process.
Groomed Scrum backlog helps to
streamline sprint planning meetings to
avoid stretching them for hours
Refinement standard Actions
What should I do on grooming meeting?
Splitting big items into smaller ones
Rewriting backlog items to be more expressive
Deleting obsolete or no more need items
Successful grooming leads to the effective sprint planning
Saving time for the devs for further discussion during sprint
1
2
3
4
5
How can it improve?
Simple rules to remember to not avoid
User Story
User Stories should meet INVEST criteria:
● Independent
● Negotiable
● Valuable
● Estimable
● Small
● Testable
You always must answer what value this
feature brings to end users and product
User Stories tips
What we need from User stories:
● What’s the main user action?
● Describe an intention, not a
feature
● Keep it short, not tech details
● Avoid describing UI
You always must answer what value this
feature brings to end users and product
Team
can discuss
and put comments
to describe
and add
other relevant info
Prioritization matrix
It helps for unaspected decisions during sprint
Should be easy collocating each
US in the correct quadrant:
● Pre-labeling US with a
predefined user value
● Use estimated value in
planning to have always
visible quadrant result
"It’s not a best practice, but sometime
happens!”
What you should do is prepare team with
all required info to let they estimate USs
— Someone smart
To estimate or not to estimate?
Estimation is part of grooming?
Thank You!
Favara Vincenzo

Scrum refinement

  • 1.
    Refinement Meeting to discussproduct backlog items Favara Vincenzo
  • 2.
    About me Refinement Backlog groomingis the pre-planning and it should take 5 or 10% of the sprint Prioritise backlog assigning user value score (useful for Matrix) It is not a formal ceremony of the Scrum process. Groomed Scrum backlog helps to streamline sprint planning meetings to avoid stretching them for hours
  • 3.
    Refinement standard Actions Whatshould I do on grooming meeting? Splitting big items into smaller ones Rewriting backlog items to be more expressive Deleting obsolete or no more need items Successful grooming leads to the effective sprint planning Saving time for the devs for further discussion during sprint 1 2 3 4 5
  • 4.
    How can itimprove? Simple rules to remember to not avoid
  • 5.
    User Story User Storiesshould meet INVEST criteria: ● Independent ● Negotiable ● Valuable ● Estimable ● Small ● Testable You always must answer what value this feature brings to end users and product
  • 6.
    User Stories tips Whatwe need from User stories: ● What’s the main user action? ● Describe an intention, not a feature ● Keep it short, not tech details ● Avoid describing UI You always must answer what value this feature brings to end users and product Team can discuss and put comments to describe and add other relevant info
  • 7.
    Prioritization matrix It helpsfor unaspected decisions during sprint Should be easy collocating each US in the correct quadrant: ● Pre-labeling US with a predefined user value ● Use estimated value in planning to have always visible quadrant result
  • 8.
    "It’s not abest practice, but sometime happens!” What you should do is prepare team with all required info to let they estimate USs — Someone smart To estimate or not to estimate? Estimation is part of grooming?
  • 9.