DEV Community

Discussion on: Software development models and methodologies (Part 1)

Collapse
 
ghost profile image
Ghost

We have to be careful tho, Waterfall/Cascade sometimes is the only acceptable option, sometimes you can't deliver a constant stream of changes and the client is not interested in give feedback, specially in areas like embedded the product has to be finished when delivered, you can't have an important embedded system half baked, because of the cost of failure and because you'll not have a happy client if you are messing with production because you have to patch the system. They usually give you a window to ask all you'll need for your design and not much more after that, you have to be extra careful and thorough to collect all the requirements at first, each additional information request is not well received and the client will take it like a lack of preparation and a poorly planned design.

Not everything is web development. There are also other projects in which the MVP is on itself big, so it will look a lot less as agile and a lot more as waterfall. Rarely things are as black and white as agile promoters want to convince us, no methodology is a replacement to common sense, experience and good judjment. :)