How to use the Story Point Calibration Tool.
Story points support relative team estimation, not conversion into universal hours. Compare unfamiliar work with agreed reference stories.
Make the workflow fit your task.
Compare the new work with the team's reference stories, discussing complexity, uncertainty and dependencies. Record the reasoning for a relative size and separate investigation when missing information prevents a useful comparison.
- What you provide
- Reference stories and team estimation scale.
- What you get
- Relative sizing discussion prompts without false precision.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Reference story A is 3 points; new work has similar implementation but uncertain data mapping.
Completed example
Discuss whether the mapping uncertainty changes size or warrants investigation before assigning a point value.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Can story points be converted into a universal hourly rate?
No. Their meaning depends on the team's conventions and reference work. Avoid comparing unrelated teams through the same point number.
Why do estimators disagree despite understanding the implementation?
They may be accounting for different risks or assumptions. Make those differences explicit before choosing a relative size.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑