Changes for page Planning Game

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -5,8 +5,6 @@
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		-
10	10	# Iterations
11	11
12	12	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.
...	...	@@ -59,4 +59,8 @@
59	59	* **Passing Tests**: Show that all unit and acceptance tests have passed, including those from previous iterations.
60	60	* **Demo Server**: Ideally, stakeholders should be able to interact with the latest release of the system on their own, for example on a demo server separate from the production server. This also prevents developers from being tempted to hide things that do not work.
61	61	* **Progress Update**: At the end of an iteration, sum the points of each <ins>completely</ins> finished story and add that value as a data point to the [[agile charts|doc:.Agile and Data.WebHome]]. Unfinished stories and all their points are ignored and moved to the next iteration.
62		-* **Iterations do not fail**: Initial velocity estimates are often overly optimistic and therefore higher than the actual measured velocity. The goal is a realistic view of team productivity. Iterations don't fail; they adjust the velocity prediction.
	60	+* **Iterations do not fail**: Initial velocity estimates are often overly optimistic and therefore higher than the actual measured velocity. The goal is to provide a realistic view of team productivity, not an accurate prediction. Iterations don't fail; they adjust the velocity prediction.
	61	+
	62	+## Story-Driven Development
	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.