Waterfall vs. Agile

Waterfall development starts with a set of requirements mandated from the top, then a sequential series of steps (design, construction, integration, and so on) leading to the product’s eventual release. The process emphasizes hierarchy and top-down management.

Agile development tends to emphasize independent, smaller cross-functional teams, working on products continuously, responding to change, and releasing software very frequently.

Unfortunately, if you have a process that is highly dependent on customer requirements and driven by top-down management, then, it is going to be hard to embrace Agile.

Scrum and daily stand-ups does not equal to Agile

Like what you read? Give Gopinath Jayaprakash a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.