Scrum Updated SMC Exam Questions and Answers by artur

Option C incorrectly describes the Probability Impact Grid. In SBOK, the Probability Impact Grid evaluates each individual risk by assigning values to both probability and impact. Those ratings are then combined—commonly by multiplication—to derive a risk-severity or PI score for prioritization.

The wording in C—calculating an overall impact from the values of multiple possible events or outcomes—is more closely associated with Probability Trees, where potential outcomes are represented by separate branches with associated probabilities and impacts.

Option A is correct. Expected Monetary Value equals the monetary impact of a risk multiplied by its probability of occurrence. Option B is correct because Pareto Analysis ranks risks according to magnitude, enabling attention to be focused on the most consequential risks. Option D also correctly describes Probability Trees, where each potential outcome is represented graphically through branching alternatives.

Thus the mismatched technique-description pairing is C.

Study Guide reference: Risk - > Risk Assessment Techniques - > Probability Trees, Pareto Analysis, Probability Impact Grid, Expected Monetary Value.

========

A risk threshold identifies the point or level at which exposure changes from being acceptable to unacceptable. SCRUMstudy distinguishes risk threshold from the related concepts of risk appetite and risk tolerance. Risk appetite reflects the overall amount of uncertainty an organization is willing to pursue or accept, while risk tolerance describes the degree or volume of variation the stakeholder can withstand. The threshold establishes the boundary at which action or rejection becomes necessary.

In this scenario, some defects remain acceptable and do not prevent release. Once the defect level rises beyond a specified point, however, the deliverables will be rejected. This establishes a clear acceptance boundary, making it a textbook example of a risk threshold.

Risk seeking is a behavioral attitude in which a stakeholder is willing to accept greater uncertainty in pursuit of additional benefits. That concept does not apply here.

The decisive phrase is effectively “acceptable until this level is exceeded.” Once that boundary is crossed, the response changes. Therefore, the scenario illustrates Risk Threshold.

Study Guide reference: Risk - > Risk Attitude - > Risk Appetite, Risk Tolerance, Risk Threshold, Utility Function.

========

Ownership of grooming—or in current terminology, refining—the Prioritized Product Backlog belongs primarily to the Product Owner, not the Scrum Master. SCRUMstudy explicitly states that the Product Owner leads backlog refinement, adds or revises User Stories, reprioritizes work, and ensures upcoming requirements are sufficiently refined.

The Scrum Master may facilitate Prioritized Product Backlog Review Meetings and help ensure that communication, estimation, and Scrum practices remain effective, but facilitation is not the same as owning or grooming the backlog.

The Scrum Master also coordinates creation of the Release Planning Schedule as part of Conduct Release Planning. SCRUMstudy's role mapping explicitly lists that responsibility.

Similarly, the Scrum Master can represent Scrum Core Team experience and lessons learned so that organizational knowledge and Scrum Guidance Body recommendations can improve.

The critical distinction is between facilitating backlog refinement and being accountable for the contents and prioritization of the backlog. The latter belongs to the Product Owner.

Therefore, A is the activity that is not a Scrum Master responsibility.

Study Guide reference: Organization - > Scrum Master Responsibilities; Implement - > Groom/Refine Prioritized Product Backlog.

========

Takeuchi and Nonaka's work is historically important because it explicitly contrasted the new product-development model with the traditional sequential relay-race approach. They did not recommend sequential development. Instead, they described a holistic or rugby-style model in which a multidisciplinary team progresses together toward a common objective.

The rugby metaphor emphasized overlapping activities, collaboration, adaptability, and shared responsibility rather than handing work sequentially from one specialist group to another. Their observations were derived from case studies involving organizations across several manufacturing industries. This conceptual foundation later contributed to what became known as Scrum.

Therefore, option B reverses the historical argument. The sequential relay-race model was the approach Takeuchi and Nonaka were challenging, whereas the rugby model represented the flexible, integrated alternative they advocated.

Options A, C, and D accurately describe the historical background presented by SCRUMstudy: the rugby analogy, team-based development toward a shared objective, and the use of cross-industry manufacturing case studies.

Study Guide reference: Introduction to Scrum - > History of Scrum; traditional sequential product development versus the holistic/rugby approach.

========