Iteration Planning

Iteration planning

is generally a process of adapting as the project unfolds by making alterations to plans. Plans are changed simply based on feedback from the monitoring process, some changes on project assumptions, risks, and changes in scope, budget, or schedule. It is essential to include the team in the planning process. Planning is generally concerned with explaining and defining the actual sequence of intermediate results. It is an event where each team member identifies how much of the team backlog, they can commit to delivering during an upcoming iteration. Iteration planning is generally the process of discussing and planning the next cycle, phase, or iteration of a software application that is in the process of development. An evolutionary developed plan is very essential because there are always adjustments in developed content and schedule as an early conjecture that simply evolves into highly and well-understood project circumstances.

Iteration Planning

1. Inception Iterations: In some of cases where the project includes a new product roll-out or simply the creation of new technology, iterations might be essential to further explain the scope of the project, risks, and all benefits. It might also involve a further increase in the quality of the use-case model, business case, risk list, architectural proof-of-concept, or even project and iteration plans. Extension of this inception phase can also be advised in some cases where both risk and required investment are high. It can also be advised where the problem domain is new or the team is not experienced. The early prototyping technique also integrates the foundation components of the architecture of the candidate and also provides an executable framework for explaining and simply elaborating the use cases of the system. To achieve an acceptable prototype, Large-scale, and custom developments are two iterations. But various projects should be able to get by use of only one. Inception iteration is generally responsible for establishing scope and vision and explaining and defining the business case.
2. Elaboration Iterations: In each of iteration, supporting environment is refined further. If the initial elaboration is only focused on the preparation of the environment for analysis design and implementation then the second iteration might focus on the preparation of the test environment. The preparation of the test environment includes configuring test processes, writing the development case part, and preparing or generating templates and guidelines that need to be followed for test and setting up test tools. Elaboration iteration also results in architecture with a complete framework and infrastructure for execution. To achieve an acceptable architecture baseline, some of the projects require two iterations. Some additional and extra iterations may be required by unprecedented architectures. On the other hand, projects that are developed on highly well-established architecture frameworks can be achieved by the use of a single iteration. During elaboration iteration, requirements are defined fully and architectures are well-established.
3. Construction Iterations: The essential result of late iteration in the construction phase is that more functionality is added, which yields an increasingly complete system. During construction iteration, use cases are generally realized and architectures are fleshed out. Some projects need and require two construction iterations. First is an alpha release that includes executable capability for each of the critical use cases. Second, is a beta release that provides 95 % of the total product capability breadth and also achieves some of the essential quality attributes that are needed and important.
4. Transition Iterations for migrating: Transition iteration is generally responsible for migrating products into the user community. Several projects use only one iteration to transition the beta release into the end product or final product. Even these projects learn to live with only one iteration between the beta release and the end product or final product release.