Differences

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

--- what_events_should_we_put_in_place_for_iterations_or_sprints [2020/12/17 09:28] – ↷ Page name changed from what_meetings_should_we_put_in_place_for_iterations_or_sprints to what_events_should_we_put_in_place_for_iterations_or_sprints hans
+++ what_events_should_we_put_in_place_for_iterations_or_sprints [2022/02/23 07:03] (current) – ↷ Links adapted because of a move operation hans
@@ Line 1: / Line 1: @@
-====== What Meetings Should We Put in Place For Iterations (Sprints)? ======
+====== What Events Should We Put in Place For Iterations (Sprints)? ======
 One the key tools that we use when we work an Lean Agile (Scrum) implementation is the notion of a "cadence". See [[what_is_the_benefit_of_having_a_cadence_of_meetings_etc|What is the Benefit of Having a Cadence of Meetings Etc?]] for more on why this is important.
@@ Line 20: / Line 20: @@
 ^ Meeting                            ^ Cadence                      ^ Length         ^ Purpose                                                                                   ^ Comments                                                                                                                                                                                                                                                                ^
-| Iteration Planning (or Sprint Planning)            | First day of the Iteration   | Max 2 hours    | Team makes a reasonable commitment to complete a set of work by the end of the Iteration  | For the next Iteration (Sprint), this can be scheduled either on the same day or the day after the Demo and Retro depending the timing of the demo. See [[how_do_we_run_our_first_iteration_or_sprint_planning_meeting|How Do We Run Our First Iteration Planning (Sprint Planning)?]] for more information.  |
+| Iteration Planning (or Sprint Planning)            | First day of the Iteration   | Max 2 hours    | Team makes a reasonable commitment to complete a set of work by the end of the Iteration  | For the next Iteration (Sprint), this can be scheduled either on the same day or the day after the Demo and Retro depending the timing of the demo. See [[how_do_we_run_our_first_iteration_planning_or_sprint_planning_event|How Do We Run Our First Iteration Planning (Sprint Planning)?]] for more information.  |
-| Daily Standup (or Daily Scrum)                        | Every day of the Iteration   | Max 15 mins    | Team synchronizes their efforts in order to meet Iteration Goals                          | See [[what_is_the_purpose_of_a_daily_scrum_meeting|What is the Purpose of a Daily Stand-up (Daily Scrums)?]] for more information.                                                                                                                                                |
+| Daily Standup (or Daily Scrum)                        | Every day of the Iteration   | Max 15 mins    | Team synchronizes their efforts in order to meet Iteration Goals                          | See [[what_is_the_purpose_of_a_daily_standup_or_daily_scrum_event|What is the Purpose of a Daily Stand-up (Daily Scrums)?]] for more information.                                                                                                                                                |
-| Mid-Iteration Review               | Middle day of the Iteration  | Max 1 hour     | Team determines whether they are on course or whether they need to adjust                 | Often combined with Backlog Refinement                                                                                                                                                                                                                                  |
+| Mid-Iteration Review               | Middle day of the Iteration  | Max 1 hour     | Team determines whether they are on course or whether they need to adjust                 | Most teams do not need this. It is used in environments where there is a lot of change. If teams do this a lot, they might want to consider 1 week iterations (or sprints). If used, it is combined with Backlog Refinement                                                                                                                                                                                                                                  |
-| Backlog Refinement                 | Middle day of the Iteration  | Max 2 hours    | Team looks ahead to next Iteration to see if they are ready for Iteration Planning        | Often combined with Mid-Sprint Review                                                                                                                                                                                                                                   |
+| Backlog Refinement                 | Middle day of the Iteration  | Max 2 hours    | Team looks ahead to next Iteration to see if they are ready for Iteration Planning        | Team works to get their stories to [[what_is_a_definition_of_ready_dor_ssa|Definition of Ready (DoR)?]]                                                                                                                                                                                                                                  |
 | Iteration Demo (or Sprint Review)  | Last day of Iteration        | Max 1 hour     | Team provides "objective milestone" of progress and gets feedback from stakeholders       | Create specific meeting that includes your stakeholders. See [[how_do_we_run_our_first_iteration_demo_or_sprint_review|How Do We Run Our First Iteration Demonstation (Sprint Review)?]] for more information.                                                                                                     |
 | Iteration Retrospective  (or Sprint Retrospective)          | Last day of Iteration        | Max 1.5 hours  | Team reflects on how to become more effective and adjusts its behavior accordingly        | This event typically runs after the Demonstration so you can incorporate stakeholder feedback in your Retrospective. See [[how_do_we_run_our_first_sprint_retrospective|How Do We Run Our First Iteration Retrospective (Sprint Retrospective)]] for more information.                                                     |
@@ Line 33: / Line 33: @@
 {{ calender_of_sprint_events.png?direct&900 |}}
-Note that we try to set up Iteration (Sprint) so they start / end in the middle of the week. If you set things up so they start / end around the weekend, you will find:
+Note that we try to set up Iteration (Sprint) so they start / end in the middle of the week …
-  - Events will often have to be delayed by long weekend holidays
+{{page> why_do_we_start_and_end_iterations_sprints_mid-week&noindent&notags&nouser&nomdate&nodate&firstseconly}}
-  - Your team will do non-sustainable things like "working weekends" to meet objectives
 ====== Want to Know More? ======
-  * [[how_do_we_run_our_first_iteration_or_sprint_planning_meeting|How Do We Run Our First Iteration Planning (Sprint Planning)?]]
+  * [[how_do_we_run_our_first_iteration_planning_or_sprint_planning_event|How Do We Run Our First Iteration Planning (Sprint Planning)?]]
-  * [[what_is_the_purpose_of_a_daily_scrum_meeting|What is the Purpose of a Daily Stand-up (Daily Scrums)?]]
+  * [[what_is_the_purpose_of_a_daily_standup_or_daily_scrum_event|What is the Purpose of a Daily Stand-up (Daily Scrum)?]]
   * [[how_do_we_run_our_first_iteration_demo_or_sprint_review|How Do We Run Our First Iteration Demonstation (Sprint Review)?]]
   * [[how_do_we_run_our_first_sprint_retrospective|How Do We Run Our First Iteration Retrospective (Sprint Retrospective)?]]