Organicity of Iterative Methodology. Part 2: Optimization of Effort.
Continuing the discussion on the topic of organicity in iterative methodology, let’s now turn to another important advantage of this approach — the optimization of effort. One of the main reasons for reducing effort when using iterative methodology is that the goals defined during the iteration’s requirements phase remain unchanged throughout its execution.
As mentioned
in the first part, iterative methodology consists of a sequence of cycles, each of which includes specific stages and links. In the first cycle of web development, for example, the links may include:
- Requirement definition,
- Structural design,
- Design development,
- Technical specification development,
- Frontend layout,
- Frontend programming,
- Backend programming,
- Backend layout.
The second cycle may contain fewer links, such as:
- Requirement definition,
- Design refinement,
- Technical specification development,
- Frontend layout refinement,
- Frontend programming.
The advantage of iterative methodology is that the goals of each iteration are predetermined and remain constant throughout the development process. This means that significant changes in requirements or project goals do not occur during the execution of an iteration. Such stability and continuity ensure optimal resource allocation and enable the development team to focus on the tasks specified for that iteration.
Thanks to this focus on specific tasks, the team can use its resources and time most efficiently. Instead of expending energy on constant replanning and reorganizing work, developers can concentrate on completing the tasks defined in advance for each iteration. This contributes to increased productivity and reduced effort since the team can work more efficiently and effectively.
Furthermore, the defined goals of an iteration facilitate project management and enable more accurate resource and time planning. The team can predict and estimate the effort required for each iteration based on the predefined tasks. This allows for a more precise distribution of work and resources, avoiding excessive workload or inefficient resource utilization.
Thus, the organicity of iterative methodology contributes to the optimization of effort in the project development process. Stable and unchanging goals for each iteration allow the development team to focus on task execution, minimizing the need for constant changes and replanning. This enables more efficient resource utilization, leading to increased productivity and quality of work.
