Is it advisable to strictly adhere to the traditional waterfall model instead of adapting to a modified waterfall model with slightly overlapping phases or an iterative model? Do organisations today even practice the waterfall model for SDLC? Saving Changes...
Sort By:
Michael WoodProject Manager / Business Analyst / Business Process Improvement Guru| Independent ContractorGig Harbor, Wa, United States
Of course it is a matter of risk but for my money a hybrid approach works best. At least it has for me over the past 30 years. Saving Changes...
Elyse NielsenSenior Project Manager| Ascension Health Information ServicesHaines City, Fl, United States
Hi,
Seems like these days there is a lot of dialogue of being all one way or all another way, I for one understand the need to standardize and minimize variation. However, there still remains the problem, if you only know how to use a hammer, all problems look like nails.
For project management, I would propose being methodology agnostic and use the techniques which work for the particular project. All projects are constrained by scope, time, and cost. Depending on which of the three is clearly know, really lays out the methodology one utilizes.
It also depends on what level of project management experience one has. Its like learning how to ride a bicycle, you are advised to hold handle with both hands but once you know how to ride it. You might as well ride it with single hand on Handle or probably none.
My advice would be to follow process in total integrity initially and if need be may be all the times but after a while you will understand yourself where to tweak it but your intentions should be loyal to a methodology. Saving Changes...
Working as a consultant has introduced me to many different industries and many different companies - all with their own way of doing things. One of the largest mistakes I've seen over and over again is when a department of company force a single methodology across the board. Each project is different. There is no "silver bullet" and one size does not fit all.
As a PM, i believe I have a toolkit with all sorts of tools (or methodologies if you will) in it - it's my job to determine which tools best fit the project.
When in doubt - go back to the basics. Waterfall is an SDLC method that works best when you can clearly define requirements. This can eliminate problems in the design and development phase while also enforcing discipline. Everyone is clear on scheduling and customer expectations. Does this sound like your project and environment?
The other thing to keep in mind is when you get right down to it, every other model is a variation of the waterfall - the method you use depends on the project, team members and company environment you work in.
