In TOCICO 2016, we had talked about how “Agile” CCPM enables us to successfully complete challenging projects in a software development environment, while maintaining 100% DDP for years.
“Agile CCPM” in a nutshell:
“Agile CCPM” is an enhancement of the current TOC knowledge in the area of Critical Chain Project Management, employing a modified network construction process and buffer management method for software development. All the benefits and attributes of CCPM are maintained while building in the adaptability, responsiveness and autonomy of some of the practices adopted by Agile. None of the fundamental rules or benefits of CCPM are sacrificed. For this reason, the application enhancement is truly CCPM. It is agile, not in the sense that it is a hybridization of Agile and CCPM, but in the sense that it makes standard CCPM more adaptable to change. Other ways to describe this method could be “Responsive”, “Adaptive”, or “Flexible” CCPM.
About the project case study and its situation in the story:
The project was for a major upgrade of an existing software product, where some new technologies needed to be employed immediately – even though it made it more challenging for the developers – so that the competitive edge of the software product would be maintained both now and in the future. In the project, task duration estimation was extremely difficult, and only relative size estimation among features was known. Therefore, the development team decided to apply “Agile” CCPM instead of standard CCPM to the project. During execution the development team experienced several critical situations, extricated themselves from them, and completed the project on the due date without sacrificing scope, by taking necessary actions in a timely manner, following the steps of “Agile” CCPM.
(Presentation slides: PDF)