APM is the new kid on the block. Its history stretches back a little more than 25 years. As recently as 2001, Agile software development was first codified through the “Agile Manifesto” (shown in the accompanying sidebar) put forth by Martin Fowler and Jim Highsmith.1 There were 17 signers of the original Agile manifesto.
THE AGILE MANIFESTO
“We are uncovering better ways of developing [products] by doing it and helping others do it. Through this work we have come to value:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiations
Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the left more.”
The Agile Manifesto has been the guiding principle in all APM models, including those discussed in this book. Most of the APM models originated with software development and, as a result, are based on very specific software development practices. Prototyping and the Adaptive Project Framework (APF) are the only APM models designed for use on any type of project. Prototyping is discussed in the Iterative PMLC model section of this chapter; APF is discussed in the Adaptive PMLC model section. I'll share several APM models in some detail and show you how they map into the Iterative PMLC model and the Adaptive PMLC model.
The bibliography in Appendix C has an extensive list of references ...