Project Management Central

Please login or join to subscribe to this thread

Agile project management and traditional waterfall method of project management
Network:673



In the current world of agile project management is there a scope. for. traditional waterfall model of project management and if so, where and what are the scenarios when waterfall model is preferred than the agile methodology of project management.
Sort By:
Network:964



There is always a scope, the difference is in how you manage that scope. My experience is that environments that are 'governance heavy' favors a predictive approach.
Network:103



Waterfall works fine for more predictable projects. Agile works better for less predictable projects.
Network:1735



First of all, you can apply Agile approach with any project life cycle process, waterfall for example. Second, each time you will apply a way to do things (Agile, Lean, etc) you have to take into account the Solution to be create. Solution is equal "the thing" to be create plus "the process" to create it. Solution is a matter of business analisys and must be analyzed before a project/program/portfolio exists. It is done in an activity named "needs analysis". Just to put a real example on the table in my actual work place we have defined five different ways to do things, some based on Agile/Lean approaches and other in non-Agile approaches. To select one we have a checklist based on product/service/result characteristics plus a way to perform needs analsysis. The same person is assinged to more than one initiative that is using different approaches as project manager. Here comes the process we use to perform needs analsysis just in case it helps you: https://www.projectmanagement.com/blog-pos...-right-solution
Network:1275



Gurudeva -

Most projects fall somewhere in the continuum between purely predictive and purely adaptive. It is very rare to see a 100% pure waterfall project without some type of iterative activities occurring.

A simple example of a project which would lend itself to a waterfall approach is the update to a customer report based on a regulatory change. The requirements are 100% known up front and unlikely to change, the report has already been developed and all we are doing is making a few changes to it, and I can't deliver half a report so only a single release would work.

Kiron
Network:121



I concur with the comments above. I get a smile on my face when I see the ongoing discussion about 'waterfall' and 'agile'. Even before the agile era there where unpredictabilities while we only had 'waterfall'. We then talked about the delivery strategy, one of which I call the evolutionary delivery, now called agile. Not much new under the sun really.
...
1 reply by Sergio Luis Conte
Oct 13, 2018 6:23 AM
Sergio Luis Conte
...
That´s the point John. Waterfall and Agile are not matter of comparison. Waterfall is a life cycle process based on predictive life cycle model while Agile is a practice. As you mentioned unpredictability is always there no matter the life cycle you will use. People do not understand the use of word "predictive". Most of the people think "predictive" as synonim of "certain".
Network:811



I agree with John. The nature of work hasn't really changed, we just try to organize it differently and put different labels on it.
...
1 reply by Justus Nyamai
Oct 12, 2018 9:05 AM
Justus Nyamai
...
100% agree
Network:451



Oct 12, 2018 9:03 AM
Replying to Aaron Porter
...
I agree with John. The nature of work hasn't really changed, we just try to organize it differently and put different labels on it.
100% agree
Network:2481



Agile is not a silver bullet for all the projects. Cynefin provides a conceptual framework for making sense of the different landscapes faced within and by projects. You can find more details here: https://en.wikipedia.org/wiki/Cynefin_framework
Network:1735



Oct 12, 2018 8:08 AM
Replying to John A. Williams
...
I concur with the comments above. I get a smile on my face when I see the ongoing discussion about 'waterfall' and 'agile'. Even before the agile era there where unpredictabilities while we only had 'waterfall'. We then talked about the delivery strategy, one of which I call the evolutionary delivery, now called agile. Not much new under the sun really.
That´s the point John. Waterfall and Agile are not matter of comparison. Waterfall is a life cycle process based on predictive life cycle model while Agile is a practice. As you mentioned unpredictability is always there no matter the life cycle you will use. People do not understand the use of word "predictive". Most of the people think "predictive" as synonim of "certain".
Network:53



I'm not even sure there is an 'agile methodology of project management'. There's lots of agile development methods e.g. Scrum, XP. There's also PRINCE2 which is a project management methodology. Then there's the PMBOK Guide which is a project management standard.
In my opinion there's a lot of confusion between all these things. Agile helps teams communicate and collaborate efficiently. Methods such as PRINCE2 offers project management governance. The PMBOK Guide offers project managers a whole toolkit of techniques to use. In todays' world, project managers need an understanding of all these, along with knowing when and how to use them all together as is needed on a project. Having said that, all projects are different. I concur with some of the comments above in regard to some projects being more suited to either waterfall or agile.

Please login or join to reply

Content ID:
ADVERTISEMENTS

"It is impossible to travel faster than the speed of light, and certainly not desirable, as one's hat keeps blowing off."

- Woody Allen

ADVERTISEMENT

Sponsors