Abstract
Let’s get to it!
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Notes
- 1.
Sometimes a track might be a small team. I worked on a project where two programmers would couple with a single tester. The three developers would be working almost exclusively together. On that project we estimated the functionality that the whole trio could complete in a day/week worth of work. Two such mini-teams were working on a single track of functionality. We had three tracks at the peak.
- 2.
I worked with a new CTO some time ago and he announced that we were going to start estimating and delivering all projects with a precision of +/- 1 day. He was reasoning that if the airlines are able to schedule transcontinental flights with precision of minutes, we should be able to deliver 3–4-month-long projects with a precision of 1 day. The frequency of deployment to production was once every three weeks because of dependencies with marketing campaigns and with other departments. Even if we were able to forecast within 1 day of the actual delivery, it would bring small practical value.
- 3.
See Appendix A for more information about software development laws.
- 4.
Treating people with respect should be considered a project control. By planning around people’s needs instead of having people adjust their needs according to a forced plan, we improve the chances for a wholehearted commitment throughout the duration of the project.
- 5.
Definition of Done is a set of conditions that the team determines as sufficient for guaranteeing valuable software. For a more thorough description, please see here: www.scruminc.com/definition-of-done/
- 6.
As opposed to the artificial control people attempt to apply when escalating issues and amplifying the pressure days before deadlines.
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2020 Dimitre Dimitrov
About this chapter
Cite this chapter
Dimitrov, D. (2020). Forecasting Mechanics. In: Software Project Estimation. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-5025-9_5
Download citation
DOI: https://doi.org/10.1007/978-1-4842-5025-9_5
Published:
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4842-5024-2
Online ISBN: 978-1-4842-5025-9
eBook Packages: Business and ManagementApress Access BooksBusiness and Management (R0)