Three Project Estimation Reports for the price of two:
- Early Lifecycle Project Estimation
- Project Duration by Size and Effort
- Software Project Estimates – How accurate?
Early Lifecycle Software Estimation
Often, when a software project is simply an idea, you need to provide an indicative estimate of the possible cost and duration to provide an indication of whether the project idea is feasible. This paper describes an early lifecycle estimating technique that uses a combination of formulae and the ISBSG project delivery rate tables. Using the information in this paper you can produce an estimate range for the effort and duration of a proposed software development. Practical examples and the required tables are provided.
Project Durations by Size and Effort
Effort and duration are the two main factors that are sought from software estimation exercises. Customers for software want to know how long it will take to develop the software and how much it will cost. Cost can be derived once the effort is known.
This Special Analysis Report concentrates on project duration. The report provides useful information that can be used to obtain an approximate duration for a software project based on the known software size or effort; or to provide a “reality check” of an existing estimate of duration.
Software Project Estimates – how accurate are they?
We look at estimates of size, effort, duration and cost; how people have gone about estimating their projects; the accuracy of the estimates and the relationships between estimates. Here are some of the findings:
Size estimates are usually based on a data model; functional specification or analogy with a previous project
Project effort estimates are only accurate for less than a quarter of projects
Despite effort being poorly estimated 51% of projects were delivered on time
When functional size-based techniques are used for a cost estimate, the estimate is within 20% of the actual cost 90% of the time.