Timeline for How does agile work when replacing a working system?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 2, 2012 at 21:02 | comment | added | aqwert | I was working somewhere where the orginal was shipped to market very quickly and therefore the design was pretty bad. We had the idea of starting over with a better idea of what to do and hopefully better code. It never went ahead which was for the best cause the cost to benefit was not viable. If the existing system works then make small improvements to it overtime. | |
| May 2, 2012 at 8:19 | comment | added | Murph | @KrisVanBael that's theoretically better (and definitely an ideal) but it's another of those "it depends" questions - some old solutions are really old (so one is looking at platform changes) or the process is wired/integrated into the system end to end and the "bits" can be rather large. | |
| May 2, 2012 at 6:01 | comment | added | Kris Van Bael | +1 that is exactly how we approached it. Although the whole idea of 'starting over' is very unagile. How hard have you tried considering to substitute the old solution bit by bit? | |
| May 2, 2012 at 5:07 | history | answered | aqwert | CC BY-SA 3.0 |