Professional Scrum Master Scrum Theory and Empiricism 5 — Questions and Answers
Question 1: A Scrum Team delivers a 'done' Increment every Sprint but the product never reaches customers due to a lengthy release process outside the team's control. Which pillar of empiricism is most weakened?
- Transparency
- Inspection
- Adaptation
- All three pillars are equally weakened (Correct answer)
Correct answer: All three pillars are equally weakened
Without real customer feedback from released Increments, all three pillars suffer: the team cannot truly see, inspect, or adapt based on actual usage data.
Question 2: What does Scrum theory say about the appropriate response when a Sprint is failing to achieve its Sprint Goal?
- The Sprint must be cancelled by the Product Owner immediately
- The Developers should inspect what is happening, collaborate with the Product Owner, and adapt their plan while keeping the Sprint Goal in focus (Correct answer)
- The Scrum Master should escalate to management to extend the Sprint
- The team should reduce quality standards to deliver something by the Sprint end
Correct answer: The Developers should inspect what is happening, collaborate with the Product Owner, and adapt their plan while keeping the Sprint Goal in focus
The empirical response is to inspect why the goal is at risk and adapt the plan — collaboration between Developers and Product Owner is key before considering cancellation.
Question 3: Why does the Scrum Guide state that each Sprint can be considered a short project?
- Because Sprints have a project manager, scope, and budget
- Because each Sprint contains all the activities needed to produce a done Increment, creating a complete inspect-and-adapt cycle (Correct answer)
- Because Sprints must produce a shippable product every time
- Because Sprints are managed using traditional project management techniques
Correct answer: Because each Sprint contains all the activities needed to produce a done Increment, creating a complete inspect-and-adapt cycle
Like a miniature project, each Sprint encompasses planning, execution, review, and retrospection, forming a complete empirical feedback loop.
Question 4: A Product Owner refuses to share product metrics with the Scrum Team, claiming they are confidential. How does this affect empiricism?
- It has no effect because metrics are the Product Owner's responsibility alone
- It reduces transparency, preventing the team from making informed decisions during inspection and adaptation events (Correct answer)
- It only affects the Sprint Review, not other Scrum events
- It is acceptable as long as the team can still estimate story points
Correct answer: It reduces transparency, preventing the team from making informed decisions during inspection and adaptation events
Withholding metrics reduces transparency, undermining the team's ability to inspect real outcomes and make evidence-based adaptations to the product or process.
Question 5: Which best describes why Scrum does not prescribe specific engineering techniques like TDD or CI/CD?
- These practices are considered too advanced for most Scrum Teams
- Scrum provides the empirical framework and values, leaving teams free to adapt specific practices based on their context and learning (Correct answer)
- The Scrum Guide was written before these techniques existed
- Scrum only governs collaboration and meeting structure, not technical work
Correct answer: Scrum provides the empirical framework and values, leaving teams free to adapt specific practices based on their context and learning
Scrum's empirical foundation means teams should inspect what works in their context and adapt their technical practices accordingly, rather than follow prescribed methods.
Question 6: An organization implements Scrum but runs two-week Sprints with only one big review at the end of the quarter. How does this violate Scrum theory?
- It does not violate Scrum theory; quarterly reviews are more efficient
- It eliminates frequent inspection and adaptation opportunities, breaking the empirical cycle that Scrum depends on (Correct answer)
- The only issue is that the review meeting is too long
- Quarterly reviews are acceptable if stakeholders prefer them
Correct answer: It eliminates frequent inspection and adaptation opportunities, breaking the empirical cycle that Scrum depends on
Holding reviews only quarterly removes the regular empirical feedback loops that Scrum Sprints are designed to create, defeating the purpose of iterative development.
Question 7: What role does courage play specifically in supporting the empirical pillars of Scrum?
- Courage allows teams to ignore stakeholder feedback they disagree with
- Courage enables teams to transparently surface problems, honestly inspect outcomes, and adapt even when changes are uncomfortable (Correct answer)
- Courage is primarily relevant to the Scrum Master's conflict resolution duties
- Courage is needed only during Sprint Reviews to defend the team's work
Correct answer: Courage enables teams to transparently surface problems, honestly inspect outcomes, and adapt even when changes are uncomfortable
Without courage, teams hide problems (undermining transparency), avoid honest inspection, and resist necessary adaptations — making empiricism impossible in practice.
A Scrum Team delivers a 'done' Increment every Sprint but the product never reaches customers due to a lengthy release process outside the team's control.
Which pillar of empiricism is most weakened?