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 [2020/11/02 12:39] – [Want to Know More?] hans | 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 (or Iteration) Planning | + | ====== How Do We Run Our First Iteration |
+ | 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 (or Iteration) Planning is to allow the team to commit to what they can deliver in the next Sprint - the committed Sprint (or Team) Backlog. | + | ====== Structure ====== |
+ | |||
+ | ===== Who ===== | ||
- | Sprint (or Iteration) Planning occurs at the beginning of the Sprint (or Iteration), after you have completed the Sprint (or Iteration) Review and Retrospective of the current (or Iteration) Sprint (i.e. the (or Iteration) Review and (or Iteration) Retrospective are an input to the Sprint (or Iteration) Planning). Note that there is typically no gap between the end of one Sprint (or Iteration) | + | Scrum Team - Team, Scrum Master, Product Owner and other stakeholders as required. |
- | Sprint (or Iteration) Planning may be divided into two sessions, be conducted as one session, or occur as a series of shorter incremental sessions. Typically, Sprint (or Iteration) Planning is viewed as having two parts: | + | ===== Duration ===== |
- | * Sprint (or Iteration) Planning 1 - Used by the Team to reach common agreement on Product Backlog items with the highest priority (including their Conditions of Satisfaction or Acceptance Criteria), to determine likely items for the Sprint (or Team) Backlog, and to discuss these latter items sufficiently so the Team can effectively conduct Sprint (or Iteration) Planning | + | Maximum 2 hours for a 2 week sprint |
- | * Sprint (or Iteration) Planning 2 – used by Teams to determine in detail how they will make and meet their commitment for the Sprint (or Iteration) including applicable Definition of Done criteria and considerations regarding individual Team Member availability during the Sprint (or Iteration). Most Teams do this by taking each Sprint (or Team) Backlog item and detailing it in terms of the tasks required to complete the work. Each task for an item has an estimate in hours (or, for some Teams, story points) that would take into consideration potential obstacles, risks and dependencies. | + | |
- | By the end of Sprint (or Iteration) 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 ====== | + | * 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 to Iteration (Sprint) Goals | ||
- | The team should use the data they have to help them make good commitments. For example, during the Sprint (or Iteration) Planning 1 process the team will have velocity or throughput information to help them understand how much they can complete as a Team. By keeping a running total of the points a team thinks it can work in the upcoming Sprint (or Iteration), and comparing it to the “normal” velocity of the team, the team can easily gauge whether they are over-committing. | + | ====== Result ====== |
- | Similarly when the team gets to Sprint (or Iteration) | + | 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), |
- | ====== | + | ====== |
- | **Purpose:** Determine what the Team should build in the next Sprint | + | |
+ | * If Team has a (Velocity) history from previous Iterations use this to determine | ||
+ | * 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 | ||
+ | * Teams commits to the Iteration Goals (e.g. by Fist of Five vote) | ||
- | **Who:** Scrum Team - Team, Scrum Master, Product Owner and other stakeholders as required. | + | 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. |
- | **Duration: | + | ====== Guidelines ====== |
- | **Summary Agenda:** | + | |
+ | | ||
+ | * NOTE: Sometimes Teams are unable to do in strict order because of, for example, a need for specialized skills. | ||
+ | * Iteration (Sprint) Goals are defined based on work that can be done | ||
+ | * [[what_is_the_purpose_of_iteration_or_sprint_goals|What is the Purpose of Iteration (Sprint) Goals?]] | ||
+ | * Include improvement items | ||
+ | | ||
+ | | ||
- | * Clarify Product / Release (or Team) Backlog items | + | ====== |
- | * Collaborate to get common understanding | + | |
- | * Define or review Definition of Ready criteria | + | |
- | * Define or review Conditions of Satisfaction (or Acceptance Criteria) | + | |
- | * Establish [[what_is_the_purpose_of_sprint_or_iteration_goals|Sprint (or Iteration) Goals]] | + | |
- | * Revise estimates | + | |
- | * The Team picks from prioritized Backlog, taking items to fill to team capacity | + | |
- | + | ||
- | **Result:** A list of backlog items that are candidates for delivery in the next Sprint (or Iteration), sometimes called the Selected Backlog. | + | |
- | + | ||
- | ====== | + | |
- | + | ||
- | **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 (or Iteration) Backlog into tasks, where estimates on the tasks are no greater than 8 hours, preferably shorter. | + | |
- | * Identify obstacles/ | + | |
- | * Identify dependencies | + | |
- | * Identify conditions of satisfaction or acceptance criteria (tests, inspection) | + | |
- | * Make needed adjustments | + | |
- | * Review Sprint (or Iteration) Backlog to confirm the Sprint (or Iteration) Commitment with the Product Owner | + | |
- | + | ||
- | **Result:** Recorded Sprint (or Iteration) Backlog against which the Team has committed to complete by the end of the Sprint (or Iteration). | + | |
- | + | ||
- | //**Sprint (or Iteration) Backlog**// | + | |
- | + | ||
- | The Sprint (or Iteration) Backlog is the result of Sprint (or Iteration) Planning. It represents two things: | + | |
- | + | ||
- | | + | |
- | - The detailed arrangements that Team has made to help them make the commitment. | + | |
- | + | ||
- | For different Teams, the level of detail tracked in the Sprint | + | |
- | + | ||
- | // | + | |
- | + | ||
- | At a minimum, the Sprint | + | |
- | + | ||
- | ====== Checklist - Sprint (or Iteration) Planning | + | |
===== Preparation ===== | ===== Preparation ===== | ||
Line 86: | Line 69: | ||
* 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 (or Iteration) Review and the Sprint (or Iteration) Retrospective are available | + | * The results of the Iteration |
- | * The Sprint (or Iteration) Schedule is defined (i.e. start and end date of the Sprint (or Iteration)) | + | * The Iteration |
===== Moderation ===== | ===== Moderation ===== | ||
* Make the following items visible to everyone in the meeting: | * Make the following items visible to everyone in the meeting: | ||
- | * Sprint (or Iteration) Schedule | + | * Iteration |
- | * Sprint (or Iteration) Review Meeting results | + | * Iteration |
- | * Sprint (or Iteration) Retrospective results (note: these are the public improvement goals rather than, say, minutes of the meeting) | + | * Iteration |
* The Product Owner informs the team about the Product (or Team) Vision | * The Product Owner informs the team about the Product (or Team) Vision | ||
- | * The Product Owner and the team define the Sprint (or Iteration) Goal | + | * The Product Owner and the team define the Iteration |
- | * 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 (or Iteration) Planning 2. | + | |
- | + | ||
- | ====== Checklist – Sprint (or Iteration) Planning 2 ====== | + | |
- | + | ||
- | ===== Preparation ===== | + | |
- | + | ||
- | * Participants are invited: Scrum Master, | + | |
- | * The Selected Product | + | |
- | * Material for the planning such as a whiteboard, pin board, sticky notes, access to tools, etc. | + | |
- | + | ||
- | ===== Moderation ===== | + | |
- | + | ||
- | * Team Members determine team capacity. An approach to do this is (assuming a 2 week Sprint (or Iteration)): | + | |
- | * Scrum Master leads | + | |
- | * Count days available for each person | + | |
- | * Do not count Scrum Master, | + | |
- | * 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 Item | + | |
- | * 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 8 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 (or Iteration) Backlog | + | |
- | * If the team believes that the Sprint (or Iteration) 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 (or Iteration) 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 ===== | + | |
- | + | ||
- | Sprint (or Iteration) Goal and Sprint (or Iteration) Backlog are visible to everyone within the organization. The tasks in the Sprint Backlog are accessible to all team members. | + | |
- | ===== Want to Know More? ===== | + | ====== Want to Know More? ====== |
+ | * [[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 Goals Look Like?]] | * [[what_should_our_sprint_goals_look_like|What Should Our Sprint Goals Look Like?]] | ||
* [[https:// | * [[https:// |
/home/hpsamios/hanssamios.com/dokuwiki/data/attic/how_do_we_run_our_first_iteration_planning_or_sprint_planning_event.1604349566.txt.gz · Last modified: 2020/11/02 12:39 by hans