Changes for page Planning Game

Summary

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

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