Scrum SMC Dumps Questions Answers

A Sprint Burndown Chart graphically represents the amount of work that remains to be completed during an ongoing Sprint. SCRUMstudy's SBOK glossary explicitly defines it as a graph depicting the amount of work remaining in the Sprint.

Normally, the horizontal axis represents elapsed Sprint time and the vertical axis represents remaining effort, tasks, or points. As work is completed, the plotted remaining workload should trend downward toward zero. Comparing actual remaining work with an expected trajectory helps the Scrum Team identify whether progress is broadly consistent with the Sprint plan.

Option A relates more directly to the Impediment Log and Daily Standup discussions. Although a Burndown Chart may indirectly indicate that progress has slowed, it does not identify the specific impediment causing that condition. Option C describes completed work rather than the traditional burndown representation of remaining work. Option D describes task or User Story estimation rather than Sprint tracking.

Therefore, its fundamental purpose is to visualize work remaining during the Sprint.

Study Guide reference: Implement - > Sprint Tracking Tools - > Sprint Burndown Chart.

========

Once a Sprint begins, its committed scope and Acceptance Criteria are normally protected from change. New requirements are ordinarily added to the Prioritized Product Backlog and considered in a later Sprint. However, SBOK defines an important exception: if a change is so significant that continuing the existing Sprint would no longer create meaningful or useful results, the active Sprint should be terminated and a new Sprint planned using the revised requirements.

The scenario explicitly describes a critical business requirement that changes the Acceptance Criteria governing committed work. This implies that the existing Sprint outcome may no longer satisfy the customer's essential need. In that situation, simply continuing against obsolete criteria would waste resources.

Option A allows uncontrolled mid-Sprint scope substitution, which Scrum avoids. Option B would normally be correct for a non-urgent change, but the question emphasizes criticality. Option C incorrectly frames the problem as team bandwidth rather than Sprint stability and business value.

Therefore, where the changed requirement invalidates the current Sprint's intended outcome, Sprint termination and replanning is the appropriate response.

Study Guide reference: Change - > Integrating Change; Maintaining Sprint Stability; Managing Urgent Change Requests.

========

A Burndown Chart is the appropriate artifact for comparing work remaining over time with the expected or planned rate of completion. The chart normally plots remaining work against the Sprint timeline and therefore makes deviations from the planned trajectory visible.

If the actual remaining-work line stays above the planned line, the team may be progressing more slowly than expected. If it is below the planned trajectory, work is being completed faster than originally anticipated. The objective is not to measure individual performance but to provide transparent team-level information that supports inspection and adaptation.

A Scrumboard visualizes task status through workflow columns such as To Do, In Progress, and Done, but it does not inherently plot planned versus actual progress over time. A Cumulative Flow Diagram visualizes work distribution across workflow states and can reveal bottlenecks. A Kanban Board similarly focuses on workflow visualization.

The Burndown Chart therefore provides the clearest direct representation of planned versus actual remaining work, making C correct.

Study Guide reference: Implement/Plan and Estimate - > Sprint Burndown Chart; Transparency and Progress Tracking.

========