Backlog Refinement Process. Carolina Graffe Jorge Fernández

Transcription

1 Backlog Refinement Process Carolina Graffe Jorge Fernández

2 Product Management

3 El Equipo Scrum

4

5 Backlog Refinement Process Backlog: cola de características que el equipo Scrum mantiene. Se espera que cambie NO es un documento de requerimientos Contiene Historias de Usuario que se van detallando y priorizando Backlog Grooming Significa esa actividad de recorte y priorización de historias de usuario

6 Un Poco de Historia 2005: primera vez que se usa el término Backlog Grooming 2008: Comienzan las descripciones al respecto y se vuelve Story Timer 2011: La práctica se hace hace oficial! 2013: Cambia de nombre a Backlog Refinement Process NO confundir con: Backlog Improvement Process!

7 Product Backlog Refinement Product Owner con Stakeholders Product Owner y Backlog Product Owner, Dev Team, Scrum Master (Backlog Refinement Meeting) Product Owner Priorizar Se refina el producto hasta obtener un entregable.

8 Backlog Refinement Meeting The team (or part of the team including the product owner) meet regularly to "groom the product backlog", in a formal or informal meeting which can lead to any of the following: removing user stories that no longer appear relevant creating new user stories in response to newly discovered needs re-assessing the relative priority of stories assigning estimates to stories which have yet to receive one correcting estimates in light of newly discovered information splitting user stories which are high priority but too coarse grained to fit in an upcoming iteration

9 How can you hold an effective Product Backlog grooming session? Have a goal in mind in each of these sessions the Product Owner should come in saying, Here is what I would like to accomplish today. This can be an agreed-upon goal with the team, but the point is the goal should be set before the meeting starts. Wandering into a backlog grooming session saying, Well, ummm what do we want to talk about today? is a guarantee that time will be wasted.

10 Schedule the session to support and improve the next Sprint Planning meeting a good backlog grooming session leaves everyone involved feeling familiar with the product backlog, gives them a clear understanding of the goals for the next sprint, and means they can hit the ground running in the Sprint Planning meeting. So schedule backlog grooming sessions to precede the next Sprint Planning by at least a couple of days. Limit chicken participation known as chickens in Scrum, stakeholders can be effective participants in a backlog grooming session. But limit their numbers. If you have, for example, 10 stakeholders from whom you want to gather feedback, get it from them in a series of 2 3 meetings, not one big one. Remember, stakeholders often do not understand the rules of Scrum as well as the team, Product Owner and ScrumMaster do. They often do not have good Scrum manners, and you may find a large group of them can quickly take over your meeting, making it chaotic and less effective.

11 INVEST principles Independent User stories are the lowest level of functional decomposition Negotiable User stories are not detailed specification. They are not a precise guide for how we are going to build the product, or even what we are going to build. Valuable User stories are written in the language of the business. They represent an increment of product that can be demonstrated to a potential customer of the system.

12 INVEST Principles Estimateable This attribute implies that the team has enough knowledge about how the user story will be developed (and tested) that they can provide a high-level estimate for how long the user story will take to implement. Small You might also express this attribute as sized appropriately. The idea is that user stories are intended to be small enough that a team can do several within the course of a two-week sprint.

13 INVEST Scale The INVEST scale is a simple yet effective measure of user story feasibility in the current sprint, based on the INVEST principle. Here's what to do: List the business requirements or the user stories in a tabular fashion. Put the INVEST columns next to each story. Have the product owner, or anyone who has business knowledge (with decision-making capabilities), fill out the matrix. Create a rule for a cutoff total to determine whether to accept the user story as is. A score of <18 is not an acceptable independent user story. Break it down further!

14 INVEST Scale INVEST Scale Definitely not 2 - Not sure 3 - Maybe 4 - Looks like / Kind of 5 - Definitely

15 Benefits of the INVEST scale Gets the product owner to think through the entire project Product owner will be ahead of the game Easier to get buy-in from stakeholders reluctant to venture into new projects Simplifies the "monster" project into small, "thinkable" deliverables Unknowns can be converted into knowns

16 Actividad programada Backlog Refinement Meeting..

17 Material para revisar How to improve Scrum Backlog Refinement: v=azmx6kfw8sa Backlog Definition: Backlog Grooming: Agile Product Ownership in a nutshell: se/2012/10/25/henrikkniberg/agile-product-ownership-in-a-nutshell Backlog Grooming: Why do Product Backlog Grooming: com/why+do+product+backlog+grooming%3f