Menu

0Comments

Top 20 Project Management Methodologies

Choosing the right project management methodology is essential. Here are the 20 most popular project management methodologies (PMMs) in practice today

Advertisement

Top 20 Project Management Methodologies

With the right project management methodology, project management offices (PMOs) can assist their organizations in improving business outcomes — but this requires more than recognising organisational priorities. For most companies, recent external forces such as COVID-19 and industry disruptions brought about by the pace of digital change have shifted company goals and priorities, making it necessary to re-evaluate whether the project methodologies they have in place can effectively and efficiently achieve new business goals while reducing risks

With so many different — and in some cases, overlapping — approaches to managing the complexities of any given project, how can you know which project management methodology is best? Here, we outline the most popular project management methodologies (PMMs) in practice today, comparing their focus and principles.

Top 20 project management methodologies

When considering these project management methodologies, it is important to note that there isn’t always a single solution in all cases, even within the same organization. The following table provides a brief snapshot of the focus of the 20 most popular project management methodologies, with the benefits — and drawbacks — of each defined more broadly below.

Methodology Focus
Waterfall A linear, sequential approach to development
Agile Continuous improvement and delivering better quality
Waterfall and agile hybrid Combines the best of waterfall for planning and agile for execution
Critical path method (CPM) Maximising project activities and finding the shortest path (timeline) to task and project success
Critical chain project management (CCPM) Optimising resource usage
Six Sigma Eliminating waste and improving processes and profitability
Scrum Delivering higher quality
Lean development (LD) Reducing waste while maximising output and increasing stakeholder value
Lean Six Sigma Customer-focused
Scrumban Reducing waste, lead time, and turnaround time, while delivering higher-quality products and services
Kanban Customer-focused, fostering ongoing collaboration and continuous learning
Event chain methodology Identifying, analysing, and managing any potential risks as early as possible in the project life cycle
Extreme programming (XP) Improving the quality and responsiveness of software as stakeholder needs change
Crystal Improving project results by focusing efforts on the people-side of projects
Feature-driven development (FDD) Addressing the complexities larger projects might pose by developing fast, repeatable processes
Dynamic systems development method (DSDM) Aligning projects with companywide strategic goals
Adaptive software development (ASD) Helping teams become more agile when dealing with change
Rapid application development (RAD) Focusing on user input based on testing, and how well a product is working compared to its intended goals
Rational unified process (RUP) Simplifying product development while reducing risk
Spiral Providing a risk-driven process model for more efficient product development

Waterfall

Waterfall is recognized as a traditional sequential methodology and has been a mainstay project management methodology for many years. It is used across many industries, but most commonly in software development. It comprises static phases (requirements analysis, design, testing, implementation, and maintenance) that are executed in a specific, linear order.

Advertisement

Waterfall allows for increased control throughout each phase. It offers a more formal planning stage that may increase the chances of capturing all project requirements upfront. It reduces the loss of any key information and requirements in the initial stages. One downside is that waterfall can be highly inflexible if a project’s scope changes after it is already under way.

Agile

Agile takes a significantly different approach to project management. It was initially developed for projects that require significant flexibility and speed, and it is focused on providing continuous improvement to delivering better quality solutions. To achieve this, agile is composed of short delivery cycles, aka “sprints.” Agile may be best-suited for projects requiring less control and more real-time communication within self-motivated team settings.

As a project management methodology, agile is highly interactive, allowing for rapid adjustments throughout a project. It is commonly used in software development projects in large part because it makes it easier to identify issues quickly and to make modifications early in the development process, rather than having to wait until testing is complete. Agile offers repeatable processes, reduces risk, allows for immediate feedback, provides fast turnaround, and reduces complexity. Drawbacks of agile include a greater time commitment needed from stakeholders when going through each iteration and potentially less documentation compared to waterfall.

Waterfall and agile hybrid

While many teams will favor either waterfall or agile, the benefits of both approaches can create a case for a hybrid project management methodology solution, one in which the planning and requirements phase is undertaken under a waterfall approach and the design, develop, implement, and evaluate phases follow the agile methodology.

Advertisement

Critical path method (CPM)

CPM is a step-by-step methodology used for projects with interdependent activities. It is focused on maximising project activities and finding the shortest path (timeline) to task and project success using a work-breakdown structure (WBS) and a timeline to complete, as well as dependencies, milestones, and deliverables. It outlines critical and noncritical activities by calculating the “longest” (on the critical path) and “shortest” (float) time to complete tasks to determine which activities are critical and which are not. One downside to CPM is that some teams may not always recognize the critical path, especially in larger more complex projects.

Critical chain project management (CCPM)

CCPM differs from CPM in that it focuses on the use of resources within a project instead of project activities. To address potential issues with resources, buffers are built in to ensure projects are on time and that safety is not compromised. It requires ensuring everyone is up to speed on critical chain and effort to gain buy-in into this methodology from all stakeholders.

Six Sigma

Six Sigma was originally developed by Motorola to eliminate waste and improve processes and profits. It is data-driven and has three key components:

  • DMAIC: Define, measure, analyse, improve and control
  • DMADV: Define, measure, analyse, design and verify
  • DFSS: Design for Six Sigma, which can include the previous options, as well as others, such as IDOV (identify, design, optimise and verify).

Six Sigma is sometimes debated as a methodology in the project management community. This methodology adds some potential rigidity that can stifle creativity or delay project delivery.

Advertisement

Scrum

Named after a play formation in rugby, Scrum is part of the agile framework and is also interactive in nature. “Scrum sessions” or “30-day sprints” are used to determine prioritised tasks. A Scrum master is used to facilitate instead of a project manager. Small teams may be assembled to focus on specific tasks independently and then meet with the Scrum master to evaluate progress or results and reprioritise backlogged tasks. Larger teams may have trouble adapting to Scrum and it can fail or be subject to scope creep, especially if all team members are not fully engaged and committed. To avoid duplication and confusion, roles need to be well-defined.

Lean development (LD)

Originally designed by Toyota, Lean was developed to focus on reducing waste while maximising output and increasing stakeholder value. While Lean got its start in the manufacturing industry, it is applied in various industries today because its focus is not sector-specific. Lean follows seven key principles: reduce waste, improve quality, share knowledge with others, remain in a state of continuous improvement, faster turnaround, removing silos, and maintaining an environment of respect. Lean relies on full stakeholder commitment, which can be problematic when stakeholders are reluctant to change or afraid of change. This can result in delivery inconsistencies.

Lean Six Sigma

This hybrid of Lean and Six Sigma focuses on the customer with the goal of improving business efficiency and effectiveness in identifying and understanding how the work gets done (the value stream). Lean Six Sigma strives to improve processes, remove unnecessary waste, and reduce defects, but it can be costly and time-consuming for companies to implement in-house.

Kanban

Kanban focuses on ongoing collaboration and fosters an environment of continuous learning and improvement. It uses visual boards and cards to help teams see tasks that are complete, in progress, and outstanding. All activities are based on being able to visualise daily tasks, carefully balance work in progress, and manage backlog. Overloaded or outdated boards, however, can create confusion or result in failure.

Scrumban

Scrumban provides product development and support teams with the best features from Scrum and Kanban. By combining Kanban’s pull system and Scrum’s backlog prioritisation and short cycles, teams are not only able to complete work quickly and effectively, but also improve processes by exposing areas of weakness. By leveraging the benefits of both frameworks, teams eventually reduce waste, shorten lead time, turnaround time, and deliver higher quality products and services. Geared toward larger teams, the success of Scrumban relies on a stable supply of products or components and team roles need to be well-defined.

Event chain methodology (ECM)

As an additional option to CPM or CCPM, ECM is focused on identifying, analysing, and managing any potential risks at the start of a project. The goal is to determine the chance of a risk becoming a reality, when it might strike, and what the impact might be to the project. There are six major principles that guide ECM: identifying a chain of events, identifying their timing and status, identifying critical events, mapping out or diagraming the chain of events, monitoring the chain of events performance, and quantifying the impact. Some teams may not recognise that an event can trigger an opportunity rather than just a potential problem.

Extreme programming (XP)

This methodology is intended to improve the quality and functionality of software as stakeholder needs change. XP uses short development cycles and requires constant collaboration, due to frequent releases. Advantages: XP can do wonders for productivity for a project team that needs a high production level. Teams are kept on their toes and find XP less focused and structured.

Crystal

As an agile approach, Crystal was designed by IBM as a way to improve project results by focusing efforts on the people-side of projects. Specifically the focus is placed on the skills, abilities, and collaboration of team members. Crystal is based on two core beliefs.

  • Teams are likely to identify and develop workflow improvements
  • Projects are unique, making it more likely that project teams are the most suited for determining how to do the work more effectively.

Crystal might not be suitable for some remote teams due to the need for close and frequent communication and brainstorming.

Feature-driven development (FDD)

Developed for larger-scale projects but applicable to projects of any size, FDD helps to address some of the complexities that larger projects might pose by developing fast, repeatable processes that can be accomplished in smaller spans of time by various teams throughout an organization. This approach follows some key processes that include developing an overall model, compiling a list of features, planning based on each of the identified features, designing the features, and building the features. FDD may not work best for smaller teams, and limited written stakeholder documentation may become an issue.

Dynamic systems development method (DSDM)

Developed as a way to align with companywide strategic goals, DSDM focuses on the delivery of proven business benefits. This approach focuses on eight key principles:

  • The need to stay focused on business requirements
  • On-time delivery
  • Collaboration is essential
  • Quality as a top priority
  • Building incrementally based on solid pillars
  • Using an iterative development approach
  • Using clear and ongoing communication
  • Maintaining control

Costly implementations using DSDM makes it less suited to smaller businesses.

Adaptive software development (ASD)

This approach works to help teams become more agile when dealing with change. Teams are encouraged to remain in a state of continuous learning in order to improve development. ASD is built on a three-phases, speculation, collaboration, and learning. ASD requires a significant amount of resourcing and higher costs making it more suitable for larger organizations.

Rapid application development (RAD)

RAD focuses on the user’s input based on testing, and how well a product is working compared to its intended goals. RAD first identifies the requirements, quickly builds prototypes and garners user input. Then based on the input, identifies requirements and builds prototypes again. User testing is then conducted and the final product is delivered. RAD is more complex and requires experienced and skilled team members seeking to deliver in shorter time frames.

Rational unified process (RUP)

RUP helps teams simplify product development and helps reduce risks. It works well in software development projects. It is similar to Waterfall, but RUP has four iterative phases: inception, elaboration, construction, and transition. Each stage involves regular and frequent stakeholder feedback while exploring ideas and defining requirements. One potential issue is, RUP is process-dependent and relies heavily on stakeholder feedback.

Spiral

Combines waterfall and an iterative mode to make it easier for teams to adapt. Spiral is divided into four stages: analysis, risk evaluation, execution, and planning. It works best for long-term and higher-risk projects. Within every stage there are multiple risk assessments and review processes. Spiral is costly and is less suitable for smaller projects.

Do you have a story that you think would interest our readers? write to us editorial@cio.co.ke

Advertisement