A description of XP as a minimal instance of RUP.

This technical report fits the Carnegie Mellon® Software Engineering Institute's (SEI's) architecture-centric methods into the framework of the RUP.

The AUP is a simplified version of the Rational Unified Process (RUP). It describes a simple, easy to understand approach to developing software using agile techniques and concepts yet still remaining true to the RUP. The AUP applies agile techniques include test driven development (TDD), Agile Model Driven Development (AMDD), agile change management, and database refactoring to improve your productivity. The AUP product can be downloaded and installed free of charge. Version 1.1 was released on May 13, 2006.

This article shares a number of common pitfalls experienced by teams attempting to adapt the Rational Unified Process to their needs, presented with a little tongue-in-cheek.

As you may know, the Rational Unified Process®, or RUP®, is a widely used software process framework that can be tailored to your process needs and can accommodate other techniques. Scrum is a collection of interesting project management patterns used to wrap agile software projects. This article introduces some important characteristics of Scrum and presents techniques on how you can add Scrum ideas to your existing RUP environment.

we've written a light-hearted story of a successful project that actually reflects the experiences of multiple teams from multiple organizations. It illustrates how to apply the principles of iterative development and steer a project toward success and customer satisfaction. It also illustrates how project metrics play an important part in objective project tracking and control.

This compilation of three brief articles by IBM Rational thought leaders describes how the IBM Rational Unified Process, or RUP, is not only "agile" in its own right, but also encompasses much of the guidance teams need to scale agile techniques successfully.

This article gives an overview of OpenUP and explains how it relates to both RUP, from which it received its foundation, and agile methods, from which it incorporates their best practices.

This article explores all aspects of integrating the CMMI and RUP frameworks: why do it, how to get started, challenges to success.

This article provides some background on each best practice, in the context of current RUP adoption, as well as my own personal experience using RUP to manage software development projects. Each best practice is accompanied by suggestions on how you as a project manager can implement or integrate these RUP best practices into your own project.