Decoding Project Management Frameworks (Part 3): Your Essential Guide to PM Methodologies
- IPMA-SA
- Apr 23
- 6 min read
Project Management Frameworks
The project management process can vary depending on the industry you’re in or the size of your team. No two projects are the same, which is why there are different types of project management methodologies. The most common project management methodologies include Agile, Waterfall, Scrum, Kanban, PRINCE2, Six Sigma, Lean, and the Critical Path Method (CPM). To be good or maybe even the best project manager, it's essential to learn about each of these frameworks to find the one that best fits your team’s needs.
There's a lot of debate about which methodology or framework is the best. However, at IPMA-SA, we believe that either all methodologies are good or none are, meaning that every project is almost always unique. Therefore, using the same tool for every project might not be the best solution. Understanding the variety of tools available allows project managers to deliver better results. Large projects might even employ different frameworks for different areas of work. Just as you wouldn't build a house with only a hammer or saw, having and understanding different tools and their best uses gives you a much better chance of delivering value.
Just a heads-up: these methodologies and frameworks can sometimes be defined differently, and there's always a debate about which ones should be included in a list of project management methodologies. In this blog, we’ve (IPMA-SA) covered a selection that we believe are essential for anyone involved in project management. We're not suggesting this is an exhaustive list—there are many more methodologies and frameworks out there. Our aim is to introduce you to some key concepts to enhance your project management toolkit!
Agile
The Agile methodology is an iterative form of project management, often favoured by software development teams due to their rapidly changing project needs. Rather than tackling one large chunk of work, Agile focuses on smaller increments, allowing teams to quickly shift strategies if necessary. This ensures that changes are focused on what’s best for the end user. Agile is more of a project management principle than a strict methodology. It’s collaborative, fast and effective, iterative, and values individuals over processes. Agile teams often use specific methodologies alongside Agile principles, such as Scrum, Kanban, extreme programming, or Scrumban.
Waterfall Model
Waterfall project management is a linear process where each step of the project depends on the completion of the previous step. This model involves extensive planning before execution begins, ensuring all dependencies are accounted for. Often visualised in a Gantt chart, the Waterfall model connects each task by a dependency, meaning each task must be completed before the next one begins. While considered traditional by some, this approach is excellent for creating a predictable and thoroughly planned project plan, fostering clear communication throughout the process.
Scrum
Scrum is a subset of Agile methodology where teams use past experiences to influence future steps. In a Scrum team, the Scrum master guides teams through stages including Planning, Execution, Review, and Retrospective. Scrum involves short “sprints” that span one to two weeks, with teams of 10 or less. Unlike the Waterfall approach, Scrum is cyclical and relies on a Scrum master to lead daily meetings, demos, sprints, and retrospectives. Although Scrum is a methodology in its own right, it’s often associated with Agile due to shared principles like collaboration and valuing individuals over processes.
Kanban
Kanban is a visual project management method represented by Kanban boards, where work is displayed as cards in columns representing stages of progress. Cards are pulled from a backlog as they move through stages. Kanban helps Agile teams visualise workflows and project progress, reducing bottlenecks. It’s often used as a software tool that allows teams to drag and change boards seamlessly, but it’s not a requirement. The main idea is to keep the framework simple and focus on the most important tasks.
PRINCE2
Known as PRojects IN Controlled Environments, PRINCE2 uses the overarching Waterfall methodology to define project stages. Originally created by the UK government for IT projects, it’s still best suited for large IT initiatives. PRINCE2 principles include Starting, Directing, Initiating, Controlling, Managing product delivery, Managing stage boundaries, and Closing a project. These principles create a thorough project process and an effective enterprise project methodology, defining roles and streamlining tasks like controlling stages, managing product delivery, and initiating and closing projects.
Lean
The lean methodology aims to cut waste and create a simple framework for project needs, ultimately doing more with less to maximise efficiency and teamwork. Originally referring to physical product waste (a method dating back to Henry Ford and later Toyota and Motorola), it now addresses wasteful practices. Lean project management avoids the three Ms: Muda (wastefulness), Mura (unevenness), and Muri (overburden). Preventing these helps execute projects better and streamline processes, similar to the rational unified process (RUP), which focuses on reducing development costs.
Six Sigma
Unlike other project management methodologies, Six Sigma is used for quality management and is often described as a philosophy. It’s frequently paired with lean or Agile frameworks, known as lean Six Sigma or Agile Six Sigma. The Six Sigma DMAIC process—Define, Measure, Analyse, Improve, Control—creates a phased approach for continuous process improvement and defect elimination. The goal is to sustain, define, and control processes through continuous improvements by experts.
Critical Path Method (CPM)
The critical path method identifies and schedules critical tasks within a project, creating task dependencies, tracking goals and progress, prioritising deliverables, and managing due dates. This methodology aims to manage successful projects at scale, ensuring milestones and deliverables are correctly mapped.
Additionally good to know
IPMA Organisational Competence Baseline (IPMA OCB)
Project, programme, and portfolio management is crucial for many organisations. The IPMA Organisational Competence Baseline (IPMA OCB) helps assess and improve this competence. Rather than aiming for the highest level, organisations should focus on achieving the right level for their needs. The IPMA OCB outlines 18 organisational competence elements in five categories, essential for translating mission, vision, and strategy into results. It can be used for self-assessment and analysis, and serves as a valuable framework for discussing improvements.
The IPMA OCB, along with IPMA ICB and IPMA PEB, forms the foundation for IPMA’s Delta certification. Unlike maturity models, it doesn't prescribe specific methods or processes and can be applied across various fields.
IPMA Project Excellence Baseline (PEB)
The IPMA Project Excellence Baseline (PEB) is a global standard for defining project excellence, not just a framework. Drawing from the EFQM model, the PEB has been tailored for project and programme management, reflecting over 15 years of refinement.
Excellent projects and programmes are evaluated in three key areas:
People & Purpose: The foundation of project excellence, involving the right people led by excellent leaders who share a common vision for success.
Processes & Resources: Practices necessary for excellence through efficient and sustainable processes and resources, fostering innovation and continuous improvement.
Project Results: Outstanding, sustainable results for all key stakeholders, proving the excellence of the project management approach.
Project excellence is defined by achieving and aligning these three areas. The PEB provides a method to measure and assess excellence and guide projects towards continuous success.
The PEB can be used for self-assessment and benchmarking projects within an organisation, providing a basis for further learning and development. It is applicable across various fields and does not depend on specific methods or tools. The PEB also underpins IPMA’s Project Excellence Awards, an annual international competition recognising the best projects worldwide.
Project Management Institute’s PMBOK® Guide
The PMI’s Project Management Body of Knowledge (PMBOK® Guide) is more a set of best practices than a traditional methodology. It focuses on implementing five project management phases to manage projects from start to finish in a structured way. The five phases are project initiation, project planning, project execution, project performance, and project closure. While a solid foundation, the PMBOK® Guide isn’t as specific as other approaches, so you’ll need to decide which tasks to complete in each phase. It’s suitable for small teams on standard projects but should be paired with a detailed methodology like CPM for large teams handling complex projects.
Conclusion
The world of project management offers a variety of methodologies, each suited to different types of projects and teams. By understanding and leveraging these frameworks, project managers can select the best approach for their specific needs, ensuring successful project delivery. At IPMA-SA, we encourage project managers to explore and understand these methodologies to enhance their toolset and improve project outcomes.
At IPMA-SA, we pride ourselves on our agnostic approach, focusing solely on enhancing competences across project leadership, business, and management. Our commitment is to elevate skills and drive excellence, regardless of industry or methodology.
Are you already a member of IPMA-SA? Ready to learn more?
Join as an organisational member and get the most benefit for your organisation:
Join as an individual member and make the most out of it for yourself:
