This article originally appeared in the January 2003 issue of The Rational Edge E-zine on-line magazine, copyright 2002-2003 IBM and Max Wideman.

The Rational Unified Process (RUP) is a rigorous software development process advocated by the Rational Software Corporation.

The downloadable PDF file of the paper on this site is the one prepared by the Rational Edge editorial staff with the special assistance of Ms Marlene Ellin.

Published here Published here July, 2003.

PART I | Recap | A Simplified Overview of Traditional Contracting
The Acquisition Process with RUP | A Progressive Acquisition Solution for Contracting
Two-Level Contracting | Progressive Acquisition and the RUP Lifecycle
The Contractual Perspective | Advantages for Both Parties | PART III

Progressive Acquisition and the RUP Lifecycle

If the foregoing description seems like a linear or waterfall approach, it is important to understand how it relates to the RUP. Figure 3 shows how the first delivery maps into the RUP from the perspective of the acquirer.

Figure 3: Acquisition Lifecycle Leading to First Delivery
Figure 3: Acquisition Lifecycle Leading to First Delivery

Note that the acquirer and supplier negotiate the first set of deliverables as part of the initial overall contract determination. These are recorded in the first one or more CWOs.

If the chosen supplier proves to be unsuitable in the "first round," or if the specific value they bring becomes exhausted, then the acquirer can terminate the Head Contract with minimal losses in terms of time, cost, and progress. Otherwise, the parties can initiate each subsequent increment with a new CWO that focuses on the latest known technical requirements, without having to invoke a full traditional and legal RFP process. Instead, they can invoke a simplified and more efficient version of the first stage process that maps to the RUP, as shown in Figure 4.

Figure 4: Acquisition Lifecycle for Subsequent Deliveries
Figure 4: Acquisition Lifecycle for Subsequent Deliveries

The timing of each subsequent CWO negotiation is critical to the efficient conduct of work for both acquirer and supplier. The trick is for the supplier to avoid loss of momentum and the consequent additional effort that can result from gaps between CWOs. The Inception phase of the next delivery should overlap with the Transition phase of the current delivery, as shown in Figure 5.

Figure 5: Product Delivery Lifecycle for Progressive Acquisition
Figure 5: Product Delivery Lifecycle for Progressive Acquisition
Two-Level Contracting  Two-Level Contracting

Home | Issacons | PM Glossary | Papers & Books | Max's Musings
Guest Articles | Contact Info | Search My Site | Site Map | Top of Page