There is a misconception about agile model with teams across the world. They create an iterative waterfall model and call it agile. In a traditional waterfall development, analysis of the entire project is done first, followed by design for the entire project, followed by coding and testing. In iterative waterfall, the same approach is followed, but each story is treated as a mini project. They do the analysis for one story followed by design, coding, and testing. This is not agile. They confuse both the model because they thrive to build an agile model without exactly considering its meaning. The incorporation of user stories, or treating it as short placeholders for future conversations; each story becomes a mini-specification document. Ideally, in an agile model, all types of work would finish exactly at the same time, be it analysis, design, coding or testing. It is not always possible to achieve this, but it should become team's goal. To know more, read the article by Mike Cohn (founder of Mountain Goat Software), at: https://www.mountaingoatsoftware.com/blog/an-iterative-waterfall-isnt-agile