Skip to Content

Changes for page Planning Game

Last modified by chrisby on 2024/06/20 14:40
From version 15.20
edited by chrisby
on 2023/12/09 12:12
Change comment: There is no comment for this version
To version 15.21
edited by chrisby
on 2023/12/18 11:14
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,10 +1,12 @@
1 1  # User Stories
2 2  
3 -In Agile, **the project workload is broken down into user stories** and estimated, prioritized, and assigned. A user story, or often just called a 'story', is an abbreviated description of a feature of a system, told from the user's perspective. There are two forms:
3 +In Agile, **the project workload is broken down into user stories** and estimated, prioritized, and assigned. A user story, or often just called a 'story', is an abbreviated description of a feature of a system, told from the user's perspective. There are two forms:
4 4  
5 5  * Long form = A sentence that describes exactly how the user interacts with the system. "When I go to the login page, enter my credentials and click the login button, the home page appears."
6 6  * Short form = A minimal set of words that hint at the underlying interactions, such as "Login".
7 7  
8 +**Story-Driven Development**: 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.
9 +
8 8  # Iterations
9 9  
10 10  Opposed to dividing the project schedule into distinct phases like in [[waterfall|doc:Software Engineering.Agile.Problems of Waterfall.WebHome]] workflow, in Agile **the project schedule is broken down into iterations 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.