Opening the book…
Sample Questions
- A Scrum Master notices that Developers are waiting for her to assign tasks each Sprint. What should the Scrum Master do?
- Assign tasks efficiently so the Sprint can begin without delay.
- Coach the team toward self-organization and let Developers plan their own work.
- Ask the Product Owner to assign tasks instead.
- Escalate the issue to the department manager for task assignment.
- During a retrospective, the team says, "Everything was fine, we were just busy," even though the Sprint had several late-discovered defects. What is the most likely explanation?
- The team genuinely had no problems worth discussing.
- The retrospective format was too short.
- The team may lack the psychological safety needed to discuss real issues.
- The Scrum Master facilitated the retrospective poorly by asking too many questions.
- A team member says, "You always create bad estimates" during a planning disagreement. How should this statement be characterized?
- Constructive conflict, since it addresses a real performance issue.
- Unhealthy conflict, since it attacks the person rather than the work.
- Acceptable, since estimation accuracy is a fair topic to raise.
- Irrelevant, since conflict has no place in Agile teams.
- An executive frequently compares team velocity across departments and rewards the team with the highest number. What risk does this create?
- It encourages teams to deliver more customer value.
- It has no real effect on team behavior.
- It may encourage inflated estimates and discourage honest forecasting.
- It improves cross-team collaboration.
- A Developer privately believes an estimate is too low but says nothing because the team already committed to it in Sprint Planning. What does this scenario best illustrate?
- A healthy respect for team commitments.
- A gap in psychological safety that prevents honest re-estimation.
- Normal and expected Agile behavior.
- A sign that the Developer lacks technical competence.
- A distributed team frequently makes important decisions in side conversations between two members who happen to overlap in time zone. What is the main risk?
- The team is being efficient by avoiding large meetings.
- Remote team members may be unintentionally excluded from decisions.
- This has no effect since decisions eventually reach everyone.
- This is a normal and acceptable Agile practice.
- A team is in the storming stage of the Tuckman model, with frequent disagreements about priorities and roles. What is the best response from an Agile leader?
- Suppress the disagreement to restore a calm environment.
- Facilitate the conflict constructively and help the team focus on shared goals.
- Replace team members who are causing friction.
- Skip the Daily Scrum until tensions settle.
- A new Scrum team wants to stop holding retrospectives because "we already know what to improve." Using Shu-Ha-Ri, how should this be understood?
- This is appropriate Ri-level mastery, since the team already knows what to fix.
- This is a risky Shu-level shortcut, since the team hasn't yet built the discipline to understand why the practice matters.
- Retrospectives are optional in Scrum regardless of team maturity.
- This decision should be made by the Scrum Master alone.
- A Product Owner keeps accepting every stakeholder request rather than saying no, causing the Sprint Backlog to grow unmanageably. What is the underlying issue?
- The Product Owner is following good stakeholder engagement practices.
- The Product Owner may lack the support or confidence to prioritize and decline requests.
- This is acceptable since stakeholders should get everything they ask for.
- The Developers should decide which requests to accept instead.
- After a production incident, a team holds a review that starts with "How did this get through testing?" and "Who approved this?" What should happen next?
- Continue identifying who is responsible so accountability is clear.
- End the review early since blame has already been assigned.
- Shift to a blameless review focused on understanding system and process gaps.
- Escalate the incident to HR for disciplinary action.
Answer Key
1. B. Servant leaders coach teams toward self-organization rather than assigning tasks, since Developers own how Sprint work gets planned.
2. C. A retrospective that avoids real problems often signals the team lacks enough psychological safety to speak honestly.
3. B. Constructive conflict focuses on the work; attacking a person's character or competence creates fear instead of useful discussion.
4. C. Using velocity as a comparison or reward metric tends to encourage inflated estimates rather than honest forecasting.
5. B. Staying silent about a known estimation problem usually signals the environment doesn't feel safe for honest disagreement.
6. B. Side conversations that produce real decisions can quietly exclude distributed team members who weren't part of them.
7. B. Storming is a natural stage of team development, and leaders should facilitate the conflict constructively rather than suppress it.
8. B. Skipping a foundational practice before the team has internalized why it matters is a Shu-level shortcut.
9. B. A Product Owner who says yes to everything is often lacking the confidence or support to prioritize honestly.
10. C. A blameless review focuses on understanding what allowed a problem to happen within the system, surfacing more useful information than blame.
This page titled 6.4: PMI-ACP Style Sample Questions was last modified on Mon, 31 Aug 2026 10:38:49 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.