APM Sprint Planning & Estimation 3

Question 1

During planning poker, two team members give estimates of 3 and 13 for the same story. What is the BEST next step?

Accepted Answer

Have both members explain their reasoning to align understanding

Answer

Large estimation discrepancies reveal different assumptions or knowledge gaps; discussion surfaces hidden complexity and builds shared understanding.

Question 2

What is the key difference between story points and ideal hours?

Accepted Answer

Story points are relative size measures; ideal hours estimate actual work time

Answer

Story points measure relative complexity and effort without specifying time, while ideal hours estimate actual work duration assuming no interruptions.

Question 3

A team's sprint planning session frequently runs over its 8-hour timebox. What is the MOST likely root cause?

Accepted Answer

The product backlog items are not sufficiently refined before planning

Answer

When backlog items lack clear acceptance criteria and refinement, teams spend planning time doing refinement work, causing sessions to overrun.

Question 4

What does 'velocity' measure in agile sprint planning?

Accepted Answer

The average amount of work a team completes per sprint, measured in story points

Answer

Velocity tracks completed story points per sprint and serves as a planning benchmark for how much work the team can realistically commit to.

Question 5

A new team member joins mid-project. How does this affect sprint planning?

Accepted Answer

Capacity may increase but velocity may temporarily decrease due to onboarding overhead

Answer

New team members add capacity but their onboarding reduces existing members' productivity, so velocity may dip before improving.

(APM) Agile Product Management Certification Practice Test

(APM) Agile Product Management Certification Practice Test

APM Sprint Planning & Estimation 3