Timeline for Quantifying the value of refactoring in commercial terms
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 31, 2012 at 17:19 | history | edited | SteB | CC BY-SA 3.0 |
Spelling fixes
|
| Oct 28, 2012 at 21:10 | comment | added | maple_shaft♦ |
@Ozz pitches will always be met with skepticism This is very true, and I would like to add that when one "pitches" an idea then you are giving the entirety of all decision making power on the people receiving the pitch, in other words, acknowledging that they have power over ultimate design and software implementation decisions. To get what you want in business you have to act as if you are in your right to own those decisions. Any sales or managers that have a problem with developers taking ownership of their responsibilities doesn't want top talent, they want people they can control.
|
|
| Oct 28, 2012 at 10:04 | comment | added | ozz | "bit at a time" is the most successful for me. Getting into long conversations trying to explain to sales people is useless 99% of the time. Big bang "we need a 2 week refactoring period" pitches will always be met with scepticism. | |
| Oct 28, 2012 at 10:00 | history | edited | SteB | CC BY-SA 3.0 |
Added graphical double-estimate example based on actual refactoring costs
|
| Oct 28, 2012 at 9:46 | history | edited | SteB | CC BY-SA 3.0 |
Added graph example
|
| Oct 28, 2012 at 9:39 | history | edited | SteB | CC BY-SA 3.0 |
Added double-estimate example
|
| Oct 28, 2012 at 9:27 | history | edited | SteB | CC BY-SA 3.0 |
Make refactorings part of development strategy
|
| Oct 28, 2012 at 9:21 | comment | added | SteB | @k3b Good point, I've added this as point 6 about technical debt. | |
| Oct 28, 2012 at 9:19 | history | edited | SteB | CC BY-SA 3.0 |
added 369 characters in body
|
| Oct 28, 2012 at 8:44 | history | answered | SteB | CC BY-SA 3.0 |