Opening the book…
Sample Questions
- During the Daily Scrum, each developer gives a status update to the project manager. The meeting takes 40 minutes and does not result in any adjustment to the team's plan. What should the Scrum Master do?
- Continue the meeting because status reporting is the purpose of the Daily Scrum.
- Coach the team that the Daily Scrum is for Developers to inspect progress and adapt their plan.
- Ask the Product Owner to assign tasks during the meeting.
- Cancel the Daily Scrum permanently.
- A stakeholder wants to add several new items to the current Sprint. What is the best Agile response?
- Add the items immediately because Agile welcomes all change.
- Ask the team to work overtime.
- Discuss the request with the Product Owner and evaluate impact on the Sprint Goal.
- Reject all changes until the end of the project.
- A team estimates a story as 13 points, but two Developers estimate it as 3 points. What should the team do?
- Average the numbers and move on.
- Let the manager decide.
- Discuss the difference to uncover assumptions and clarify the work.
- Remove the story from the backlog permanently.
- A team's velocity increased after the manager started comparing teams publicly. What is the most likely risk?
- The team has definitely become more productive.
- The team may inflate estimates or reduce quality to appear faster.
- Velocity is now more accurate.
- The team no longer needs retrospectives.
- A Product Backlog contains hundreds of outdated and unclear items. Sprint Planning is taking too long and Developers are confused about priorities. What should happen next?
- Start the Sprint anyway.
- Conduct backlog refinement and reorder items based on value and clarity.
- Move all items into the Sprint Backlog.
- Ask Developers to ignore the Product Owner.
- During the Sprint Review, the team shows slides instead of working product because the increment is not fully integrated or tested. What is the best response?
- Continue using slides because stakeholders only need a summary.
- Strengthen the Definition of Done so future increments are usable and inspectable.
- Cancel Sprint Reviews until the product is complete.
- Ask stakeholders to provide feedback without seeing anything.
- A Scrum Team keeps discussing the same problem in every retrospective, but nothing changes. What should the Scrum Master encourage?
- Stop holding retrospectives.
- Choose one specific improvement action and carry it into the next Sprint.
- Use the retrospective to assign blame.
- Ask management to write the retrospective notes.
- A team faces uncertainty about whether a third-party API can support a planned feature. What is the best Agile response?
- Build the entire feature and hope the API works.
- Create a timeboxed spike to investigate feasibility.
- Stop all development until the vendor guarantees success.
- Ignore the risk until the Sprint Review.
- A manager asks the Scrum Master to assign tasks to Developers to improve accountability. What should the Scrum Master do?
- Assign the tasks because the Scrum Master manages the team.
- Explain that Developers manage the Sprint Backlog and decide how to do the work.
- Ask stakeholders to assign the tasks instead.
- Cancel Sprint Planning.
- The team has many blocked items, but stakeholders are unaware of the delays. What would help most?
- Hide the blockers until the end of the Sprint.
- Create an impediment board or other information radiator to make blockers visible.
- Increase velocity targets.
- Add more work to the Sprint Backlog.
Answer Key
1. B. The Daily Scrum is not a manager status meeting; it is for Developers to inspect progress toward the Sprint Goal and adapt their plan.
2. C. Agile welcomes change, but the Product Owner and team should evaluate the impact on the Sprint Goal before adding it.
3. C. Large estimation differences reveal hidden assumptions, uncertainty, or missing information worth discussing.
4. B. Velocity should not be used to compare teams, since misusing it can distort behavior and reduce quality.
5. B. Backlog refinement improves clarity, priority, and readiness, supporting better planning and delivery.
6. B. Sprint Reviews should inspect real product progress, which a weak Definition of Done can undermine.
7. B. Retrospectives should lead to practical improvement, not repeated discussion without action.
8. B. A timeboxed spike is useful for research and reducing technical uncertainty.
9. B. Developers own the Sprint Backlog and decide how to accomplish the work; the Scrum Master coaches and removes impediments.
10. B. Information radiators improve transparency and help the team and stakeholders inspect problems quickly.
This page titled 4.4: PMI-ACP Style Sample Questions was last modified on Sun, 30 Aug 2026 23:53:31 GMT and is shared under a CC BY 4.0 license and was authored, remixed, and/or curated by Guharaman Janakiraman.
The book could not be loaded just now.