When I talk to people from software development industry about usage of agile practices vs. waterfall they always tell me agile (e.g., Scrum) is the standard in project execution, that there is almost never a reason not do to it. The only reason I hear for waterfall usage are projects that actually require waterfall usage by contract (e.g., government projects) or projects that cannot be done in iterations (e.g., writing software for fighter jet).
To get to the bottom of this I actually need your help. Are you working for a software development company? Do you practice Scrum (daily Product backlog, Scrum planning, Scrum meetings, Scrum review, etc.)? If you answered true to both then please leave a comment or message me or email me at firstname.lastname@example.org. More information bellow.
Some local universities sill mainly teach waterfall (from PMI's PMBOK). I'm Hawaii Pacific University student and I would like to change universities's computer science / information systems curriculum to include more of agile practices. In form of lectures and to use agile practices while working on group projects (many times during group projects we had enormous planning phase, documenting phase, and short development phase (which resulted in a low quality product)).
My research will compare Scrum agains waterfall practices in local Hawaiian software development companies. It will look into when Scrum is more appropriate to manage a projects and when waterfall is.
If you use Scrum or know a company that does, please contact me. You will help local software development community in term of receiving students with agile mindset when finishing their studies (or maybe waterfall if it turns out most local software development companies prefer waterfall over agile with Scrum).
For anyone not familiar with agile I recommend (reading all in following order):
- Website Agile manifesto