← Back to How do I write a step?
What is an Estimate?
Checked against GilbApp cd21a94.
An Estimate is the change a step or a Solution is expected to make on a Value or Development Resource, written before it is built.
It is written as the change on the Value's Scale from its Status, not as the end number, with a range, an Experience Level and the evidence if known. A step's Estimate stays as it stood once the step is delivered, so its Actual can be read against it. Example: the step Core.DayView is expected to move Usability.Find from 30 to 24 seconds, an Estimate of -6.
Deeper
Source: Kai-Zen.VTTRules.Cell (Each cell holds Estimate, then Actual ... Estimate from Status), .Estimate (Fill a step's Estimates before it is built); Kai-Zen.VDTRules.Unit (Estimate each impact as the change on the Value's Scale from Status), .Experience, .Evidence; GilbVeda t:ImpactActual ("The Estimate ... is the step's own t:ImpactOn cell, which the app locks once the step is Delivered ... so the Estimate the Actual is read against cannot move after delivery"); GilbApp af0f04ee planKinds.ts:296-301; published What is an Impact of a Solution? (It is an estimate until it is measured).