<!---

This work is marked CC0 1.0 Universal.  To view a copy of this mark,
visit https://creativecommons.org/publicdomain/zero/1.0/.

--->

# Sprint Planning and Review

## Effort Estimation

:::{admonition} Guidance

Scrum masters **SHOULD** estimate each user story's
[level of effort](wiki:level_of_effort), with one (1) story point
being roughly equivalent to one (1) [work day](wiki:man-hour).

:::

Level-of-effort estimates scale following the
[Fibonacci sequence](wiki:Fibonacci_sequence), with thirteen (13)
points representing approximately two (2) work weeks total effort.
[Work cannot always be parallelized](wiki:The_Mythical_Man-Month), so
consider refactoring user stories larger than twenty-one (21) points
into smaller, more managable collections of work.  Ideally, the
project team can complete a user story in one or two sprints---a
[calendar month](wiki:elapsed_real_time) at most.

:::{table} Normalizing Story Points

| Work Amount | Story Points | Equivalent Activities  |
|-------------|--------------|------------------------|
| 1 day       | 1 point      | incident, task, commit |
| 2 weeks     | 13 points    | story, pull request    |
| 3 months    | 55 points    | feature, release       |

:::