In Part I of this series, we identified the gap between the expectations of traditional procurement specialists and the realistic needs of the software
development community. We acknowledged that there is currently a fundamental disconnect between the legal practices concerning contracting and effective software development
practices, but that a new approach called "progressive acquisition" can help bridge that gap.
To prepare for a detailed discussion of progressive acquisition, in Part I we also developed a simplified acquisition scenario for discussion purposes and defined key terms. And finally, we looked at both the variables involved in contracting and the range of conventional contract types defined by the Project Management Institute.
Now, in Part II, we will describe how to modify the traditional contracting process to fit a progressive acquisition model that meets the needs of both acquirers and suppliers. Like the material in Part I, this material is based partly on the work of Mike Barnard, a Rational Unified Process ¨ expert in Rational's Vancouver office, and partly on what I have learned through years of experience on many projects.