Sprintpunten

Sprintpunten (sprint points) are a unit of estimation used in Agile and Scrum to measure the relative effort, complexity, and risk of work items, typically user stories, within a sprint. They are commonly equated with story points and are not a direct measure of time or person-hours.

Teams assign points during backlog refinement and sprint planning using relative estimation techniques such as planning poker, where members estimate stories in comparison to a reference item, often using a Fibonacci-like scale (1, 2, 3, 5, 8, 13, 21).

A sprint's scope is determined by the team's capacity and the total points they can deliver in a sprint, which leads to velocity—the average number of sprintpoints completed per sprint over time. Velocity helps forecast how many backlogged items can be completed in future sprints or releases, guiding prioritization and planning.

Points reflect effort, complexity, and risk, not exact duration. They are influenced by team experience, technical risk, dependencies, and unknowns.

Criticisms include that points can be subjective and cross-team comparisons are not meaningful; they require anchoring to a common scale and consistent estimation practices, and they should not be equated with hours or used to measure individual productivity.

Best practices involve keeping a stable estimation scale, re-estimating when major changes occur, maintaining a predictable velocity, and limiting the sprint backlog to a reasonable number of points. Ensuring a cross-functional team is involved in estimation helps maintain consistency.

In Dutch contexts, sprintpunten are sometimes simply referred to as “punten” used for backlog sizing and may align with the English term “story points.”