Differences

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

--- what_events_should_we_put_in_place_for_iterations_or_sprints [2021/11/16 13:36] – [Events] Added DoR 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 23: / Line 23: @@
 | 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                 | 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        | Team works to get their stories to [[what_is_a_definition_of_ready_dor|Definition of Ready (DoR)?]]                                                                                                                                                                                                                                  |
+| 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.                                                     |