Author and entrepreneur Eric Ries unpacks the difference between waterfall and agile product development theories, and outlines when each are best employed. Waterfall – the linear path of product build-out – is best used when the problem and its solutions are well-understood. However, its hazard is that it can also lead to tremendous investment without guarantee of its success. Agile development, on the other hand, is a less-risky model of what can happen when the product changes with frequent user feedback and minimal waste. Without an authoritative solution clearly in sight, which is often the case of the startup, agile programming allows the growing enterprise to build-out quickly and correct itself often.
A Minimum Viable Product is, well, minimal. Agile focuses on building a rough version as fast as possible and then adding more and more until you have a polished final product. Your product will be ugly for a while. This is normal but is helpful to know this from the beginning.
One of the first questions that comes up when a team is introduced to scrum is the difference between a sprint and a waterfall. Traditional waterfall development happens from beginning to end in a sequence that’s easy to understand, and at first glance, agile sprints appear as if they’re simply shorter versions of the same workflow. Read the article