The Myth of the 'Waterfall' SDLC | Wiki | BAwiki
This is admittedly my interpretation, but I have tried to provide links to all of the source material I have used so that you can do your own research if you don't agree with my conclusions. Also known as: Phased Development, Plan-Driven Development, Specification-Driven Development, Cascade Model Introduction This is the 5th major version of this wiki article, and I thought it might be useful to provide a bit of introduction as to why I have written (and occasionally update) such a long article about a ‘discredited’ methodology like Waterfall. Several years ago, my employer started making efforts to formally adopt some Agile processes (Scrum at the time, DAD currently) for some project types. Wanting to educate myself more I started doing Google searches and reading what material I could find. So, I got curious. So I started researching Waterfall. So thus was born this article on ‘Waterfall’. You may not care about any of this. What is it? What's in a Name? Figure A A Tale of Two Waterfalls
The Waterfall Myth
"Waterfall" doesn't mean what you think it means |> Changelog
Editor’s Note: After publication, Kris joined us on Changelog & Friends to discuss this article, his dislike of the “tech debt” analogy, why documentation matters so much & how everything is a distributed system. Early reviews of that episode have included the words “great” and “awesome”… On Go Time #281, my Unpopular Opinion was about the software development method outlined in the waterfall paper. There was a brief exchange between myself and Johnny: Kris: So I read the “Waterfall” paper, and I will say that the method of doing engineering described in that paper is far superior to anything that we’re doing today.Johnny: I heard Waterfall is superior to all.Kris: That might be what you heard. The Unpopular Opinion segment of the show is a lot like No Nuance November, in that the opinions that are offered generally have deep truths to them, but we strip away that nuance to provide a quick soundbite that we can have our audience vote on. Background Production of Large Computer Programs 1.
There is No Such Thing as Waterfall - DaedTech
Don’t try to follow the waterfall model. That’s impossible. Instead, only try to realize the truth: there is no waterfall. Waterfall In Practice Today I often see people discuss, argue and debate the best approach or type of approach to software development. I saw a fantastic tweet earlier from Energized Work that said “Waterfall is typically 6 months of ‘fun up front’, followed by ‘steady as she goes’ eventually ramping up to ‘ramming speed’.” This is so psychically exhausting to the team that the only possible option is 3 months of doing nothing, er, excuse me, requirements and design phase for the next project, to rest. Diving into the Waterfall So, what actually happens during these phases, in a more detailed sense, and what right have I to be so dismissive of requirements and design phases as non-work? But the interesting part of this isn’t that people will tend to relax instead of “plan for months” but what happens when development actually starts. Whoah. The Take-Away
The Perennial Waterfall Strawman/Myth | Post Agilist
The Perennial Waterfall Strawman/Myth Just as the ‘abominable snowman’ never existed, and is merely used to frighten children from playing in the snow too long, “Waterfall” is just as nonexistent and is used by agile coaches as propaganda scare tactics to frighten developers into buying into Agile, Lean, kanban, or whatever the flavor of the month is in project management. Agilists constantly talk about ‘Waterfall’ in derisive terms, however we can get an idea what this mythical beast is like from the depictions of the Agilists. Waterfall requires absolute command and controlTasks are assignedTesting never happens until after the project is finishedThe customer is not involved until it’s too lateEverything must be done in strict phases, the phases must be horizontal in nature (eg, no UI gets done until ALL of the database is done, etc), and once a phase is complete it will never be modified in the futureA huge amount of upfront design is done before coding These are all myths. PostAgilist
The Father of Waterfall Isn't - The Ultimate Guide to the SDLC
👋 Hi, I’m Victor. How may I help you today? 👋 Hi, I’m Victor. How may I help you today?
