Spike Quick programming exploration of an issue, to enable an estimate. Next release planned so it gives most bang for the buck. Do Actions 1 to 4. From high to low, or least labeled high, medium, and low. From high to low, or least labeled high, medium, and low.
Velocity is empirically determined.
If this is the first time, a reasonable guess is 1 story point per programmer per 3-week iteration. Choose Scope Choose stories for the next release. The total story estimates, divide by the velocity, tell how long it will take. Manage ongoing development. When one of the triggers occurs, react to it as shown.