When it comes to project management, the methodology you use is of paramount importance. Regardless of scope, budget or resources, the management methodology employed is one of the key determining factors when it comes to project success or failure. Increasingly, companies are moving from a traditional waterfall approach to the Agile method, or fusing the two together. Is this right for you?
Cons of Agile
Before you look at fusing the two methods, be aware of the cons of Agile. While it is a highly versatile management method, it’s not perfect and it’s not ideal for all solutions. Some of the cons include:
Not ideal for large projects and teams
Not ideal for projects with relatively static requirements
Not ideal for situations where rigor is needed in project management and implementation
Cons of Waterfall
The waterfall management method, or “traditional” if you prefer, has been around for a very long time. It’s one of the most trusted out there, but it’s not ideal for all situations. For instance, you’ll find that it:
Is not ideal for small projects
Is not ideal for small task sets
Is not ideal as the only methodology, particularly in very complex, long-term projects
Fusing Waterfall and Agile
As you can see from the information above, both Agile and waterfall techniques have some drawbacks. However, they interestingly cancel each other out in many ways. Fusing the two together is a very good option, and is increasing in popularity, particularly in complex projects. In these instances, the best option is to use waterfall management as the overriding methodology, supplemented by Agile in different areas.
For instance, suppose you are the manager of a very large project, requiring more than one team (or a team and then a specialist team or subset of team members). That second or smaller team could operate on Agile principles in order to enjoy flexibility and continual re-evaluation as the project goes on, and to help them reach and complete tasks as needed.
This is not to say that waterfall and Agile should be fused all the time. To a large extent, the two are mutually exclusive. Combining the two should be done on an experimental basis with your own specific projects in order to determine which elements of each methodology provide you with the optimum return and best value at the end of the project.
Additional Considerations
Whether you’re merging Agile and waterfall methodologies or going more for Agile, it’s important that you understand what you’re in for. Remember – chances are good that management is not really going to understand what they’re asking of you. They have heard the benefits of Agile and want to improve things, but they’re unsure of what Agile really means.
In these situations, you need to be armed with a good understanding of this method, how it works, what it can offer and what it cannot provide. If necessary, you need to be prepared to inform management that Agile isn’t the right path for your project as well.