100 full PSM-style questions + answers in one go would be extremely long and hard to use effectively (and it also becomes less useful for learning because it’s just a wall of text).
Better approach: I’ll give you 4 high-quality sets of 25 questions (100 total), progressively increasing difficulty, like the real Scrum.org PSM exam.
Here is PART 1 (25 PSM-style questions + answers).
1. What is Scrum based on?
Answer: Empiricism and Lean thinking.
2. What are the three pillars of empiricism?
Answer: Transparency, Inspection, Adaptation.
3. Who is accountable for maximizing product value?
Answer: The Product Owner.
4. Who owns the Sprint Backlog?
Answer: The Developers.
5. What is the purpose of the Daily Scrum?
Answer: Inspect progress toward Sprint Goal and adapt the plan.
6. Who facilitates the Daily Scrum?
Answer: The Developers.
7. Timebox of a Daily Scrum?
Answer: 15 minutes.
8. Can the Scrum Master attend the Daily Scrum?
Answer: Yes, but as an observer or coach, not facilitator.
Answer: A timebox where a usable Increment is created.
10. Can a Sprint be cancelled?
Answer: Yes, by the Product Owner.
11. Who can cancel a Sprint?
Answer: The Product Owner.
12. What is the Sprint Goal?
Answer: The single objective for the Sprint.
13. Who defines the Sprint Goal?
Answer: Developers and Product Owner collaboratively.
14. What is an Increment?
Answer: A usable, potentially releasable product outcome.
15. What is Definition of Done?
Answer: Shared quality standard for Increment completeness.
16. Who creates the Product Backlog?
Answer: The Product Owner.
17. Is the Product Backlog ever complete?
Answer: No, it is always evolving.
18. What happens in Sprint Planning?
Answer: Sprint Goal is defined and work is selected.
19. Timebox of Sprint Planning?
Answer: Up to 8 hours for a 1-month Sprint.
20. What is the main output of Sprint Planning?
Answer: Sprint Goal and Sprint Backlog.
21. Who participates in Sprint Review?
Answer: Scrum Team and stakeholders.
22. Purpose of Sprint Review?
Answer: Inspect Increment and adapt Product Backlog.
23. Purpose of Sprint Retrospective?
Answer: Improve team process, behaviour, and system.
24. Who participates in Retrospective?
Answer: Scrum Team only.
25. What is Scrum Master accountable for?
Answer: Ensuring Scrum is understood and enacted.
PART 1 SUMMARY (Agile Coaching Insight)
These questions test:
Here is PART 2 (26–50) of PSM-style questions + answers (intermediate level, more exam-trick focused like Scrum.org exams).
26. Can Developers change the Sprint Backlog during the Sprint?
Answer: Yes, they can update it at any time.
27. Who is accountable for the Sprint Backlog?
Answer: The Developers.
28. Does the Scrum Master assign tasks?
Answer: No.
29. Who is responsible for managing the Product Backlog?
Answer: The Product Owner.
30. Is the Product Owner allowed to delegate backlog management?
Answer: They may delegate, but remain accountable.
31. What is the primary measure of progress in Scrum?
Answer: A Done Increment.
32. Can incomplete work be released?
Answer: No, only Done Increments can be released.
33. What is the purpose of a Sprint?
Answer: To deliver a usable Increment aligned to a Sprint Goal.
34. Who decides what to work on during the Sprint?
Answer: The Developers.
35. Can scope be changed during a Sprint?
Answer: Yes, as long as Sprint Goal is not compromised.
36. Who owns quality in Scrum?
Answer: The entire Scrum Team.
37. What happens if Definition of Done is not met?
Answer: The work is not considered an Increment.
38. Is velocity a required Scrum metric?
Answer: No.
39. What is velocity used for?
Answer: Forecasting, not performance measurement.
40. Who can attend the Sprint Planning?
Answer: Scrum Team.
41. What happens if the Product Owner is absent in Sprint Planning?
Answer: Sprint Planning is incomplete and should not proceed effectively.
42. What is the Scrum Master’s role in Sprint Planning?
Answer: Facilitate Scrum understanding and ensure event happens effectively.
43. What is the outcome of Sprint Review?
Answer: Feedback and updated Product Backlog.
44. Is Sprint Review a demo?
Answer: No, it is a collaborative inspection.
45. Who decides what is “Done”?
Answer: The Scrum Team defines Definition of Done.
46. Can Definition of Done change?
Answer: Yes, but only to increase quality standards.
47. What happens if multiple teams work on the same product?
Answer: They should align on a shared Product Backlog and Definition of Done.
48. What is the main goal of Scrum Master?
Answer: To enable Scrum effectiveness in the organization.
49. Is Scrum Master a management role?
Answer: No.
50. What is the difference between Scrum Master and Project Manager?
Answer: Scrum Master coaches and enables; Project Manager directs and manages delivery.
PART 2 SUMMARY (Agile Coaching Insight)
This set tests:
Next step:
👉 PART 3 (51–75): advanced + trick questions (exam-level thinking traps)
👉 includes: Sprint cancellation scenarios, PO authority traps, Scrum Master influence limits, team autonomy edge cases
Here is PART 3 (51–75) of PSM-style questions + answers, designed to reflect advanced Scrum thinking, ambiguity traps, and real exam-level reasoning aligned with Scrum.org.
This is where questions become less “definition-based” and more scenario + mindset based.
51. Who decides when a Product Backlog item is ready for Sprint?
Answer: The Developers, based on their understanding of capacity and readiness.
52. Can the Scrum Master stop Developers from working on a chosen Sprint Backlog item?
Answer: No.
53. Who is accountable for ensuring Scrum is understood?
Answer: The Scrum Master.
54. Who is responsible for stakeholder management?
Answer: The Product Owner.
55. Can stakeholders attend Sprint Planning?
Answer: No, only Scrum Team members.
56. What is the main purpose of Sprint Retrospective?
Answer: Improve effectiveness of the Scrum Team.
57. Who owns the Sprint Goal after it is created?
Answer: The entire Scrum Team.
58. Can Developers add new work during the Sprint?
Answer: Yes, as long as it supports the Sprint Goal.
59. What happens if the Sprint Goal becomes obsolete?
Answer: The Product Owner may cancel the Sprint.
60. Who decides Sprint cancellation?
Answer: The Product Owner.
61. Is Sprint cancellation common practice?
Answer: No, it is rare.
62. Who is responsible for technical practices?
Answer: The Developers.
63. Can the Scrum Master define technical solutions?
Answer: No.
64. What is the role of Scrum Master in conflict?
Answer: Facilitate resolution, not impose solutions.
65. What is the best measure of Scrum success?
Answer: Value delivered through a Done Increment.
66. What is empiricism in Scrum?
Answer: Making decisions based on observation and experimentation.
67. What are the three Scrum pillars?
Answer: Transparency, Inspection, Adaptation.
68. What happens during Sprint Review?
Answer: Inspect Increment and adapt Product Backlog based on feedback.
69. Who prioritises the Product Backlog?
Answer: The Product Owner.
70. Can Developers refuse Product Owner priorities?
Answer: They may negotiate during Sprint Planning but not override Product Owner accountability.
71. Who is accountable for delivery of Increment?
Answer: The Developers.
72. What is the Scrum Master accountable for in organisational context?
Answer: Removing impediments and enabling Scrum adoption.
73. Is Scrum a process or framework?
Answer: A framework.
74. Can Scrum be changed?
Answer: Yes, but changes must preserve Scrum theory.
75. What is the purpose of Sprint Backlog?
Answer: To plan work needed to achieve Sprint Goal.
PART 3 SUMMARY (Agile Coaching Insight)
This section tests:
role boundaries under pressure
decision authority clarity
Sprint cancellation logic
Scrum Master limitations
empirical thinking
Scrum “intent vs mechanics”
👉 PART 4 (76–100): full exam-level scenario questions
This will include:
Just say: “continue”
part 4
Here is PART 4 (76–100) — the final set of PSM-style scenario questions + answers, designed to match the real exam thinking level of Scrum.org.
This section focuses on situational judgment, Scrum Master mindset, and anti-pattern detection.
76. A manager asks the Scrum Master for individual developer performance reports. What should the Scrum Master do?
Answer: Refuse and explain that Scrum focuses on team accountability, not individual performance tracking.
77. Developers are not attending Daily Scrum consistently. What should the Scrum Master do?
Answer: Coach the team on the purpose of the Daily Scrum and ensure it remains valuable to them.
78. The Product Owner wants Developers to commit to a fixed scope. What is the correct response?
Answer: Educate that Scrum uses forecasting, and Developers commit to a Sprint Goal, not fixed scope.
79. Stakeholders want to change Sprint scope mid-Sprint. What should happen?
Answer: Changes are allowed only if they do not compromise the Sprint Goal and are negotiated with Developers.
80. Developers are reporting progress to the Scrum Master during Daily Scrum. What is the issue?
Answer: The Daily Scrum is for Developers to coordinate with each other, not report to Scrum Master.
81. The Scrum Master is asked to assign tasks to speed up delivery. What should they do?
Answer: Refuse; Developers self-manage their work.
82. The team is not completing Sprint Goals. What should the Scrum Master focus on?
Answer: Systemic issues, team collaboration, and impediments—not assigning blame or controlling work.
83. The Product Backlog is unclear and poorly ordered. Who is responsible?
Answer: The Product Owner.
84. Developers say the Definition of Done is too strict. What should happen?
Answer: It can be discussed and adjusted, but only to increase quality, not reduce it.
85. A Sprint Goal is not defined during Sprint Planning. What is the issue?
Answer: Sprint Planning is incomplete; Sprint Goal is essential.
86. The Scrum Master notices lack of collaboration between Developers. What should they do?
Answer: Coach the team to improve collaboration and self-organisation.
87. The Product Owner is unavailable during Sprint Planning. What should happen?
Answer: Sprint Planning should be postponed or incomplete decisions avoided.
88. Developers want to skip Retrospective due to time pressure. What should Scrum Master do?
Answer: Reinforce importance of continuous improvement and ensure it happens.
89. A stakeholder requests detailed task tracking reports. What is the Scrum Master’s response?
Answer: Explain Scrum focuses on transparency via working Increment, not task-level reporting.
90. Developers are blocked but not raising it in Daily Scrum. What is the issue?
Answer: Lack of transparency or psychological safety.
91. Scrum Master is asked to approve technical decisions. What should they do?
Answer: Decline; technical decisions belong to Developers.
92. A team is delivering many items but not achieving Sprint Goal. What is wrong?
Answer: Lack of focus on Sprint Goal.
93. Stakeholders are unhappy with Sprint Review results. What should Scrum Master do?
Answer: Facilitate better collaboration and expectation alignment, not defend the team.
94. Developers are overloaded during Sprint. What should Scrum Master address?
Answer: Improve planning, capacity understanding, and system flow—not enforce overtime.
95. The Product Owner wants to bypass Developers and assign tasks. What is correct?
Answer: Not allowed in Scrum; Developers self-manage work.
96. Scrum events are being skipped due to “busy schedules.” What should Scrum Master do?
Answer: Reinforce Scrum framework and ensure events are restored.
97. The team is dependent on another team causing delays. What should Scrum Master do?
Answer: Help remove organizational impediments and improve cross-team collaboration.
98. Developers are not updating the board regularly. What is the concern?
Answer: Reduced transparency and poor flow visibility.
99. The organisation wants Scrum Master to also manage delivery timelines. What should happen?
Answer: Clarify Scrum Master is not responsible for delivery management.
100. What is the ultimate measure of Scrum success?
Answer: Delivery of valuable, usable Increments through an effective, self-managing Scrum Team.
FINAL AGILE COACHING INSIGHT
Across all 100 questions, Scrum.org is testing one core principle:
Scrum is not about controlling work—it is about enabling self-management, transparency, and empirical decision-making.
If you understand these 4 layers, you understand PSM:
Theory → empiricism (transparency, inspection, adaptation)
Accountability → clear roles, no overlap
Flow → Increment + Sprint Goal focus
Mindset → enablement over control