Estimating is the bête noire of software development: simple to conceptualise, but a mine-field for the unwary. There are multiple levels of problems involved with estimating: technical, theoretical, political, social, economic, which we will touch on in our tour.
The main take aways from this series is:
An appreciation as to why estimating is so hard in Software Development. We take a step-by-step approach to understanding the nature of the problem, and why it isn’t as easy as estimating other, simpler things.
How difficulty estimating impacts our work. Estimating is practically impossible, yet it is a cornerstone of Scrum. Alternatively, the “No Estimates” movement tries to go the other way and dismiss estimating completely. Here we try to reframe the problem as focusing on the wrong thing.
How we can get faster at development, despite the complexity. Some practical tools and advice for planning in the absence of reliable estimates.
Part of the 'Estimating' Risk-First Series, in which we look at straightforward extrapolation.
Part of the 'Estimating' Risk-First Series, where we look at exponential distributions in estimates.
Part of the 'Estimating' Risk-First Series, where we look at estimates with dependent, connected parts.
Part of the 'Estimating' Risk-First Series, where we look at estimating with uncertain boundaries.
Part of the 'Estimating' Risk-First Series, looking at how risk is apportioned when contracts are agreed.
Part of the 'Estimating' Risk-First Series, looking at the essential flaws in Scrums' time-boxing of work.
Add Your Star On GitHub to receive an invite to the GitHub Risk-First team.