1. The concept of iteration planning arises for defining intermediate results sequences.
2. The most definite form of the risk management plan is to the content and schedule of major milestones and their intermediate iterations.
3. Basically, iteration can be beefing as a synchronized, global assessment of the entire project-baseline.
4. The general guidelines of iteration planning depend on the iteration count in each phase of the project life cycle.
5. Micro iterations are also performed to the project-level synchronization points.
6. The inception and elaboration iterations are carried out in an engineering stage, whereas the construction and transition iterations are carried out in the production stage.
7.Inception iterations: Inception iterations are considered as the feasibility iterations.
8. These iterations result in the integration of candidate architecture components and executable framework.
9.Candidate architecture demonstration: To demonstrate the candidate architecture, the framework must include the foundation components such as commercial components, custom prototypes, and existing components.
10.Establishment of business case vision and software plan: Requirements understanding are enough to establish a possible business case, vision, and software development plan.
11. Large-scale, custom development projects may require two iterations.
12. Most of the projects use only one iteration in the inception phase.
Elaboration iterations:
13. Elaboration iterations are considered as the architecture iterations.
14. These iterations result in architecture with a complete framework and execution structure.
15. A few critical use cases need to be demonstrated after completing the architecture iteration.
Transition iterations:
16. Transition iterations are treated as the final product releases.
17. To transition a beta release into a final product, most of the projects use a single iteration.
18.In order to solve all defects or defect reduction by including beta feedback and performance improvement many small scale iterations are needed.
19.teration count in this phase is carried out.
20. Most of the projects use a single iteration between beta release and final product release, because of the associated type of full-scale transition to the group of users.
21. By summarizing all these iterative phases the general criteria are, most projects must have four to nine iterations.
22. In the case of highly precedented projects or very small-scale projects inceptions and elaboration, phases require only a single iteration that produces a product with four iterations.
23. In case of unprecedented or very large scale projects, there is a requirement of one extra inception iteration, two extra construction iterations.
24. Forming a total of nine iterations.
25. Finally, the management overhead is valuable to assure risk management and synchronization of stakeholders.
26. The planning which is done practically for a successful project is called pragmatic planning.