Timeline for When creating time estimates for features, is there a standard percentage to tack on for potential refactoring?
Current License: CC BY-SA 3.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 25, 2016 at 22:05 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Oct 30, 2016 at 21:48 | history | protected | gnat | ||
| Oct 26, 2016 at 21:22 | comment | added | Bradley Thomas | @DouglasGaskell The thing is, the refactoring is a bit of a red herring since it's an implementation detail that won't concern management. | |
| Oct 26, 2016 at 21:18 | comment | added | Bradley Thomas | @DouglasGaskell Well it is always expected, however inexperienced you are, that you can provide some kind of estimates... I understand it's a bit unrealistic for management to want a number if you feel you really have no idea, so the answer is to mitigate this mainly by (1) explaining the uncertainty as best you can, which you have done and (2) try to use analysis and research to formulate some accuracy as best you can. Even ask experienced people how long they think it will take you, if you have to. They'll need some idea of your skill level. I've added an answer below also. | |
| Oct 26, 2016 at 21:00 | answer | added | Bradley Thomas | timeline score: 1 | |
| Oct 26, 2016 at 20:40 | comment | added | Douglas Gaskell | @BradThomas I am definitely aware of that, I even brought it up, especially that in that cone is the best case scenario, when you have an experienced and expert estimator. Which I am not. Though it was kind of shrugged off as an excuse and I was asked what kind of timeframes I can provide again. The largest uncertainty for me is rewriting and refactoring, which I will be doing a lot of during the process as I'm new to the technologies being used. | |
| Oct 26, 2016 at 20:20 | answer | added | raghavendrasri | timeline score: 0 | |
| Oct 26, 2016 at 20:10 | comment | added | Bradley Thomas | @douglas see "Cone of Uncertainty" | |
| Oct 26, 2016 at 18:01 | answer | added | Doc Brown | timeline score: 1 | |
| Oct 26, 2016 at 18:01 | answer | added | Ewan | timeline score: -5 | |
| Oct 26, 2016 at 17:57 | answer | added | Becuzz | timeline score: 0 | |
| Oct 26, 2016 at 17:51 | history | edited | Robert Harvey | CC BY-SA 3.0 | deleted 18 characters in body |
| Oct 26, 2016 at 17:51 | comment | added | Robert Harvey | Why would something like this be a standard or typical? Every team is different. Some teams are better at estimation than others. Some teams build refactoring time into their original estimates. There's no way for us to know how much time your team will need for refactoring; ask them what their typical refactor time is. | |
| Oct 26, 2016 at 17:44 | history | asked | Douglas Gaskell | CC BY-SA 3.0 |