Timeline for Is it true: use Agile methodology results less planning?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 12, 2017 at 7:31 | history | edited | CommunityBot | replaced http://programmers.stackexchange.com/ with https://softwareengineering.stackexchange.com/ | |
| Jul 18, 2014 at 5:32 | comment | added | InformedA | @Dunk what you said is true, but the point I want to say is that the 'cache' still helps because for things that are not the exact absolute same but very similar, you can still make your subjective decision to apply the 'cache' or not. In many cases, it helps doing it that way. | |
| Jul 17, 2014 at 20:20 | comment | added | Dunk | @random:Maybe there is some profession that covers almost everything. However, I can't think of one. Even construction projects which have been done hundreds of thousands of times usually end up having quite a few hiccups. About the only time things go smoothly is when building an identical thing that already went through the hiccups many times over before the system for developing that specific product had been developed. The problem with your "cache" those failures idea is that it only works if you are doing the same thing. Anything new will have its own unique issues that are overlooked. | |
| Jul 16, 2014 at 6:26 | comment | added | CsBalazsHungary | I can accept the answer, I feel like having less planning, but it is hard to summarize the planning time since it is very divided by time and it might add up to waterfall planning in sum if the project is big enough. | |
| Jul 16, 2014 at 6:24 | vote | accept | CsBalazsHungary | ||
| Jul 16, 2014 at 1:52 | comment | added | InformedA | @Dunk I would only add that some people in some profession can actually cover almost everything ahead of time. This often applies in hardware construction area, and they themselves have decades/centuries of doing trials and errors in the lab and/or with disastrous failures. At the end of the day, it's about how to 'cache' and 'compress' those failures into a knowledge base that can be organized, stored and retrieved easily (either in human brain or set of books, database, library etc..) | |
| Jul 15, 2014 at 17:45 | comment | added | Dunk | Re:"You need enough planning to be able to do a sprint without revisiting the requirements/user stories constantly. If this isn't happening, you aren't really using Agile appropriately." Even in Waterfall-like you are revisiting user stories and requirements constantly. To say that if you are revisiting then you aren't doing agile doesn't make sense. As you start designing/implementing user stories/requirements it always uncovers new questions. Nobody is omniscient enough to cover everything that could pop up ahead of time. | |
| Jul 15, 2014 at 16:22 | history | answered | enderland | CC BY-SA 3.0 |