Timeline for How does agile work when replacing a working system?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 3, 2017 at 5:58 | vote | accept | Steve Bennett | ||
| Feb 16, 2017 at 15:47 | comment | added | kenchilada | This is our approach. The problem with agile in our scenario is the legacy code is an inherited mess. It is impossible to size story complexity accurately when they heavily involve legacy. It is easy for the team to fail the sprint because of it. We're trying to determine how to deal with this in scrum. | |
| May 3, 2012 at 0:50 | comment | added | sleske | @SteveBennett: Yes, it does. That, of course, is a tradeoff. But the payoff is greatly reduced risk, and you only need to redo the part that needs redoing. | |
| May 3, 2012 at 0:19 | comment | added | Steve Bennett | Keeping parts of the old system running implies spending development effort on integrating with the old system, right? | |
| May 2, 2012 at 18:46 | comment | added | MarkJ | @pap Yes, agile (TM) has been hyped so hard there's a danger of blindly using one fixed methodology, without thinking about your own specific situation. | |
| May 2, 2012 at 14:25 | comment | added | pap | +1 for demonstrating that Agile may not be an ideal approach for certain kinds of real-life implementations. | |
| May 2, 2012 at 12:59 | comment | added | Michael Brown | +1 didn't even see your answer here before I said practically the same thing. Great minds and all ;) | |
| May 2, 2012 at 11:37 | history | answered | MarkJ | CC BY-SA 3.0 |