CAD CAD Agile Planning and Estimation Questions and Answers 2 — Questions and Answers
Question 1: During sprint planning, the team discovers that a high-priority user story has unclear acceptance criteria. What is the most appropriate action?
- Begin development and clarify criteria during the sprint
- Send the story back to the product owner for refinement before committing (Correct answer)
- Estimate the story with extra buffer time to account for unknowns
- Skip the story and move to the next sprint
Correct answer: Send the story back to the product owner for refinement before committing
Stories with unclear acceptance criteria should be refined by the product owner before the team commits to them in a sprint.
Question 2: What is the primary purpose of using Planning Poker in agile estimation?
- To speed up the estimation process by limiting discussion
- To leverage collective team knowledge and drive consensus through independent estimates (Correct answer)
- To assign story points based on lines of code
- To ensure the scrum master controls the estimation outcome
Correct answer: To leverage collective team knowledge and drive consensus through independent estimates
Planning Poker uses independent simultaneous estimates to leverage diverse perspectives and avoid anchoring bias.
Question 3: A team consistently completes 30 story points per sprint. The product backlog for the next release contains 150 story points. How many sprints should be planned for this release?
- 3 sprints
- 4 sprints
- 5 sprints (Correct answer)
- 6 sprints
Correct answer: 5 sprints
Dividing 150 total story points by the team's velocity of 30 points per sprint yields 5 sprints needed.
Question 4: Which estimation technique uses T-shirt sizes such as S, M, L, and XL to categorize work items?
- Wideband Delphi
- Affinity estimation
- Relative sizing (Correct answer)
- Ideal days
Correct answer: Relative sizing
Relative sizing uses abstract categories like T-shirt sizes to quickly group work items by perceived effort.
Question 5: What should a team do when their actual velocity varies significantly from sprint to sprint?
- Use the highest recorded velocity for future planning
- Average velocity over the last 3-5 sprints for more reliable forecasting (Correct answer)
- Set velocity targets and hold the team accountable
- Increase sprint length to stabilize velocity
Correct answer: Average velocity over the last 3-5 sprints for more reliable forecasting
Averaging velocity over multiple recent sprints smooths out variability and provides a more reliable planning baseline.
Question 6: In release planning, what is a key difference between a fixed-date release and a fixed-scope release?
- Fixed-date adjusts scope to meet the deadline while fixed-scope adjusts the timeline to deliver all features (Correct answer)
- Fixed-date releases never use story points
- Fixed-scope releases do not require velocity tracking
- There is no practical difference between the two approaches
Correct answer: Fixed-date adjusts scope to meet the deadline while fixed-scope adjusts the timeline to deliver all features
Fixed-date releases hold the date constant and flex scope, while fixed-scope releases hold features constant and flex the timeline.
During sprint planning, the team discovers that a high-priority user story has unclear acceptance criteria.
What is the most appropriate action?