Different project management approaches or methodologies will benefit different types of projects. A project management methodology is a collection of principles and procedures for managing projects from start to end.
Project management methodologies provide project managers with guidance on what steps to take, what tasks to complete, and how to manage the project. We’ll go over two different kinds:
Linear
Linear means you must complete the previous phase or task before the next can begin. A linear approach would be ideal for a project like building a house. You’d need the blueprint before you could start laying the foundation. You must know precisely how the house will look, its dimensions, and what type and how many resources you will require.
Then you have to finish the foundation before putting up the walls, the walls before putting up the roof, and so on until you have the finished project, which is a bungalow-style home.
There’s also a clear goal; you know exactly how the house will look.
It’s unlikely that your client will decide they’d prefer a multi-level Victorian over a single-level bungalow in the middle of construction.
Furthermore, even if they decided to alter their minds, it’s too late; the bungalow’s foundation and walls are laid. The bungalow will be given to them as requested.
Using the linear project management method, you complete each step in order, adhering to the agreed-upon specific results, and delivering what the client requested.
Iterative
For a project like creating a new show for a television network, on the other hand, it is more beneficial to use an iterative and flexible approach in which some tasks overlap or occur at the same time as other tasks are executed.
Your group develops a show concept and films a pilot. You conducted several pilot tests in various locations and time slots. Changes are made to the show as your team gathers feedback on the pilot. While the work on the final version of the show is ongoing, you can make decisions and begin working on other aspects of the project, such as hiring permanent actors, starting film production, and working on advertising.
And while the overall goal is clear: create a new show, the type of show produced may differ from the original concept. Your team may have started with a one-hour show, but testing revealed that a half-hour show would be more popular. Or perhaps a supporting character received a lot of positive feedback, so you want to elevate them to the main cast. More important is that you create a show that people will view.
Benefits of Iterative Process
Plans are adaptable due to the iterative process, and you can make changes as you go. Each of these projects benefits from a unique approach to task completion to best meet the project’s objectives. Linear projects have a straightforward sequential process and do not require many changes during development. If you stick to the plan, you should be able to complete your tasks on time and meet all other criteria.
Iterative projects allow for greater flexibility and predictability. You can test parts of the project to ensure they work before delivering the final result, and you can provide portions of the project as they are completed, rather than waiting for the entire project to be completed.
Over the years, project management has developed numerous methods from which project managers can choose to help them manage more effectively. You can use a hybrid approach to project management depending on the project requirements. Depending on the nature of the project, you can combine methods.
The following are two of the most widely used project management methodologies:
- Waterfall
- Agile
Waterfall
The waterfall methodology, which refers to the sequential ordering of phases, was developed in the 1970s. You work on one part of a project simultaneously, like a waterfall, starting at the top and working your way to the bottom. The Waterfall takes a sequential approach. Physical engineering disciplines such as manufacturing and construction used the Waterfall methodology. Still, as software became a vital engineering field, Waterfall was also applied to those projects.
It is still widely used in engineering fields such as product feature design and application design, also known as app design. Other industries, such as event planning and retail, have adapted Waterfall phases to fit their projects over time.
There are now numerous Waterfall styles, each with its own set of steps. They all have in common that they all follow an ordered series of steps directly linked to well-defined expectations, resources, and goals that are unlikely to change. Let us investigate further.
Waterfall project phases follow the same standard project life cycle flow that we discussed in our previous post. Initiating, planning, executing (including task management and completion), and closing.
When should you use the Waterfall methodology of project management?
When changes to the project are prohibitively expensive, you must complete tasks in order before starting another. For example, if you are running a catering event for a client on a shoestring budget, you should consider using the Waterfall methodology. This way, you can first confirm the number of guests, define the menu very clearly, get approval and agreement on the menu items and costs, order the non-returnable ingredients, and successfully feed the guests.
You can’t afford to make changes or waste food because your budget is limited. A client cannot change the menu after placing the order in a traditional method. As you know, the quantity and type of food preparation you can reserve tables, chairs, and dishes. A well-planned conventional approach to project management can help you achieve your desired outcome with as little pain as possible during project implementation.
You’ll set yourself up for success if you put in the extra effort to think through the entire project ahead of time. Following this approach, in an ideal world, will assist you in identifying the right people and tasks, planning accordingly to avoid any hiccups along the way, creating space for documenting your plans and progress, and enabling you to meet that goal. However, plans do not always go as planned. They rarely do. The Waterfall methodology includes some risk management practices to avoid and deal with Project changes.
Agile
Another popular project management approach is agile. Agility is the ability to move swiftly and efficiently. It also relates to adaptability, or the willingness and ability to change and adapt. Agile projects frequently have multiple tasks being worked on simultaneously or in various stages of completion, making it an iterative approach.
The concepts that would shape Agile methodology emerged in the 1990s in response to the growing demand for faster delivery of products, primarily software applications at the time. However, it was not named Agile until 2001. In general, the phases of an Agile project follow the project life cycle stages we discussed earlier.
However, rather than having to go in order or wait for one phase to finish before beginning the subsequent, Agile project phases overlap. Tasks are completed in iterations, referred to as sprints in Scrum. Scrum is an Agile methodology. Sprints are short periods, usually one to four weeks, during which a team collaborates to complete specific tasks.
What must be understood is that Agile is a mindset rather than a set of steps or phases. It is concerned with forming an effective, collaborative team that solicits regular client feedback to give the best value as soon as possible and make adjustments as needed.
When should you use the Agile methodology of project management?
Projects that are best suited for an Agile approach are those in which the client has an idea of what they want but doesn’t have a concrete picture in mind, or they have a set of qualities they’d like to see in the result but aren’t as concerned with the exact appearance. Another sign that a project could benefit from Agile is the high uncertainty and risk.
Building a website is an example of a project that would benefit from an Agile approach. Your team can make and deliver completed parts of the website in sprints to the client. As a result, you can launch the completed and ready part of the website for public viewings, such as the main homepage. Other features, such as the company blog or the ability to book online appointments, continue to be built out over time. Being agile allows the team to get early feedback on what works and doesn’t, make changes, and reduce wasted effort.
The Waterfall method, in this same website example, will plan for and require the entire website to be completed before it can launch.
Comparing Waterfall and Agile project management methodologies
Project manager’s role:
- Waterfall – The project manager acts as an active leader by prioritising and assigning tasks to team members.
- Agile – The agile project manager (or Scrum Master) primarily serves as a facilitator, removing any obstacles that the team may encounter. In managing their work, the team takes on more responsibility.
Scope:
- Waterfall – In the early stages of initiating and planning, project deliverables and plans are well-established and documented. Changes are subject to a formal change request process.
- Agile – Planning occurs in shorter iterations and focuses on delivering value as soon as possible. You can tweak the following iterations in response to feedback or unforeseen issues.
Schedule:
- Waterfall – Follows a primarily linear path through the project’s initiating, planning, executing, and closing phases.
- Agile – To organise time, use Sprints as periods. Each Sprint has a set duration and a predefined list of deliverables at the start of the Sprint.
Cost:
- Waterfall – Through careful planning and close monitoring, you can keep the costs under control throughout the project’s life cycle.
- Agile – Costs and timeline may change with each iteration.
Quality:
- Waterfall – At the start of a project, the project manager plans and defines quality criteria.
- Agile – By testing products in the field and implementing improvements regularly, the team solicits ongoing stakeholder input and user feedback.
Communication:
- Waterfall – The project manager communicates to stakeholders regularly about progress toward milestones and other key performance indicators to ensure that the project is on track to meet the customer’s expectations.
- Agile – The team is customer-focused, with consistent communication between users and the project team.
Stakeholders:
- Waterfall – To keep the project on track, the project manager constantly manages and monitors stakeholder engagement.
- Agile – The team is customer-focused, with users and the project team communicating regularly.
Key Takeaway
A basic understanding of Waterfall and Agile will assist you in determining the most effective way to organise and plan your project. Knowing about these two methodologies will help you stand out in future job interviews by demonstrating a deeper understanding of the project management landscape. Waterfall and Agile are two of the most well-known and widely used project management methodologies, but they are far from the only or best.
