7.4: PMI-ACP Style Sample Questions

Sample Questions

1. A manager wants to compare two Scrum Teams based on velocity and reward the team with the higher number. What should the Agile coach explain?
   1. Velocity is a good way to compare teams because all story points are equal.
   2. Velocity should mainly be used by a team for its own forecasting, not for comparing teams.
   3. The team with lower velocity should be required to work overtime.
   4. Teams should increase story point estimates to improve velocity.
2. A customer submits a request on April 1, and the team delivers it on April 20. The team actively worked on it from April 10 to April 15. What does the April 1 to April 20 period represent?
   1. Cycle time.
   2. Lead time.
   3. Velocity.
   4. Throughput.
3. A team has many items started but few items completed. Team members are constantly switching between tasks. Which metric or practice should the team inspect first?
   1. Work in progress.
   2. Individual utilization.
   3. Number of meetings attended.
   4. Number of emails sent.
4. A burndown chart has been flat for several days during a Sprint. What is the best Agile response?
   1. Ask the team to work overtime immediately.
   2. Inspect the situation with the team to identify blockers or work that is not moving to done.
   3. Hide the chart from stakeholders.
   4. Cancel the Sprint Retrospective.
5. A cumulative flow diagram shows that the Testing band is widening over time. What does this most likely indicate?
   1. Testing is becoming a bottleneck.
   2. The team has no work to do.
   3. Velocity is automatically increasing.
   4. The Product Backlog is complete.
6. A team is unsure whether a third-party API can support the required transaction volume. What should the team do?
   1. Ignore the risk until development is complete.
   2. Run a timeboxed spike to investigate the API capability.
   3. Commit to the full solution without investigation.
   4. Remove all performance requirements.
7. A team is under schedule pressure. A manager suggests skipping testing to finish faster. What is the best Agile response?
   1. Agree because testing can always be done after release.
   2. Protect quality and inspect scope, risks, impediments, and tradeoffs.
   3. Remove the Definition of Done.
   4. Hide known defects from stakeholders.
8. A team has stable velocity, but customer complaints are increasing, lead time is getting longer, and defects are rising. What should the team conclude?
   1. Stable velocity proves delivery is healthy.
   2. Velocity alone is not enough, and the team should inspect flow, quality, and customer value.
   3. The team should stop collecting all metrics.
   4. The Product Owner should ignore customer complaints.
9. A team has repeated delays because it depends on another team for security review. What should the team do?
   1. Wait until the end of the release to request security review.
   2. Make the dependency visible and engage the security team earlier.
   3. Remove security review from the process.
   4. Blame the Developers for the delay.
10. A team has accumulated technical debt from rushed shortcuts. Delivery is slowing, defects are rising, and changes are becoming harder. What should the Product Owner and team do?
    1. Ignore technical debt because it is not customer-facing.
    2. Make technical debt visible and balance debt reduction with feature work.
    3. Increase WIP to deliver more features.
    4. Remove refactoring from the backlog.