Skip to Content

Changes for page Planning Game

Last modified by chrisby on 2024/06/20 14:40
From version 15.14
edited by chrisby
on 2023/10/12 13:45
Change comment: There is no comment for this version
To version 15.16
edited by chrisby
on 2023/11/18 16:36
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  
... ... @@ -40,8 +40,8 @@
40 40  * **Story Deck Evolution**
41 41   * Solved stories are removed from the Story Deck. As the project progresses, new usage requirements may emerge and be added as new cards to the Story Deck. Stories could also split or merge.
42 42   * Estimated effort and business value are affected by the evolution of the project. Therefore, stories need to be re-evaluated and the story deck re-ordered on a regular basis, i.e. in the IPMs.
43 - * There may be stories that do not currently have a favorable cost/benefit ratio and are not worth implementing. They remain in the story deck because there is a chance that their estimated effort and business value will change over time, making them worth implementing later. Conversely, some stories may become irrelevant over time.
44 - * If the story deck has no stories with a cost/benefit ratio that makes them worth implementing, the project ends.
43 + * There may be stories that do not currently have a favorable ROI and are not worth implementing. They remain in the story deck because there is a chance that their estimated effort and business value will change over time, making them worth implementing later. Conversely, some stories may become irrelevant over time.
44 + * If the story deck has no stories with a ROI that makes them worth implementing, the project ends.
45 45  
46 46  ### During Iteration
47 47