Re:To the future occupants of my office at the MIT Media Lab
by ptx on Sunday August 16, 2020 @08:30AM
(#24177233)
> waterfall process ... keep working on it till it works
I thought waterfall was to plan it out in detail, then do all the work according to the plan despite realizing that the plan is wrong, then finally, after disbanding the development team, test it to see if it works?
That's obviously a caricature, but if you have the feedback loop to see if it works while you're working on it, you might also call it agile.
Re:To the future occupants of my office at the MIT Media Lab
by jki275 on Sunday August 16, 2020 @08:55PM
(#24182750)
You’ve described waterfall accurately, but waterfall is kind of an anti-pattern. Nobody actually uses it.
Re:To the future occupants of my office at the MIT Media Lab
by lmilcin on Sunday August 16, 2020 @11:07PM
(#24183470)
You mean there are no places where managers tell their teams the scope and deadlines and then tell the team to go play "agile"?
Re:To the future occupants of my office at the MIT Media Lab
by jki275 on Monday August 17, 2020 @08:14AM
(#24186467)
That's not waterfall.
Re:To the future occupants of my office at the MIT Media Lab
by lmilcin on Monday August 17, 2020 @09:43AM
(#24187124)
From that point of view I would say no project is waterfall. In any sufficiently complicated project requirements MUST change over development if only for the fact it is not feasible to specify absolutely everything absolutely precisely before development starts.
From a SWE perspective, Robotics Engineers need to know physics and math than the average SWE learns.
Interestingly almost all the successful robot projects I've worked on seem to follow a waterfall process. You keep working on it till it works. After its ready don;t change anything.