4 ms·
I worked for a large corporation which used a hard core water fall method to produce software. And yet it called it Agile. Why? Because why not.
by asdkl234890 13y ago
I worked for a large corporation which used a hard core water fall method to produce software. And yet it called it Agile. Why? Because why not.
- donretag 13y agoI worked in a similar environment. Sprint 1 is requirements gathering. Sprint 2 is coding. Sprint 3 is testing. Water fall really is agile!
- collyw 13y agoI have noticed this. Every one claims to be doing agile, even though they pick and choose the parts they decide are "agile". I just continue to write software the way I always have. Kind of disciplined version of cowboy coding I would say. Sometimes I have design documents - when I feel it helps. Other times the problem might be less clear, built a prototype, and iterate from there. It really depends on the problem you are trying to solve and the time frame you need to do it in. I get software working, usually in a decent time frame. Is that not what agile is supposed to be about?