Internal: Estimating Projects: Difference between revisions
John.meegan (talk | contribs) No edit summary |
John.meegan (talk | contribs) mNo edit summary |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 17: | Line 17: | ||
* '''Writing requirements documents''' -- if not already done | * '''Writing requirements documents''' -- if not already done | ||
* '''Coding''' | * '''Coding''' | ||
* '''Testing & Rework''' -- there’s no general rule for this. Sometimes changes take ages but are easy to test, sometimes they are small changes but take ages to test. One line of core code is very different to 100 lines of UI code. | * '''Testing & Rework''' -- there’s no general rule for this. Sometimes changes take ages but are easy to test, sometimes they are small changes but take ages to test. One line of core code is very different to 100 lines of UI code. | ||
* '''Documentation''' -- For Context Summary Help. | * '''Documentation''' -- For Context Summary Help. | ||
* '''Validation''' -- "release testing" at the end | * '''Validation''' -- "release testing" at the end | ||
Estimates need to take into account time to fix bugs that come back from testing and reviewing, not just time on the original issues. | |||
Latest revision as of 04:04, 9 March 2016
Estimating Projects
For one issue you’re almost never going to get it right, but for groups of work our estimates get better because if say 90% are done earlier than estimated, and 10% blow out, the overall amount is about right. So if you provide a “bit” of slack for each issue then you should be safe.
It is useful to group issues into 3 pools, then estimate issues individually based on these:
- Hard
- Medium
- Easy
Include estimates for:
- Writing requirements documents -- if not already done
- Coding
- Testing & Rework -- there’s no general rule for this. Sometimes changes take ages but are easy to test, sometimes they are small changes but take ages to test. One line of core code is very different to 100 lines of UI code.
- Documentation -- For Context Summary Help.
- Validation -- "release testing" at the end
Estimates need to take into account time to fix bugs that come back from testing and reviewing, not just time on the original issues.