Scrum Updated SMC Exam Questions and Answers by pixie

Velocity measures the amount of estimated work successfully completed by a Scrum Team during a Sprint. Where User Stories are estimated in story points, Sprint velocity is normally calculated by totaling the story-point values of the User Stories completed during that Sprint. SCRUMstudy explicitly describes velocity in these terms.

Velocity is particularly useful because historical values can support future Sprint planning and release forecasting. After several Sprints, a reasonably stable team can use its observed velocity to estimate how much work it is realistically capable of completing in a similar Sprint.

Business Value Delivered measures value rather than effort points. Number of Stories counts items without considering their relative size—a Sprint containing five small stories is not necessarily equivalent to one containing five large stories. A Sprint Burndown Chart shows remaining work over time during the Sprint rather than defining the quantity of story points successfully delivered.

Therefore, the metric that directly captures the number of completed story points per Sprint is Velocity.

Study Guide reference: Plan and Estimate - > Estimation; Implement - > Sprint Metrics; Velocity and Story Points.

========

SBOK distinguishes risks from issues primarily through uncertainty. A risk is an uncertain future event that may affect project objectives. An issue is an existing, well-defined condition that is already occurring and therefore does not require a probability assessment.

Statements I and II contain future uncertainty: the representatives might not be ready, and the painting crew might be delayed by rain. These events have not occurred and therefore qualify as risks.

Statements III and IV describe current facts. Funding was not approved, making this an existing problem. Requirements are unclear, so ambiguity is already affecting the project. SCRUMstudy actually uses these examples when explaining the distinction: delayed crews and potentially unprepared representatives are risks, while unapproved funding and unclear requirements are issues.

Risk management is proactive—identify, assess, prioritize, mitigate, and communicate uncertain events before they materialize. Issues require active resolution because they are already real.

Therefore, I and II are the risks.

Study Guide reference: Risk - > Difference between Risks and Issues.

========

Statements II, III, and IV align with the Scrum Master's facilitative role. The Scrum Master ensures Scrum practices and processes are correctly followed, supports transparency and effective communication, facilitates Scrum meetings, and removes obstacles that interfere with successful delivery. SCRUMstudy describes the Scrum Master as the facilitator and supporting/servant leader who creates an environment conducive to team success.

Statement I is incorrect because strategic objectives and priorities are not defined by the Scrum Master. Strategic priorities are associated with Product Owner roles at the appropriate organizational level—for example, Program Product Owner or Portfolio Product Owner when Scrum is scaled. The Scrum Master supports execution of Scrum and removes impediments; the role does not own the business strategy.

Release Planning is also facilitated or coordinated by the Scrum Master while the Product Owner and Scrum Team participate in determining the release structure and Sprint length. Transparency is supported through visible artifacts, effective facilitation, and adherence to empirical process control.

Therefore, the valid combination is II, III, and IV.

Study Guide reference: Organization - > Scrum Master Responsibilities; Initiate - > Conduct Release Planning; Principles - > Empirical Process Control/Transparency.

========

The description corresponds to the Scrum Guidance Body (SGB). The SGB can provide organizational guidance, standards, regulations, recommended practices, templates, procedures, and lessons learned that Scrum Core Teams may use when appropriate.

In the backlog-refinement context, Scrum Guidance Body Recommendations can include guidance on how to understand and collate requirements, prioritize the backlog, document User Stories appropriately, and communicate changes to relevant participants.

Subject Matter Experts provide specialized knowledge based on particular technical or business domains, but the question specifically refers to documented organizational rules, development guidelines, standards, and best practices, which are characteristic of the Scrum Guidance Body.

Team Expertise refers to the collective capability of Scrum Team members to understand and execute Sprint work. Stakeholders contribute requirements, business needs, feedback, and priorities, but they are not the repository responsible for organizational Scrum standards.

The Scrum Guidance Body therefore provides consistency without converting Scrum into a centralized command-and-control methodology. Its recommendations support teams while still allowing appropriate tailoring.

Study Guide reference: Implement - > Groom/Refine Prioritized Product Backlog - > Scrum Guidance Body Recommendations.

========