- Description
- An architect’s plan (cyanotype print)
- Source
- author not stated · original page
- Licence
- PD Public domain
In IT project delivery
Estimating, deciding, designing, understanding the need: project biases.
An IT project chains decisions made on estimates: how long, how much effort, what risk. This is where biases do the most damage, because feedback (“was the estimate right?”) arrives months later, when it is too late to learn.
Pages are arranged by the moment of the project where the bias strikes: estimating and planning, deciding whether to continue or stop, designing and reusing, understanding the client's need. For a first read, start with the planning fallacy.
Estimation and planningLead times, workloads and budgets: where optimism and arbitrary figures do the most damage.Decisions and steeringContinue, stop, choose: the biases that distort project trade-offs.Design and engineeringDesigning, documenting, reusing: the biases of the craftsman and the architect.Client relationship and the needUnderstanding the request and breaking work down: the biases that distort the need.
