How to Choose the Right Project Management Methodology

Professional projects are like snowflakes—no two are exactly alike. That’s where project management methodologies come in handy! Methodologies act like blueprints, providing a specific structure and outline for your project based on the tasks at hand. While project methodologies can be pretty complex, this guide will walk you through the basics by answering some of your most common questions.

[Edit]Steps

[Edit]What is a project management methodology?

1. It’s a template that helps you organize and maintain your project. Project management methodologies come in all shapes and sizes, but they have 1 common goal—to help your project run as efficiently as possible. Since there are countless types of projects out there, there are tons of methodologies to help you best manage your workload.^[1]
   

[Edit]What are some popular project management methodologies?

1. Waterfall: This methodology divides your project into specific segments that you follow in a specific order. Choose this methodology if you’d like to have a lot of control over each aspect of your project.^[2]
   
   • Waterfall methodology is best for static projects that aren’t likely to shift. Unfortunately, this type of methodology doesn’t adapt well to change, especially if the project’s focus shifts midway.
   • This methodology requires a lot of planning and preparation ahead of time, so your project runs smoothly.
   • If you’re designing a new hiking boot for a sports shop, you could use Waterfall methodology to create different project phases.
2. Agile: Not all projects thrive on a static, unchanging timeline. If your project’s scope and goals keep changing, an Agile process might be the best option. With this type of methodology, you’ll focus more on working with clients instead of ironing out a contract.^[3]
   • Think of your project like a boat—with an agile project methodology, the boat heads in a general direction, steering and adapting as needed as the project goals change and develop.
   • For instance, if you’re designing a new software program, an agile methodology would help you fix problems on-the-spot instead of following a structured plan.
3. Scrum: The Scrum methodology operates in “sprints,” or fast-paced segments of work. These sprints are usually 1-4 weeks long, and help outline a rapid timeline for your project. This methodology mainly decides when tasks get done—you and your team decide what gets done.^[4]
   • Each day throughout the sprint period, you and your team members can meet for 15-minute check-ins called “scrums.”
4. Kanban: The Kanban methodology revolves around creating a Kanban board—this is a whiteboard or digital bulletin board that keeps track of your project. On your board, divide your project into 4 columns: waiting, in-progress, completed, and blocked. Organize project tasks on your board, shifting them as the project gets completed. ^[5]
   • The “waiting” column collects your project’s backlog—try to format this in small, bite-sized tasks that are easy for team members to accomplish.
   • The “in-progress” column compiles tasks that are underway; once they’re done, these tasks are moved into the “completed” column.
   • If you can’t accomplish a task for some reason, move it into the “blocked” column, where you can get back to it later.
5. Six Sigma: You can take this methodology in 2 directions—improving low-quality products, or boosting products that were already optimized in the past. This is a great methodology for manufacturers, or any project centered around project quality.^[6]
   • The Motorola company originally created this methodology in 1993.
6. Lean: The Lean process hones in on 3 common types of waste: wasting resources (muda); uneven production (mura); and strained equipment and employees (muri). Lean methodology tries to get rid of these 3 “Ms” to make your project more efficient.^[7]
   • This methodology is popular for manufacturing businesses—in fact, the Toyota Production System originated it.

[Edit]What methodology is right for my project?

1. Pick a methodology that fits your project’s size and budget. Before you get your project up and running, brainstorm the possible risks and roadblocks you may encounter further down the line. Outline what your project will and won’t be covering, along with your estimated budget.^[8] Some methodologies, like Lean and Six Sigma, require a bigger budget to get going, and may not work for projects with tighter budgets.^[9]
   
   • If you work for a manufacturing company, your project scope might involve developing a new product as quickly and efficiently as possible.
   • If you work for a software firm, you might focus on rapid ways to develop new software.
2. Choose a methodology that fits your project timeline. Estimate how long your project will last—is it a matter of weeks, months, years, or something else altogether? Certain methodologies are designed for fast-paced projects, while others give you more wiggle room.^[10]
   • For instance, Scrum methodology accomplishes tasks in short, “sprint-like” periods. On the other hand, Waterfall methodology follows a very specific, structured timeline.^[11]
3. Factor in stakeholders and clients when choosing a methodology. Think about the big picture—are your clients and stakeholders looking for a fast turnaround time, or are they more concerned with efficiency? Outline a specific goal or objective for your project that will leave your stakeholders and clients satisfied.^[12]
   
   • For instance, Six Sigma methodology targets multiple aspects of a project, including production, development, marketing, administration, and more.

[Edit]Are there other methodologies I can choose from?

1. There definitely are, but some methodologies cater to certain industries. As the name suggests, the Adaptive Software Development (ASD) methodology is designed specifically for the software field. This methodology revolves around the possibility of change, and operates within 3 phases: speculation, collaboration, and learning.^[13] Package Enabled Reengineering (PER) methodology is geared toward product-based businesses, and helps you redesign an existing product from a brand new perspective.^[14]
   
   • The Extreme Programming (XP) methodology is another great option for software development.^[15]

[Edit]Can you combine project management methodologies?

1. Yes, you absolutely can. The Hybrid methodology combines and customizes different aspects of waterfall and agile methodologies that work best for your project. Similarly, the Lean Six Sigma meshes the quality-control focus of Six Sigma with the waste management angle of Lean Methodology.^[16]
   

[Edit]Tips

• In the UK, the Projects in Controlled Environments (PRINCE2) methodology is used the most. PRINCE2 focuses on best practices, and has its own training/accreditation course that you can sign up for.^[17]

[Edit]References

1. ↑ https://www.teamwork.com/project-management-guide/project-management-methodologies/
2. ↑ https://www.cio.com/article/2950579/how-to-pick-a-project-management-methodology.html
3. ↑ https://www.apm.org.uk/resources/find-a-resource/agile-project-management/
4. ↑ https://www.pmi.org/learning/library/agile-project-management-scrum-6269
5. ↑ https://www.cio.com/article/3441536/what-is-kanban-workflow-management-simplified.html
6. ↑ https://www.cio.com/article/3237692/six-sigma-quality-management-methodology.html
7. ↑ https://www.teamwork.com/project-management-guide/project-management-methodologies/
8. ↑ https://www.northeastern.edu/graduate/blog/identifying-project-management-strategies/
9. ↑ https://www.teamwork.com/project-management-guide/project-management-methodologies/
10. ↑ https://www.northeastern.edu/graduate/blog/identifying-project-management-strategies/
11. ↑ https://www.teamwork.com/project-management-guide/project-management-methodologies/
12. ↑ https://www.northeastern.edu/graduate/blog/identifying-project-management-strategies/
13. ↑ https://www.cio.com/article/2950579/how-to-pick-a-project-management-methodology.html
14. ↑ https://www.teamwork.com/project-management-guide/project-management-methodologies/
15. ↑ https://www.pmi.org/learning/library/managing-software-development-using-extreme-programming-7662
16. ↑ https://www.cio.com/article/2950579/how-to-pick-a-project-management-methodology.html
17. ↑ https://www.pmi.org/learning/library/project-management-methodology-knowledge-8258