3 ms·
He wasn't advocating iterative methods in the agile sense, in fact he calls for "complete program design" before any analisys or coding, along with intensive do
by ricardobeat 15y ago
He wasn't advocating iterative methods in the agile sense, in fact he calls for "complete program design" before any analisys or coding, along with intensive documentation, planning, controlling and monitoring. An iterative approach to development drops nearly all of those.
The graphic where he shows cycles going back stages is used to exemplify failure, which he proposes to fix via the strict practices above.
- jt2190 15y agoOr, he could be advocating the most agile process that the technology of the time (1970) would allow. Remember that there were no desktop computers, no internet, the programming language C was just being created.
- ricardobeat 15y agoAgile processes don't depend on technology, just people, paper and communication, in fact technology can be a burden sometimes. Just in case someone from the future misunderstands this: I don't mean that agile drops analysis, documentation, planning or monitoring (they are essential to it) but it leaves the "intensive" and "before" parts out.
- MortenK 15y agoDevelopment processes very similar to todays "agile" family, existed back in 1970. "Evolutionary prototyping" for example (a member of the "prototyping" process-family), is one of the precursors for todays agile practices.