2 ms·
Traditional waterfall would not be releasing every 4-5 weeks. Traditional waterfall would attempt to define all the requirements up front, freeze the specificat
by ams6110 12y ago
Traditional waterfall would not be releasing every 4-5 weeks. Traditional waterfall would attempt to define all the requirements up front, freeze the specification, then implement/test, then (in theory) the product is "done."
This sounds like some form of iterative/agile development, though perhaps not ideally managed. Standups are generally not 1 hour (but they are not part of waterfall at all).
An agile process can start to look like waterfall if you zoom way in. At some point you have to define what it is you're building, then build it, then QA it. Agile just does this in short cycles based on user stories, while traditional waterfall would attempt to define (as much as possible) ALL the requirements up front.
- viredfox 12y agoNormally we have a scope of what we want to do (ie. Let's redo the homepage and the login page). Then the product team group up and hash out the requirement, which is then sent to the developer. Although there are iterative changes in design, I actually don't know why the changes were made most of the time (they are not because of the implemented demo by the dev, the product team only starts seeing at the same time of QA)