in reply to Re^6: Beyond Agile: Subsidiarity as a Team and Software Design Principle
in thread Beyond Agile: Subsidiarity as a Team and Software Design Principle
Is that what you read?
You linked to a long document without giving pointers past that. Further, you lightly insult in your posts. I wanted to just close it right there, but i respect you enough to at least skim the first few pages, and that indeed was what i saw. It's there, and quite relevant to the discussion.
While the "requirements" change here, as you point out "even after the system became operational and throughout its 30-year operational lifetime" That's a revision, not a requirements change. That's a revisions after the initial version came out and after the original requirements already produced a product. Agile will not help you there.
Now, if they started coding for the shuttle before it was done, in anticipation of the years required to write and test the software, perhaps the requirements could not be finished ahead of time, unless done piecemeal. If that was the case, i could hear the argument that Agile might be a viable alternative to piecemeal.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^8: Beyond Agile: Subsidiarity as a Team and Software Design Principle
by BrowserUk (Patriarch) on Jul 23, 2015 at 18:37 UTC | |
by chacham (Prior) on Jul 23, 2015 at 18:44 UTC | |
by Anonymous Monk on Jul 30, 2015 at 00:28 UTC | |
by BrowserUk (Patriarch) on Jul 30, 2015 at 01:07 UTC | |
by BrowserUk (Patriarch) on Jul 23, 2015 at 18:49 UTC |