Guide Recommends Estimating Software Projects as Ranges Rather Than Single Figures

An article on DEV Community argues that software project estimates should be presented as a range rather than one precise number, since single figures conceal uncertainty and lead to disputes when schedules slip. It recommends splitting work into milestones, each given low, likely and high estimates in person-weeks, along with the assumptions behind them. The piece cites Steve McConnell's cone of uncertainty, which holds that early estimates can be off by up to fourfold and narrow as requirements and decisions firm up. It also suggests using the PERT formula to derive a planning figure while still showing clients the full range. An illustrative example for an invented field-service app demonstrates how milestone ranges sum to a total of 20 to 37 person-weeks, with a most likely figure of about 26.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in