Agile Unified Process
The Agile Unified Process (AUP) is a simplified version of the Rational Unified Process (RUP) created by Scott Ambler in the early 2000s. Its aim was to adapt RUP's architectural robustness to agile principles, reducing its documentation overhead and organizing development into short iterations geared toward the continuous delivery of value.
Context: RUP and its simplification
The Rational Unified Process was a complete but heavyweight software development framework, known for its exhaustive documentation and its tightly defined phase structure. AUP takes its four-phase structure and its emphasis on architecture, but removes much of the documentation bureaucracy and adopts agile practices such as iterative development and continuous collaboration with the customer.
Key characteristics
- Iterative and incremental: development is organized into short iterations that produce partial, working deliveries.
- Emphasis on architecture: the elaboration phase is dedicated to confirming that the chosen architecture is viable before building on it, which reduces early technical risks.
- Efficient documentation: only the necessary documentation is produced, avoiding RUP's documentation overload.
- Collaboration with stakeholders: continuous communication with the customer is encouraged from the earliest phases.
- Adaptable: it can be adjusted to projects of different sizes and complexities.
The four phases of the AUP cycle
- Inception: the scope and size of the project are identified, an initial architecture is proposed, and the budget is set.
- Elaboration: the suitability of the chosen architecture is confirmed. This is the phase that most distinguishes AUP from other agile frameworks: investing time in validating the architecture before building significantly reduces the risk of having to redo work.
- Construction: incremental development of the system following the stakeholders' functional priorities, with regular deliveries.
- Transition: final validation and deployment of the system into the production environment.
AUP in perspective
AUP has limited adoption in 2025. Its use declined as Scrum and other lighter frameworks became established as the industry standard. Its value today is mainly as a historical and conceptual reference:
- For teams working on systems with high architectural complexity, where AUP's emphasis on the elaboration phase remains relevant.
- As a bridge for organizations with a RUP culture that want to move toward more agile practices without completely abandoning their process structure.
Common mistake
Mistaking AUP for a lightweight agile framework. Despite its name and its incorporation of agile principles, AUP is still more structured and documentation-heavy than Scrum or Kanban. Teams looking for real operational agility will find lighter frameworks more useful; AUP makes sense in contexts where architecture and documentation traceability are non-negotiable requirements.
References
- Ambler, Scott W. (2002). Agile Modeling: Effective Practices for Extreme Programming and the Unified Process. Wiley.
See also
Want to take your agility further? You can look for upcoming course and exam dates, or go at your own pace by becoming an Agile Club member. Membership includes exclusive resources, e-learning classrooms, and access to Skill Arena: a space to practice and measure your agile skills whenever it suits you.