Somewhere in between. We really have poor memory in technology field so the tendency is to go back and forth with what we learn and unlearn.
Take a processs framework that evolved from waterfall, for example and added the good parts of "agile" and extreme practices: RUP. In practice, what you have in RUP is iterations, at the end of which you get a "releaseable" increment of a product/system/solution. And in each of these iterations you do a little bit/refine everything by doind a little bit of all the disciplines that are part of the sdlc (requirements, analysis, design, code, testing). Sounds like anything you heard of ? It's been around since around the 2000s btw, and I remember it whenever someone complains about not having enough design, or requirement details during scrum sprints.
Somewhere in between. We really have poor memory in technology field so the tendency is to go back and forth with what we learn and unlearn.
Take a processs framework that evolved from waterfall, for example and added the good parts of "agile" and extreme practices: RUP. In practice, what you have in RUP is iterations, at the end of which you get a "releaseable" increment of a product/system/solution. And in each of these iterations you do a little bit/refine everything by doind a little bit of all the disciplines that are part of the sdlc (requirements, analysis, design, code, testing). Sounds like anything you heard of ? It's been around since around the 2000s btw, and I remember it whenever someone complains about not having enough design, or requirement details during scrum sprints.
I endorse this: