Timeline for How can you estimate time for tasks which primarily consist of figuring out a problem?
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Jan 22, 2019 at 22:13 | history | suggested | Glorfindel | CC BY-SA 4.0 | broken image fixed (click 'rendered output' to see the difference); for more info, see https://gist.github.com/Glorfindel83/9d954d34385d2ac2597bbe864466259f |
| Jan 22, 2019 at 8:21 | review | Suggested edits | |||
| S Jan 22, 2019 at 22:13 | |||||
| Apr 12, 2017 at 7:31 | history | edited | CommunityBot | replaced http://programmers.stackexchange.com/ with https://softwareengineering.stackexchange.com/ | |
| Mar 26, 2014 at 22:40 | history | edited | user40980 | CC BY-SA 3.0 | Add link to full article for cone of uncertainty. Add additional intro text. |
| Mar 26, 2014 at 18:37 | comment | added | user40980 | @Ptolemy either way - be it implementation or concept, its an estimate. I can estimate how long it will take such that I am 90% confident that the range covers what the end result will be. It may be a very wide range, but thats an estimate too - far too many people give estimates of "6-8 weeks" and then miss that estimate because it was too narrow - they gave a 30% confidence rather than 90% confidence. This deals with the skill at estimating, iterative refinements, and common pitfalls with estimating any task as those are the first skills necessary to work on to solve the problem. | |
| Mar 26, 2014 at 14:03 | comment | added | Michael Shaw | This answer is interesting and has a lot of merit, but is probably answering a question about estimating more implementation based tasks, rather than the question of how to estimate how long its going to take to have a brainwave.... | |
| Mar 24, 2014 at 1:25 | audit | First posts | |||
| Mar 24, 2014 at 1:26 | |||||
| Mar 21, 2014 at 23:13 | history | answered | user40980 | CC BY-SA 3.0 |