When experts are asked about the usibility of IBM’s Rational Unified Process for agile projects they mostly agree that it is too complex to apply and the experienses show that other, special considerations and simplifications are necessary. This is why agile unified process was developed. So what is this unified process? Wikipedia said:
Agile Unified Process (AUP) is a simplified version of the IBM Rational Unified Process (RUP) developed by Scott Ambler. It describes a simple, easy to understand approach to developing business application software using agile techniques and concepts yet still remaining true to the RUP. The AUP applies agile techniques including test driven development (TDD), Agile Modeling, agile change management and database refactoring to improve productivity.
7 Disciplines of Agile Unified Process
During model creation, first the organization and the problem domain have to be understood, then a viable solution has to be found for the problem.
After model creation, during implementation phase, the model has to be transformed into executable code that has to be tested at a basic level.
Basic tests are just the beginning. To ensure the required quality, a more comprehensive, objective evaluation has to be conducted. If it is done well:
- defects are found
- working of the system is validated against the designs
- meeting of requirements are verified
The tested system is deployed and delivered to the end users.
Configuration management is an important part of the unified process. It manages the access to project artifacts that covers tracking of artifacts versions and their changes.
During the process, project managent‘s role is to direct the activities, managing risks and coordinating with people and systems outside the scope of the project. Why? The aim is to deliver the project on time and within budget.
The last principle, the environment, is also a very important aspect. When the team needs processes, tools and guidance have to be available to optimize the efficiency of the project.