Agile practices teach to respect every aspect of the whole work and to appreciate the values of the project development in order to achieve the desired business results.
Every technique from a big Agile family has its own features and peculiarities, but there is one common thing for them all. Every Agile practice is performed according to a specific scenario.
1. Iterative process
Iterative process concept implies a performance of work in the form of several phases that are being executed in parallel to each other. The obtained work results are analyzed and can be also corrected in order to increase the quality of such a project management practice.
Iterative process has its certain scheme a special cycle consisting of ‘plan-do-check-act’ algorithm (PDCA). It allows developers to have the following advantages in the project development process:
- a tangible risk reduction in the early stages of project production
- a continuous work planning and testing of the project’s produced elements simultaneously with its development
- a uniform workload on all the specialists involved in the project development
- an easy assessment of the current state of the project
2. Adaptive process
The adaptive Agile process can be considered as the entire strategy of Agile. In this context, it gives an opportunity to make changes to the project structure at any stage of its development. It means that a long-term Agile planning is absent, and the project is always on alert to accept any changes in the form of adding new features or removing any existing functions.
The adaptive process can be helpful when:
- the project has no clear requirements for its development, and everything can be solved at the last minute
- the project is undergoing constant structural changes (top management, sponsors and investors, stakeholders and others)
- the previous version of the project was subjected to a deep marketing analysis, and at the earliest possible time it may require constant but not consistent additions or changes
3. Two-level process
The two-level process is one of the most complex projects development approaches. It is a special structural process when the project is being developed in two dimensions: the first level implies some short iterations and periods of the active implementation of some components, and the second level is presented as the structuring and systematizing of all these components and their filling into releases.
This system shows its effectiveness in that the first level usually consists of a purely technical development, while the second level already includes all other additions to the project structure.
The two-level process looks good for the projects with very complex structures and that require their gradual and phased development (banking systems, programs for high-security enterprises, etc.)