It is an interesting read, yet you fail to explain why Agile would be better than the older Waterfall/SDLC techniques. In fact, when you do Agile development, you're basically having smaller waterfalls. I've had to learn the "Cap Gemini SDM" methodology when I was young, decades ago. This method explains how development goes through several different phases, starting from a new idea all the way until it's implemented. And while it predates Agile methodologies with about 3 decades, (Agile is from 2001, SDM is from 1970) it is not obsolete! In fact, if you use Agile properly then you can still find these phases, but they happen in much smaller pieces. Any project starts with a bunch of ideas, where you just determine the goal for any functionality. You need to collect information and decide what is and isn't important. This would be the first phase. But instead of having one big piece of information, you would divide it in dozens of smaller bits and thus turn it into Agile. The next step would be defining each piece of information. In Waterfall, you would have a lot of stuff that need to be defined at the same time. In Agile, you just define dozens of smaller pieces. This continues for all the other phases, all the way to the operation and support phase. In classic Waterfall, users end up with large updates once every X months or so. With Agile, updates could be once every two weeks or even faster, as a new update can be done whenever a new feature was added. So, Agile is not a single, huge waterfall. It's just dozens of much smaller waterfalls that all cascade down into the final product. It speeds up delivery of new features, but it's still not that different. Many compare Agile with Waterfall and think they're opposites. That's not really the case, although Waterfall focuses on the whole project and each phase applies to the whole project. With Agile, you have phases per feature instead. And you basically start with Scrum or Kanban to put some new idea or feature on the board. Then you work it out further, start coding and then testing before the feature can be published. So, Agile still has flows. They're just a lot smaller than with classic Waterfalls. :)