Explain why the process of project planning is iterative and why a plan must be continually reviewed during a software project?

Answer 1

In software systems development, iterative project planning adds agility to the development process by allowing the developers as well as the users to learn from, and build upon former software development projects. In particular, iterative development reduces development risks such as poorly defined user requirements; untenable architectures as well as untenable user interfaces. Iteration is defined as the process of repeating something as often as is necessary until a specific result is achieved. This certainly holds true when defining the exact user requirements of a computerized system before the design and development stages begin. It is often stated that if you can find an error or an oversight during the requirements definition stage, you can fix it with an eraser and a pencil. Finding the same mistake once the system has become operational, can be costly in several ways.
A project plan is analogous to a road map that not only shows you how to get from point A to point B; but also lists various milestones along the way. A project plan is similar to a road map with the exception that it also includes the "what" and the "when" with respect to certain project resource requirements as well as their critical paths. A project plan must be continuously monitored to as to determine, at any point in time during the project, if the planned progress of the project corresponds with the actual progress of the project. A discrepancy can be the result of poor planning and/or the introduction of one or more factors during the project that were unforeseen during the project planning phase. If such a discrepancy exists, it must be intercepted at the earliest point in time possible so that immediate corrective actions can be taken, thus minimizing the possibility that the project will not be completed on time and/or within the allocated budget.