Timeline for Disadvantages of agile approach
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 29, 2015 at 19:02 | comment | added | Daniel | I don't think stackexchange's format lends itself well to digging into where agile might be beneficial in that example, so I just want to focus on the fact that I don't think this example shows a case where agile values are a bad fit. For example, I'm not sure that you can say that working alongside of the person who designs and builds the release clamps for the rocket would be detrimental to the project in favor of a very thorough SOW on the same piece. | |
| Apr 29, 2015 at 18:11 | comment | added | Sergey Kudryavtsev | In example below most of dependencies are not flexible, so even if it is easy to make change in software, re-assemble part of rocket will be much more harder. So "following a plan" more preferable than "responding to change", because in that kind of project should be no changes at all. And of course, if we talk about principles, nobody needs frequent deliveries, because launch time is fixed. And so on... This is just an example. But I would like to formulate general principles of projects, where agile is not applicable. | |
| Apr 29, 2015 at 18:03 | comment | added | Sergey Kudryavtsev | Thank you for your answer. I can show you an example of that kind of project: software development for carrier rocket. There are too many dependencies. Any change in the project will lead to a chain reaction of changes. So "contract negotiation" is more important then "customer collaboration". | |
| Apr 29, 2015 at 17:25 | history | answered | Daniel | CC BY-SA 3.0 |