Content deleted Content added
follow order and name of article elements per MOS:SECTIONORDER |
Srich32977 (talk | contribs) Filled in 1 bare reference(s) with reFill 2 |
||
| (2 intermediate revisions by 2 users not shown) | |||
Line 1:
{{Short description|Software estimation based on data collection and analysis}}
{{Use dmy dates|date=October 2017}}
{{refimprove|date=October 2017}}
Line 9 ⟶ 10:
Most people, when estimating, measure the time they actually spend on a project – classic Time Accounting categories such as cited in McConnell's ''Software Project Survival Guide''<ref name="SPSG">[https://www.amazon.com/dp/1572316217 Software Project Survival Guide]</ref> do not allow for accounting for non-project activities. While McConnell goes on to include less obvious activities such as holidays, sick days and project support, he and most others identify such as activities to be separately recorded.
However, recording and attempting to budget for secondary activities often leads to political pressure to drop such activities. In practice, people find themselves unable to avoid them and compensate by working overtime. Similarly, as Spolsky points out,<ref name="EBS">
The key insight in evidence-based scheduling is that the only thing which needs measuring is the actual delivery of tasks. Over time, it is assumed that all other distractions will average out. For the purposes of estimation, variations due to interruption will show up as inaccuracies in estimation and will be compensated for by statistical analysis. The reasons for anomalies may come out if the organisation wishes to dig deeper into why people have irregular estimates.
| |||