Difference between revisions of "Product Backlog Refinement (grooming) Workshop"
(New page: == Overview == 1 day In Scrum, 5-10% of each Sprint should be spent on refining the Product Backlog, with the Team and Product Owner. This is ideally done in a focused workshop. The activ...) |
|||
(3 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
== Overview == | == Overview == | ||
− | 1 day | + | 1-2 days (or 0.5 day, if a 1-week mini-Sprint) |
− | In Scrum, 5-10% of each Sprint should be spent on refining the Product Backlog, with the Team and Product Owner. This is ideally done in a focused workshop. The activities include: | + | In Scrum, 5-10% of each Sprint should be spent on refining (or 'grooming') the Product Backlog, with the Team and Product Owner. This is ideally done in a focused workshop. It is often done near the middle of each Sprint. |
+ | |||
+ | The activities include: | ||
* splitting large items (e.g., user stories) | * splitting large items (e.g., user stories) | ||
Line 8: | Line 10: | ||
* re-estimation of the Release Backlog (a portion of the Product Backlog) | * re-estimation of the Release Backlog (a portion of the Product Backlog) | ||
− | |||
<br> | <br> | ||
<br> | <br> | ||
− | Learning how to do | + | Learning how to do Product Backlog refinement requires coaching-while-doing; it can't be effectively learnt in a classroom setting. In this workshop, the coach will facilitate the activities for a real product, while educating. |
− | |||
== Methods of Education == | == Methods of Education == | ||
Line 19: | Line 19: | ||
== Audience == | == Audience == | ||
− | + | For 1 product group -- teams and Product Owner. | |
Line 31: | Line 31: | ||
== Objectives == | == Objectives == | ||
− | This is not a course per se, but a product-specific | + | This is not a course per se, but a product-specific workshop to refine the Product Backlog. Learning objectives include (but are not limited to): |
* agile estimating and planning | * agile estimating and planning | ||
* modeling with user stories | * modeling with user stories | ||
− | * splitting large user stories | + | * splitting large items (e.g., user stories) |
− | + | * Scrum Product Backlog refinement | |
− | |||
− | * Scrum Product Backlog | ||
* prioritization in Scrum | * prioritization in Scrum | ||
+ | * acceptance test-driven development | ||
+ | * specifications by example, expressed usually in tables | ||
* much more | * much more | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
== Maximum Participants == | == Maximum Participants == | ||
− | + | For 1 product group -- teams and Product Owner. Up to 3 teams may participate if the workshop room is large enough. | |
== Environment - Room, Tools, Texts == | == Environment - Room, Tools, Texts == | ||
− | Read this: [[ | + | Read this: [[Workshop Environment - PBR]] |
'''Text and Notes''' | '''Text and Notes''' | ||
* a useful pre-read is [http://www.scrumprimer.com/ The Scrum Primer] | * a useful pre-read is [http://www.scrumprimer.com/ The Scrum Primer] |
Latest revision as of 06:44, 5 September 2013
Contents
Overview
1-2 days (or 0.5 day, if a 1-week mini-Sprint)
In Scrum, 5-10% of each Sprint should be spent on refining (or 'grooming') the Product Backlog, with the Team and Product Owner. This is ideally done in a focused workshop. It is often done near the middle of each Sprint.
The activities include:
- splitting large items (e.g., user stories)
- detailed analysis of items (e.g., using acceptance test-driven development techniques, among others)
- re-estimation of the Release Backlog (a portion of the Product Backlog)
Learning how to do Product Backlog refinement requires coaching-while-doing; it can't be effectively learnt in a classroom setting. In this workshop, the coach will facilitate the activities for a real product, while educating.
Methods of Education
primarily workshop exercises & coaching; some discussion, presentation, Q&A
Audience
For 1 product group -- teams and Product Owner.
Level
This is an immersive workshop. No prior knowledge is required, but the experiences and knowledge will extend from introductory to intermediate or advanced.
Prerequisites
none.
Objectives
This is not a course per se, but a product-specific workshop to refine the Product Backlog. Learning objectives include (but are not limited to):
- agile estimating and planning
- modeling with user stories
- splitting large items (e.g., user stories)
- Scrum Product Backlog refinement
- prioritization in Scrum
- acceptance test-driven development
- specifications by example, expressed usually in tables
- much more
Maximum Participants
For 1 product group -- teams and Product Owner. Up to 3 teams may participate if the workshop room is large enough.
Environment - Room, Tools, Texts
Read this: Workshop Environment - PBR
Text and Notes
- a useful pre-read is The Scrum Primer