Scrum Refresher #4

Story Point estimation should only be done at the beginning of the project and should not change over time.

• TRUE

• FALSE

Answer explanation

Estimations should be revisited as needed, particularly during backlog refinement, to improve accuracy and account for changes.

Story Points estimate the exact amount of time required to complete a task.

• TRUE

• FALSE

Answer explanation

Story Points measure the relative effort, complexity, and uncertainty of a task, not the exact time needed.

The Scrum Master is responsible for assigning Story Points to user stories.

• TRUE

• FALSE

Answer explanation

Only the Development Team estimates Story Points since they are the ones doing the work.

Breaking down large user stories into smaller ones improves estimation accuracy and Sprint planning.

• TRUE

• FALSE

Answer explanation

Smaller user stories make estimation more reliable and help the team deliver incremental value more effectively.

A Scrum Team should commit to completing exactly the number of Story Points equal to their average Velocity in every Sprint.

• TRUE

• FALSE

Answer explanation

While past Velocity helps guide Sprint Planning, commitment should be based on team capacity and the nature of the work, not just a fixed number.

A team’s Velocity should always increase over time.

• TRUE

• FALSE

Answer explanation

Velocity naturally fluctuates based on work complexity, team availability, and external factors. An increase is not always expected.

If a team completes fewer Story Points than planned in a Sprint, they should analyze potential impediments in the Sprint Retrospective.

• TRUE

• FALSE

Answer explanation

The Retrospective helps the team identify blockers, process inefficiencies, or unrealistic estimations and make improvements.

A user story with 8 Story Points should take exactly four times as long to complete as a 2 Story Point user story.

• TRUE

• FALSE

Answer explanation

Story Points represent relative effort, not exact time. An 8-point story is more complex but not necessarily four times the duration of a 2-point story.

Story Points should consider only the development effort and ignore factors like testing and design.

• TRUE

• FALSE

Answer explanation

Story Points should include all effort required to complete the story, including development, testing, design, and reviews.

The Development Team should always estimate Story Points collaboratively rather than letting one person decide.

• TRUE

• FALSE

Answer explanation

Estimations should be a team effort to ensure diverse perspectives and more accurate assessments of complexity and effort.