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 October, 2003.

PART IV | Recap | Progressive Acquisition Workflow
Specifying the Work | Selecting or Pre-Qualifying Suppliers
Making the Solicitation | Evaluating Submissions | Negotiating the Contract
Administering the Contract and Controlling the Supplier's Work
Terminating the Contract | Understand Progressive Acquisition
Appendix: Glossary of Terms for Progressive Acquisition

Progressive Acquisition Workflow

As you will recall, Part II described a two-level contracting approach consisting of a Head Contract and a series of Contract Work Orders (CWOs). Now we will look at some aspects of the primary contracting activities involved in developing the Head Contract and pursuing the CWOs. For readers who are familiar with RUP terminology, we can express the workflow, activities, and artifacts for the Head Contract and first CWO as shown in Figure 1.

Figure 1: Workflow, Activities, and Artifacts for Head Contract and First Contract Work Order (CWO)
Figure 1: Workflow, Activities, and Artifacts for Head Contract and First Contract Work Order (CWO)
(click for larger diagram - opens a new window)

For subsequent CWOs and the remaining project life span, we can express these things in a similar view, but we would modify the figure to look like the one in Figure 2. Note that most of the work associated with the Head Contract has been eliminated, and this workflow focuses specifically on the next CWO.

figure 2: Workflow, Activities, and Artifacts for Subsequent Contract Work Orders
Figure 2: Workflow, Activities, and Artifacts for Subsequent Contract Work Orders
(click for larger diagram - opens a new window)

However, our real goal is to help technical professionals talk to procurement personnel, so let us now discuss these aspects of contracting in the traditional terms of the contracting industry rather than in RUP terms. Indeed, some terms are used quite differently in these different contexts.

Throughout our discussion, we will view these aspects of contracting from the acquirer's perspective.

Recap  Recap

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