User Tools

Site Tools


how_do_we_run_our_first_iteration_planning_or_sprint_planning_event

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
how_do_we_run_our_first_iteration_planning_or_sprint_planning_event [2020/12/17 10:02]
hans
how_do_we_run_our_first_iteration_planning_or_sprint_planning_event [2021/04/28 11:35] (current)
hans Changed terminology to reflect more modern language
Line 7: Line 7:
 Iteration (Sprint) Planning may be divided into two sessions, be conducted as one session, or occur as a series of shorter incremental sessions. Typically, Iteration (Sprint) Planning is viewed as having two parts: Iteration (Sprint) Planning may be divided into two sessions, be conducted as one session, or occur as a series of shorter incremental sessions. Typically, Iteration (Sprint) Planning is viewed as having two parts:
  
-  * Iteration (Sprint) 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 Iteration (Sprint) Planning 2, where they will commit to deliver specific items by the end of the Iteration (Sprint).+  * Iteration (Sprint) Planning 1 - Used by the Team to reach common agreement on Product Backlog items with the highest priority (including their Acceptance Criteria (or Conditions of Satisfactionor 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 Iteration (Sprint) Planning 2, where they will commit to deliver specific items by the end of the Iteration (Sprint).
   * Iteration (Sprint) Planning 2 – used by Teams to determine in detail how they will make and meet their commitment for the Iteration (Sprint) including applicable Definition of Done criteria and considerations regarding individual Team Member availability during the Iteration (Sprint). 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.   * Iteration (Sprint) Planning 2 – used by Teams to determine in detail how they will make and meet their commitment for the Iteration (Sprint) including applicable Definition of Done criteria and considerations regarding individual Team Member availability during the Iteration (Sprint). 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.
  
Line 27: Line 27:
  
   * Define or review Definition of Ready criteria   * Define or review Definition of Ready criteria
-  * Clarify Team (Product) Backlog items and define or review Conditions of Satisfaction (or Acceptance Criteria)+  * Clarify Team (Product) Backlog items and define or review Acceptance Criteria (or Conditions of Satisfaction(or Acceptance Criteria)
     * Collaborate to get common understanding     * Collaborate to get common understanding
   * Establish [[what_is_the_purpose_of_iteration_or_sprint_goals|Iteration (Sprint) Goals]]   * Establish [[what_is_the_purpose_of_iteration_or_sprint_goals|Iteration (Sprint) Goals]]
Line 51: Line 51:
   * Identify obstacles/risks   * Identify obstacles/risks
   * Identify dependencies   * Identify dependencies
-  * Identify conditions of satisfaction or acceptance criteria (tests, inspection)+  * Identify Acceptance Criteria (or Conditions of Satisfaction) or acceptance criteria (tests, inspection)
   * Make needed adjustments   * Make needed adjustments
   * Review Iteration (Sprint) Backlog to confirm the Iteration (Sprint) Commitment with the Product Owner   * Review Iteration (Sprint) Backlog to confirm the Iteration (Sprint) Commitment with the Product Owner
/home/hpsamios/hanssamios.com/dokuwiki/data/pages/how_do_we_run_our_first_iteration_planning_or_sprint_planning_event.txt · Last modified: 2021/04/28 11:35 by hans