The Product Backlog Refinement sometimes also called Grooming is an activity that typically takes part one week after the Sprint Planning in a two weeks sprint. In longer sprints it takes place mostly half way through the sprint.
But what is PBR? What do we have the Product Owner (PO) for? Isn’t it his job to detail out all information about what to implement and then officially hand that over at the sprint planning so the team can start doing their magic and show their results in the Sprint Review?
For those of you new to Agile and Scrum: the truth is no longer in the documents, it’s now shared understanding that exists in all the heads of Customer, PO and Scrum Team.
The PBR has 3 main purposes which you can see in pink in the picture:
- Clarify the backlog items so everyone has the same understanding
- Splitting up too big stories/features
- Estimation as preparation of the sprint planning and also check for the size of the product backlog items
A good PBR has some pre-requisites
- the PO prepares the Backlog
- Details out stories with the help of the customer keeping mostly the Customer and Business Value in focus
- Prioritises the backlog according to the Vision and Roadmap
- Tidies up stories/items that are no longer needed or deprecated
- splitting down features into stories
- talking the resulting backlog through with the customer to make sure Business and Customer value are understood right and all use cases and scenarios have been captured
Doing the PBR
- the PBR is a join effort of
- the cross functional Team (including everyone who is working on the project)
- Scrum Master to help with the facilitation
- The whole above mentioned group together starts going through all items to:
- identify big or vaguely analysed items
- analyse/split items
- Doing the PBR is best done with hands on material like cards, post-its, flip-charts, whiteboards. Try to avoid using a computer and staring with 5-8 people on a screen, this will cause another form of “death by powerpoint”.
Ultimately the outcomes of the PBR is learning and shared understanding by talking to each other.
It is NOT a desired outcome to have user stories that have extremely specified information in form of pages and pages of text. This would cause one of the lean wastes of “handover”.