project management framework

When it comes to choosing a project management framework, project managers have various options. While some frameworks originated for general project management purposes, others were designed for specific use cases — such as in software development, IT governance structure or business process improvement. Some frameworks were designed for specific use cases but have since branched out into use with a broader variety of project types.

Traditional project management. A framework that draws from the Project Management Body of Knowledge (PMBOK) guide. PMBOK is designed around three phases of a project: inputs, tools and techniques, and outputs.

Agile. This framework, which relies on short delivery cycles, is often employed for projects where speed and flexibility are prioritized.

Lean. This framework focuses on reducing unnecessary waste in resources and optimizing processes for efficiency. Originated from Toyota’s manufacturing processes.

Critical chain project management (CCPM). This project management framework is more centered around the use and allocation of specific resources, as opposed to emphasizing timelines.

Critical path method (CPM). A step-Event chain methodology (ECM). This framework focuses on managing events — and chains of events — that affect the schedules of projects, Project headway. A work breakdown structure (WBS) framework built around Project Management Institute (PMI) standards that is offered only through PMI membership.

Integrated project method (IPM). An adaptive and incremental mode of project delivery. The IPM framework divides its core areas of focus into six areas:

• Management processes and functions
• Management deliverables
• Metrics
• Roles and responsibilities
• Reviews and sign-offs
• Techniques

PRINCE2. Involves a high degree of early stage planning. Originating from the U.K. government, where it is still used, this project management framework combines many proven practices from a variety of backgrounds and industries. It is commonly employed for IT projects.

Waterfall methodology. Sequential in nature, where work flows between defined phases and work stations. In the Waterfall model, work only moves to the next phase after completion of the previous phase; workflow in the opposite direction is generally discouraged.

Cynefin. A variant of the Agile framework designed Scrum. An Agile framework that is typically used for complex projects. Scrum places a focus on transparency, inspection and adaptation. Scrum encourages iterative progress, accountability and teamwork. Work is broken down into short “sprints.”

Extreme programming (XP). Another Agile variant. This framework emphasizes an incremental, iterative approach to product development with cycles of continual testing and revision. Extreme programming is primarily focused on business results.

Feature-driven development (FDD). A software development framework that utilizes shorter iterations and more frequent releases for projects. This framework encourages a customer-centric approach to development.

Dynamic systems development method (DSDM). Another Agile delivery framework. DSDM determines fixed time, quality and cost factors at the start of the project, and then prioritizes what the project must have, should have, could have and won’t have.

Adaptive software development (ASD). This software development framework embraces continuous adaptation to work processes as the norm.

Rational Unified Process (RUP). This framework divides development into four phases: inception, elaboration, construction and transition. Each of these phases involves its own cycle of modeling, analysis, design, implementation, testing and deployment. RUP is named after a division of IBM called Rational, where this framework originated.

Six Sigma. A data-driven framework that relies on the systematic measurement and analysis of quality, to bring the number of defects in the project as close to zero as possible.

Customer experience management (CEM). A framework that takes an “outside-in” approach to project processes, which are designed around specific, successful customer outcomes.

Information Technology Infrastructure Library (ITIL). A framework that helps coordinate IT functions to support the business. It helps identify, plan, delivery and support IT services.

COBIT PO10.2 (Control Objectives for Information and Related Technology). A framework that includes various components: an overall master plan, a resource assignment plan, defined deliverables, user approval, multiphase delivery, a test plan and a review process for the post-implementation stage.

Joint framework (COBIT + ISO17799 / 27001 + ITIL). A framework that combines ITIL and COBIT with ISO/IEC 27001 (the International Organization for Standardization‘s information security best practice code).

Kaizen. This is an approach that focuses on the continuous improvement of business processes. The premise of Kaizen is that small, ongoing changes produce substantial benefits.