- Types
- Top-Down Estimate
- Bottom-Up Estimate
- Estimation determines
- Estimation is based on
- The four basic steps in Project Estimation
- References
Types
- Analogous Estimating: Previous iteration
- Based on experience (2 - 2.5 days per feature for manual testing and automation)
- По трем точкам (best case, worst case, average case)
- Divide percent (collecting reqs, writing test cases, executing, retesting)
- Based on development team * 0.5
Top-Down Estimate
High-level chunks at the feature or design level are estimated and are decomposed progressively into smaller chunks.
Bottom-Up Estimate
This technique is used when the requirements are known at a discrete level where the smaller workpieces are then aggregated to estimate the entire project. This is usually used when the information is only known in smaller pieces.
Estimation determines
- Effort (time)
- Resource (people)
- Cost (money)
Estimation is based on
- Past Data/Past Experience
- Available Documents/Knowledge
- Assumptions
- Identified Risks
The four basic steps in Project Estimation
- Estimate the size of the development product.
- Estimate the effort in person-months or person-hours.
- Estimate the schedule in calendar months.
- Estimate the project cost in agreed currency.
