Tips for selecting the right project management methodology

by Moira Alexander

Choosing the right project management methodology for the job is essential. There are so many; Agile, Waterfall, Scrum, and others. Our guide to evaluating project management methodologies will ensure you pick the perfect fit for your next project.

Choosing the right project management methodology for your team is the first step to success. But 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?

Project managers can assist their organizations in improving how they implement projects in the most effective and efficient way while reducing risks. But this requires much more than just recognizing organizational priorities. You have to have a deeper understanding of how each project management methodology can create the greatest positive impact — and how each can derail your organization’s likelihood of project success.

Here, we outline the most popular project management methodologies (PMMs) in practice today, showing you how to evaluate which is best for your project and organization. Once developed, a process for evaluating and choosing the right project management methodology can be documented and repeated, enabling your organization to spend less time haggling over how to structure and manage your projects and more time on achieving project objectives and deliverables.

The most popular project management methodologies today

There are many well-known project management methodologies to choose from like waterfall, agile, scrum, critical path, critical chain and more. Here’s what you need to know about each.

WaterfallWaterfall has been a mainstay project management methodology for years. It is sequential in nature and is used across many industries, most commonly in software development. It comprises static phases (requirements analysis, design, testing, implementation, and maintenance) that are executed in a specific order. Waterfall allows for increased control throughout each phase but can be highly inflexible if a project’s scope changes after it is already underway. It offers a more formal planning stage that may increase the chances of capturing all project requirements up front, reducing the loss of any key information and requirements in the initial stages.

Agile: Agile takes a significantly different approach to project management. It was initially developed for projects that require significant flexibility and speed. To achieve this, agile is composed of short delivery cycles, aka “sprints.” Agile may be best suited for projects requiring less control and 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.

HybridWhile 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.

Critical path method: Critical path method (CPM) is a step-by-step methodology used for projects with interdependent activities. It contains a list of activities and uses 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.

Critical chain project management: Critical chain project management (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.

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, analyze, improve and control), DMADV (define, measure, analyze, design, and verify), and DFSS (Design for Six Sigma). DFSS can include the previous options, as well as others, such as IDOV (identify, design, optimize and verify). Six Sigma is sometimes debated as a methodology in the project management community.

Scrum: Scrum is named after rugby, scrum is a part of the agile framework and is also interactive in nature. “Scrum sessions” or “30-day sprints” are used to determine prioritized 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 reprioritize backlogged tasks.

Other PMMs: In addition to the project management methodologies mentioned above, there are other PMMs to consider, including event chain methodology (ECM), crystal, feature-driven development (FDD), dynamic systems development (DSDM), adaptive software development, rational unified process (RUP), lean development (LD), Prince2 and others.

It’s important to note that there is no one solution in all cases, even within the same organization. Project management experience comes into play, and this is where a project manager’s knowledge of the pros and cons of each methodology can greatly assist organizations in successfully navigating projects in ways that allow them to maximize the potential for stakeholders.

How to effectively evaluate project management methodologies

project managers lean project management project manager traditional project management methodologies agile project management methodology right project management methodology project management methods comprehensive documentation customer collaboration project teams project life cycle project management body other project management methodologies agile project management waterfall project management waterfall methodology traditional project management methods extreme programming critical path methodology project management knowledge critical path project progress single project management methodology agile methodologies single project management methodology different project management methodologies software development life cycle project team project management method project management certification best project management methodology continuous improvement project management strategies adaptive project management agile approach project management skills contract negotiation responding scrum methodology tools working software entire project working software project process project methodology critical path analysis lean methodology quality management seven principles project stakeholders kanban methodology project management approaches short development cycles manufacturing industry agile method project's life cycle waterfall method contract negotiation project environment managing projects optimizing separate technologies project planning kanban method manage projects waterfall model uk government business processes project scope agile projects toyota production system traditional approach package enabled reengineering a few hundred employees critical tasks hybrid approach project progresses defined process developing software controlled environments management body of knowledge eliminating waste extreme programming xp six sigma dmaic process hybrid methodology agile frameworks helps manage workflow waterfall projects waterfall project how many stakeholders five process groups lean six sigma software quality time management software teams harvard business review project plans kanban board knowledge workers outcome mapping visual overview hybrid methodologies eliminate defects successfully completed separate technologies sigma dmaic process initially created business justification agile principles scrum framework scrum master one methodology seven processes improve performance agile teams physical waste lean principles task dependencies particular industries linear process minimize waste project plan team reports requires steady output sigma focuses wasteful practices short cycles too much strain reduce costs scrum teams project moving kanban boards kanban methods small projects work management raw materials kanban board view popular pm methodologies pm methodologies visual approach manage work strict deadlines traditional project management final product cut waste next task day to day activities body of knowledge pmbok scope creep best methodology seven themes same page self organizing well suited customer requirements steady output sticky notes resources needed easily manage team members pmp certification small team gantt charts five phases product introduction guiding principles team size c ontrolled e nvironments product owners team holds lessons learned next phase larger organizations makes sense sprint retrospective large scale previous one end user product delivery management processes due dates approach to project management adaptive project framework
The process required to assess, document, and select the right project management methodology for each project is detailed, time-consuming, and complex initially, but worth it in the end (assuming the most appropriate PMMs have been selected).

The Project Management Institute (PMI) has developed a globally recognized standard called the Organizational Project Management Maturity Model (OPM3). This assists organizations in identifying, measuring, and improving PM capabilities and standardizing processes. It helps solidify successful project outcomes, ultimately determines best practices, and strengthens the connection between strategic planning and execution. OPM3 focuses on overall organizational strategic effectiveness and incorporates project, program, and portfolio management. In 2013 it was recognized by the American National Standards Institute (ANSI) as an American National Standard.

Within its Implementing Organizational Project Management: A Practice Guide, PMI discusses high-level processes for tailoring PMMs that organizations should carefully evaluate and use to determine which methodologies work for various projects. Decisions should also be based on factors in the PMI Methodology Tailoring Process to maximize strategic benefits.

Benefits of Organizational Project Management

It may make sense for your business to adopt OPM3, given that a primary goal of OPM3 is to achieve successful strategic alignment and successful project outcomes depend heavily on such alignment. Organizations will need to include enterprise program management offices (EPMOs) in high-level planning sessions to ensure the right methodologies are deployed for specific projects to increase productivity and customer satisfaction, gain a competitive advantage, improve cost control and communications and predict performance. Ultimately, this will improve and expedite decision-making as well as support alignment with company-wide goals.

Because of the various strengths and weaknesses of each PMM, organizations may want to consider adopting multiple project management methodologies based on the unique nature of their project, organizational makeup, and project goals. Either way, organizations need to develop standardized best practices that can be refined as various factors change. Here, the key is to figure out how a specific project aligns with company-wide objectives. Once success or failure criteria can be isolated, it’s easier to find the most suitable methodology or methodologies that will enable your organization to effectively and efficiently reach the desired business result.

Key considerations in choosing a project management methodology

Whether you lean toward Scrum, Agile, Waterfall or other methodologies, throughout evaluating methodologies, here are just a few of the numerous factors that should be carefully considered:

  • Organizational strategic goals and core values
  • Key business drivers
  • Constraints
  • Stakeholders
  • Risks
  • Complexity
  • Project size and cost

The project management methodology assessment process

Once the assessment criteria have been factored into the decision, you need to develop a process to identify the best PMM option(s) for your specific project. This process will need to be revisited and modified from time to time to keep up with evolving business and stakeholder needs. Here are some general steps:

  1. Determine project drivers by identifying and weighing primary goals and priorities of the project.
  2. After determining project drivers, requirements and goals, identify all the criteria that a methodology will impact and vice versa.
  3. Identify all available/possible methodologies that are most relevant to the project.
  4. Spend time comparing and contrasting each PMM in relation to the project.
  5. Consider which methodology will yield the best results and offer the least risk.
  6. Gain feedback and buy-in.
  7. Document the methodology and rationale.
  8. Implement the methodology.
  9. Monitor and modify as required.

What to include in the project management methodology assessment

In organizational development, as well as within projects, this list of relevant assessment criteria applies. When it comes to selecting a methodology, these same criteria should also factor in. These can be broken down into internal and external criteria, with relevant subcategories for each.

Although the biggest risk factors are likely to fall within organizational capabilities and preparedness, any other criteria mentioned previously can create significant problems if they are in breach of a key project requirement.

As mentioned, PMMs are definitely not one-size-fits-all, even within the same company, project type, or industry. In one situation a specific methodology may work best, and in others, it may be more suitable to use a different project management methodology or even a hybrid approach. The same methodology is unlikely to work in the same organization on all projects; a best practice is to develop and implement a streamlined methodology assessment process (MAP) to determine the best approach for each project. Keep in mind this process itself may require reassessment and modifications as business factors change.


All content: Copyright 2018 by—IDG Enterprise Inc., 492 Old Connecticut Path, Framingham, MA. 01701.


Similar Content:

You may also like