Skip to Content

Changes for page Planning Game

Last modified by chrisby on 2024/06/20 14:40
From version 15.23
edited by chrisby
on 2023/12/18 11:24
Change comment: There is no comment for this version
To version 15.24
edited by chrisby
on 2023/12/18 11:27
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -61,4 +61,6 @@
61 61  
62 62  ## Story-Driven Development
63 63  
64 -In projects, there may be many interdependent stories to implement, so the final design will be very complex and impossible to predict in advance. Therefore, the initial [[waterfall|doc:Software Engineering.Agile.Problems of Waterfall.WebHome]] planning is likely to fail. The solution is to implement the stories sequentially, even if it means redesigning the previous design frequently. This breaks the one big complex problem into many small but manageable chunks. Even when working more informally or alone, it makes sense to have a story deck. It reduces the mental load of having to design everything in advance, and allows you to focus on the current simple story that needs to be implemented.
64 +In projects, there may be many interdependent stories to implement, so the final design will be very complex and impossible to predict in advance. Therefore, the initial [[waterfall|doc:Software Engineering.Agile.Problems of Waterfall.WebHome]] planning is likely to fail. The solution is to implement the stories sequentially, as described above, even if it means redesigning the previous design frequently, which is why this approach is called **story-driven development**. It breaks the big complex problems into many small but manageable chunks.
65 +
66 +Even when working more informally or alone, it makes sense to have a story deck. It reduces the mental load of having to design everything in advance, and allows you to focus on the current simple story that needs to be implemented.