how_do_we_run_our_first_iteration_planning_or_sprint_planning_event
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
how_do_we_run_our_first_sprint_planning_meeting [2015/11/17 13:09] – [Moderation] hpsamios | how_do_we_run_our_first_iteration_planning_or_sprint_planning_event [2022/08/10 08:57] (current) – hans | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== How Do We Run Our First Sprint Planning | + | ====== How Do We Run Our First Iteration (Sprint) Planning |
+ | The purpose of Iteration (Sprint) Planning is to allow the Team to commit to what they can deliver in the next Iteration (Sprint) - the committed Iteration (Sprint) Backlog. | ||
- | ====== Premise ====== | + | Iteration (Sprint) Planning occurs at the beginning of the Iteration (Sprint), after you have completed the Iteration Demo (Sprint Review) and Retrospective of the current Iteration (Sprint) (i.e. the Iteration Demo (Sprint Review) and Iteration (Sprint) Retrospective are an input to the Iteration (Sprint) Planning). Note that there is typically no gap between the end of one Iteration (Sprint) and the start of the next Iteration (Sprint). (See [[what_events_should_we_put_in_place_for_iterations_or_sprints|What Events Should We Put in Place For Iterations (Sprints)? |
- | The purpose of Sprint Planning is to allow the team to commit to what they can deliver in the next Sprint - the committed Sprint Backlog. | + | ====== Structure ====== |
+ | |||
+ | ===== Who ===== | ||
- | Sprint Planning occurs at the beginning of the (next) Sprint, after you have completed the Sprint Review and Retrospective of the current Sprint (i.e. the Review and Retrospective are an input to the Planning). Note that there is typically no gap between the end of one Sprint | + | Scrum Team - Team, Scrum Master, Product Owner and other stakeholders as required. |
- | Sprint Planning may be divided into two sessions, be conducted as one session, or occur as a series of shorter incremental sessions. Typically, Sprint Planning is viewed as having two parts: | + | ===== Duration ===== |
- | * Sprint Planning 1 - Used by the Team to reach common agreement on Product Backlog items with the highest priority (including their Conditions of Satisfaction), | + | Maximum 2 hours for a 2 week sprint |
- | * Sprint Planning 2 – used by Teams to determine in detail how they will make and meet their commitment for the Sprint | + | |
- | By the end of Sprint Planning 2, all Team members should be confident that the worked committed to can be completed by the end of the Sprint or have identified the risks associated with any items about which there are doubts. | + | ===== Summary Agenda |
- | ====== Background ====== | + | |
- | The team should use the data they have to help them make good commitments. For example, during | + | * Review Team Capacity |
+ | * Review Team backlog | ||
+ | * Select stories that will be completed by the end of the Iteration (Sprint) i.e. sum of estimates is less than Capacity | ||
+ | * Summarize as Iteration (Sprint) Goals | ||
+ | * Commit | ||
- | Similarly when the team gets to Sprint Planning 2, comparing a running total of the estimated hours on the tasks to a total team capacity for planning purposes will help the team understand what is truly possible to commit to. | + | ====== Result ====== |
- | ====== | + | A committed set of Iteration (Sprint) goals plus a set of backlog items that are candidates for delivery in the next Iteration (Sprint) (or Iteration), sometimes called the Iteration (Sprint) Backlog. |
- | **Purpose: | + | ====== Sample Agenda ====== |
- | **Who:** Scrum Team - Team, Scrum Master, Product Owner and other stakeholders as required. | + | |
+ | | ||
+ | * If Team does not have a history base this on the following calculation | ||
+ | * For a 10 day Iteration, give each person 8 points = 10-2 where the 2 represents one day for Iteration Planning, one day for Iteration Review and Retrospective | ||
+ | * Subtract out the Product Owner | ||
+ | * Subtract out the Scrum Master | ||
+ | * Remove vacations and holidays for everyone | ||
+ | * E.g. Team of 7 people, including a Product Owner and Scrum Master means (7 - 2) people X 8 points per person results in capacity of 40 points. | ||
+ | * Clarify Team Backlog User Stories | ||
+ | * Collaborate to get common understanding | ||
+ | * Story in “user voice” format - As a < | ||
+ | * Acceptance criteria is gherkin format - Given <system is in a state> when < | ||
+ | * Update and / or revise estimates | ||
+ | * The Team picks from prioritized Backlog, taking items to fill to team Capacity | ||
+ | * Establish Iteration Goals | ||
+ | * Teams commits to the Iteration Goals (e.g. by Fist of Five vote) | ||
- | **Duration:** Maximum 2 hours for a 2 week sprint (10 working days). | + | NOTE: New Teams sometimes have a second meeting immediately after this meeting to determine how they will work together to deliver the commitment but in most cases this is discussed during planning. |
- | **Summary Agenda:** | + | ====== Guidelines ====== |
- | * Clarify Product / Release | + | * In Backlog |
- | * Collaborate to get common understanding | + | * As you do this have Teams ask themselves “do we think we can do this story and all the other stories we have accepted so far? |
- | * Define or review Conditions | + | * NOTE: Sometimes Teams are unable to do in strict order because |
- | * Establish | + | * Iteration (Sprint) Goals are defined based on work that can be done |
- | * Revise estimates | + | * [[what_is_the_purpose_of_iteration_or_sprint_goals|What is the Purpose of Iteration (Sprint) Goals?]] |
- | * The Team picks from prioritized backlog, taking | + | * Include improvement |
+ | * "Fist of five" | ||
+ | * Ensure tooling you are using are up to date based on committed plan. | ||
- | **Result:** A list of backlog items that are candidates for delivery in the next sprint, sometimes called the Selected Backlog. | + | ====== Checklist - Iteration (Sprint) Planning ====== |
- | + | ||
- | ====== Sprint Planning 2 ====== | + | |
- | + | ||
- | **Purpose: | + | |
- | + | ||
- | **Who:** Scrum Master and the Team, with the Product Owner at least available to answer question if not fully engaged. | + | |
- | + | ||
- | **Duration: | + | |
- | + | ||
- | **Summary Agenda:** | + | |
- | + | ||
- | * Determine team capacity | + | |
- | * Review " | + | |
- | * Team plans how it will work together to deliver | + | |
- | * One approach is to break the sprint backlog into tasks, where estimates on the tasks are no greater than 16 hours. | + | |
- | * Identify obstacles/ | + | |
- | * Identify conditions of satisfaction (tests, inspection) | + | |
- | * Make needed adjustments | + | |
- | * Review Sprint Backlog to confirm the Sprint Commitment with the Product Owner | + | |
- | + | ||
- | **Result:** Recorded Sprint Backlog against which the Team has committed to complete by the end of the Sprint. | + | |
- | + | ||
- | //**Sprint Backlog**// | + | |
- | + | ||
- | The Sprint Backlog is the result of Sprint Planning. It represents two things: | + | |
- | + | ||
- | - The subset of the Product Backlog that the Team has committed to deliver in the next Sprint. | + | |
- | - The detailed arrangements that Team has made to help them make the commitment. | + | |
- | + | ||
- | For different Scrum Teams, the level of detail tracked in the Sprint Backlog depends on each Team. The key information is that the Team makes a commitment, and that commitment is knowable to all stakeholders. | + | |
- | + | ||
- | // | + | |
- | + | ||
- | At a minimum, the Sprint Backlog is a list of Product Backlog Items that the Team has committed to deliver in the Sprint and the basis of the information required to generate the Sprint Burn-down chart. In most cases this is a detailed plan of tasks the Team expects to undertake to meet their commitment. This detailed plan is created and tracked by the Team. | + | |
- | + | ||
- | ====== Checklist - Sprint Planning | + | |
===== Preparation ===== | ===== Preparation ===== | ||
- | * Scrum Team is invited: Product Owner, Scrum Master, | + | * Team is invited: Product Owner, Scrum Master, |
- | * Product Backlog is prioritized | + | * Product |
* Backlog Items are estimated | * Backlog Items are estimated | ||
- | * Product Backlog is visible and accessible to everyone in the meeting | + | * Product |
- | * Planned absences (e.g. holidays) of team members are known | + | * Planned absences (e.g. holidays) of Team members are known |
- | * The room / environment is suitable for team discussions | + | * The room / environment is suitable for Team discussions |
- | * The results of the Sprint Review and the Sprint Retrospective are available | + | * The results of the Iteration (Sprint) Review and the Iteration (Sprint) Retrospective are available |
- | * The Sprint Schedule is defined | + | * The Iteration (Sprint) Schedule is defined |
===== Moderation ===== | ===== Moderation ===== | ||
* Make the following items visible to everyone in the meeting: | * Make the following items visible to everyone in the meeting: | ||
- | * Sprint Schedule | + | * Iteration (Sprint) Schedule |
- | * Sprint Review Meeting results | + | * Iteration (Sprint) Review Meeting results |
- | * Sprint Retrospective results (note: these are the public improvement goals rather than, say, minutes of the meeting) | + | * Iteration (Sprint) Retrospective results (note: these are the public improvement goals rather than, say, minutes of the meeting) |
- | * The Product Owner informs the team about the product vision | + | * The Product Owner informs the team about the Product (or Team) Vision |
- | * The Product Owner and the team define the Sprint Goal | + | * The Product Owner and the team define the Iteration (Sprint) Goal based on the Stories selected. |
- | * If there are Backlog Items missing the Product Owner can add the Backlog Item to the Product Backlog | + | * If there are Backlog Items missing the Team can add the Backlog Item to the Team (Product) Backlog |
- | + | ||
- | ===== Results ===== | + | |
- | + | ||
- | Selected Product Backlog is well prepared for the Sprint Planning 2. | + | |
- | + | ||
- | ====== Checklist – Sprint Planning 2 ====== | + | |
- | + | ||
- | ===== Preparation ===== | + | |
- | + | ||
- | * Participants are invited: Scrum Master, | + | |
- | * The Selected Product Backlog - the Sprint Backlog is accessible for the task planning (Optional) | + | |
- | * Material for the planning such as a whiteboard, pin board, sticky notes etc. | + | |
- | + | ||
- | ===== Moderation ===== | + | |
- | + | ||
- | * Team members determine team capacity. An approach to do this is: | + | |
- | * Scrum Master leads | + | |
- | * Count days available for each person | + | |
- | * Do not count Scrum Master, Product Owner | + | |
- | * Breakdown to hours, count 6 hours per day | + | |
- | * Remove other impacts | + | |
- | * Ask “What else” – vacation, moves, other work | + | |
- | * Understand who is not 100% on team and adjust | + | |
- | * Sum total hours available to team in next 9 working days | + | |
- | * Determine percentage of “unplanned” work and breakdown so that you have “hours available for planning purposes” and “hours available for ‘planned unplanned’ proposes. | + | |
- | * Team members find tasks for each Backlog | + | |
- | * Make sure that every piece of work is taken into account to reach Definition of Done – Coding, Testing, etc – to get to a “potentially shippable” state. | + | |
- | * If a task effort is bigger than 16 hours, try to split the task into smaller tasks, so the team can understand during the Sprint whether real progress is being made on the commitment. | + | |
- | * If the team believes that the resultant Sprint Backlog is too large, work with the Product Owner to remove low priority Backlog Items | + | |
- | * If the team believes that the Sprint Backlog is too small, work with the Product Owner to bring in additional Product Backlog items from the Product Backlog | + | |
- | *
The team commits to the Sprint Goal. An approach to make this concrete is to have the Product Owner ask “Fist of five vote – how likely do you think that you’ll be able to make the commitment? | + | |
- | ===== Results | + | ====== Want to Know More? ====== |
- | Sprint Goal and Sprint Backlog are visible to everyone within the organization. The tasks in the Sprint | + | * [[what_events_should_we_put_in_place_for_iterations_or_sprints|What Events Should We Put in Place For Iterations (Sprints)? |
+ | * [[what_should_our_sprint_goals_look_like|What Should Our Sprint | ||
+ | * [[https:// | ||
- | ====== | ||
+ | {{tag> | ||
/home/hpsamios/hanssamios.com/dokuwiki/data/attic/how_do_we_run_our_first_iteration_planning_or_sprint_planning_event.1447794546.txt.gz · Last modified: 2020/06/02 14:27 (external edit)