Relevant For:
- PMO leaders responsible for capability assessments
- Senior project managers implementing or adopting PMBOK processes
- Process improvement consultants mapping maturity to execution
- Organizations seeking to link project risk to process capability
Remarkable Points:
- Direct mapping between Capability Maturity Model, Project Management Maturity Model, and PMBOK knowledge areas
- Practical assessment approach that prioritizes usable processes over theoretical completeness
- Framework for baselining team process capability against project requirements
- Emphasis on adoption and use, not just documentation
Most Liked (As-Is Statements):
"A plan is only as good as the team's ability to execute it."
"Process capability must be measured in use, not in paper compliance."
Key Themes:
Theme 1: Capability Alignment
The central mental model reframes improvement as a matching problem. Projects demand specific process levels; the organization supplies capability. Value comes from closing the gap, not from generic maturity.
Theme 2: Usability Over Completeness
Wysocki privileges processes that are actually applied. He treats adoption as the true metric and shows how leaner, well-used processes outperform exhaustive but unused documentation.
Theme 3: Diagnostic Thinking
The book arms readers with diagnostic lenses: baseline, measure, and fit. These lenses convert vague improvement goals into targeted interventions tied to project risk.
Theme 4: Pragmatic Prescription
Recommendations are tactical and actionable rather than ideological. The approach favors iterative fixes tied to capability shortfalls and project milestones.
Final Remark:
Wysocki's work is not a how-to for creating immaculate process libraries. It is a clear argument for process economy and strategic alignment. The strongest contribution is a repeatable way to decide what process maturity is necessary for a given project and how to get teams to that point. Read it to refine judgment about when to invest in process and when to stop.
Good process is the difference between a plan that waits and a plan that happens.
Similar Books:
- A Guide to the Project Management Body of Knowledge (PMBOK Guide) by PMI
- CMMI: Guidelines for Process Integration and Product Improvement by Chrissis, Konrad, and Shrum
- Organizational Project Management Maturity Model (OPM3) by PMI
- Managing Successful Projects with PRINCE2