Scrum Master Certified SMC Scrum Study Notes

A Probability Impact Grid evaluates each identified risk according to two primary dimensions: its probability of occurrence and its potential impact on project objectives. SBOK explains that each dimension may be assigned a numerical or categorical rating and that probability and impact can then be combined to derive a risk-severity score.

That makes the technique particularly appropriate for the flood-and-landslide scenario. The team can estimate how likely these events are and assess the severity of their consequences for safety, cost, schedule, infrastructure, or environmental objectives. The resulting score helps determine prioritization and the urgency of mitigation.

Probability Trees model multiple possible outcomes as branches and calculate associated expected values. Pareto Analysis ranks identified risks by magnitude to focus attention on the most significant contributors. Expected Monetary Value converts uncertainty into a financial expectation by multiplying monetary impact by probability.

All four can support risk analysis, but the question specifically emphasizes evaluating probability and impact on project objectives, which directly matches the Probability Impact Grid.

Study Guide reference: Risk - > Risk Assessment - > Probability Impact Grid.

========

The Chief Scrum Master is the designated role responsible for coordinating multiple Scrum Masters and facilitating cross-team integration in a large Scrum project. The Scrum of Scrums Meeting is one of the principal mechanisms used for this purpose.

Each Scrum Team normally sends a representative—often its Scrum Master—who communicates team progress, upcoming activities, dependencies, impediments, and work that could affect other teams. The meeting allows problems spanning several teams to be identified and coordinated at an appropriate level.

A Product Owner manages business value and requirements for a product or project scope. A Portfolio Product Owner operates at the broader portfolio level and is concerned with strategic prioritization and portfolio value. A Sponsor provides business support and funding. None of these roles normally facilitates the Scrum of Scrums.

SCRUMstudy's scaling guidance describes synchronization across multiple teams as essential to large-project Scrum and assigns this coordination responsibility to scaled Scrum leadership structures.

Therefore, Chief Scrum Master is correct.

Study Guide reference: Organization - > Scrum for Large Projects - > Chief Scrum Master and Scrum of Scrums.

========

SBOK defines risk as an uncertain event or set of events that can affect project objectives. Importantly, risk is not necessarily negative. Risks with potentially favorable consequences are classified as opportunities, whereas risks capable of producing adverse outcomes are called threats. SCRUMstudy explicitly distinguishes these two categories.

In this scenario, additional orders have not yet materialized, so they remain uncertain. However, if they occur, they would generate a positive business consequence attributable to successful project performance. That makes the event a positive risk—an opportunity.

An issue differs from a risk because an issue has already occurred and therefore is no longer uncertain. “Weakness” may be used in analytical techniques such as SWOT Analysis but is not the correct risk classification in this scenario. A threat would apply if the uncertain event could negatively affect objectives.

Because future orders represent uncertainty with a beneficial potential impact, the correct classification is Opportunity.

Study Guide reference: Risk - > Definition of Risk - > Opportunities and Threats; Risk Identification and Assessment.

========

C is the intended answer in the legacy SMC question bank, but the wording is technically defective because of the word “only.” Older SMC practice material keys C because SBOK historically described approximately 6–10 members as the ideal Scrum Team size. The intended concept is therefore that a typical individual Scrum Team should remain relatively small.

However, this must not be interpreted to mean Scrum itself can only be used when an entire project contains 6–10 people. Current SCRUMstudy guidance explicitly states that Scrum can be applied to projects of any size or complexity and can scale to large projects containing many Scrum Teams.

Options A, B, and D are clearly false: Scrum is not restricted to small projects, software development, or large corporations.

Thus, for the historical SMC item, C is the expected exam answer, but the accurate SBOK interpretation is: a Scrum Team is ideally small; Scrum as a framework is not limited to projects having only 6–10 total participants.

Study Guide reference: Introduction to Scrum - > Applicability of Scrum; Organization - > Scrum Team Size and Scaling.

========