Changes for page Planning Game

Last modified by chrisby on 2024/06/20 14:40

From version 15.15
edited by chrisby
on 2023/11/15 18:57
Change comment: There is no comment for this version
To version 15.17
edited by chrisby
on 2023/11/28 19:08
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -7,7 +7,7 @@
7 7  
8 8  # Iterations
9 9  
10 -Opposed to dividing the project schedule into distinct phases like in [[waterfall|doc:Software Engineering.Agile.Problems of Waterfall.WebHome]] workflow, <ins>the project schedule is broken down into iterations</ins> with a fixed size of usually two weeks. For example, a 1-year project could have 26 iterations of 2 weeks each. An iteration is not a mini-waterfall with specific phases that occur only once and in a particular order, such as planning -> design -> implementation -> testing. In an iteration, all phases are performed continuously, allowing for overlap and frequent revisits. For example, if a design problem arises during implementation, you simply redesign immediately and then continue implementing.
10 +Opposed to dividing the project schedule into distinct phases like in [[waterfall|doc:Software Engineering.Agile.Problems of Waterfall.WebHome]] workflow, in Agile <ins>the project schedule is broken down into iterations</ins> with a fixed size of usually two weeks. For example, a 1-year project could have 26 iterations of 2 weeks each. An iteration is not a mini-waterfall with specific phases that occur only once and in a particular order, such as planning -> design -> implementation -> testing. In an iteration, all phases are performed continuously, allowing for overlap and frequent revisits. For example, if a design problem arises during implementation, you simply redesign immediately and then continue implementing.
11 11  
12 12  ## Goals of the Initial Iteration
13 13  
... ... @@ -20,9 +20,7 @@
20 20  
21 21  ### Start of Iteration
22 22  
23 -**The Iteration Planning Meeting (IPM)**
24 -
25 -* **Meeting Setup**
23 +* Each iteration begins with the **Iteration Planning Meeting (IPM)**. Meeting Setup:
26 26   * The purpose is to determine and prioritize stories to be implemented in the current iteration based on estimated effort and business value.
27 27   * The IPM allocates about 1/20 of the total iteration time. For a two-week iteration, this translates to a half-day IPM.
28 28   * The whole team and the stakeholders attend the meeting.