dc dotCreds
Reference guide

Scrum Master Course Notes

Study Scrum Master section notes, then jump straight into the guided course or related practice questions without losing your place.

Continue Course Start Practice
Checking access

Checking Pro access...

Looking for your active Pro access before showing Course Notes. This usually takes just a moment.

Course Notes preview

Unlock Pro for the full per-exam reference guide.

Preview one piece from each section. Pro includes every Course Notes section, summary, key point, common mistake, exam tip, related-question review, and PDF export.

Includes full Course Mode and Course Notes.

Section 1 Scrum Foundations Preview
More in this section
  • Full summary in Pro version
  • 9 more key points in Pro version
  • 17 more related questions in Pro version

Summary

Scrum exists for complex work where the right answer cannot be fully known at the start. The framework creates short learning cycles: order the work in a Product Backlog, turn a selection into an Increment during a Sprint, inspect the result with stakeholders, and adapt the next step from evidence.

Key Points

  • Scrum exists for complex work where the right answer cannot be fully known at the start. The framework creates short learning cycles: order the work in a Product Backlog, turn a selection into an Increment during a Sprint, inspect the result with stakeholders, and adapt the next step from evidence.

Common Mistakes

No common mistakes are available for this section yet.

Exam Tips

No exam tips are available for this section yet.

Section 2 Scrum Team Dynamics Preview
More in this section
  • Full summary in Pro version
  • 9 more key points in Pro version
  • 15 more related questions in Pro version

Summary

A Scrum Team contains one Product Owner, one Scrum Master, and Developers. Scrum does not split this unit into analysts, testers, architects, or implementation sub-teams because the team as a whole is accountable for creating a valuable Increment each Sprint.

Key Points

  • A Scrum Team contains one Product Owner, one Scrum Master, and Developers. Scrum does not split this unit into analysts, testers, architects, or implementation sub-teams because the team as a whole is accountable for creating a valuable Increment each Sprint.

Common Mistakes

No common mistakes are available for this section yet.

Exam Tips

No exam tips are available for this section yet.

Section 3 Product Ownership Preview
More in this section
  • Full summary in Pro version
  • 9 more key points in Pro version
  • 15 more related questions in Pro version

Summary

The Product Owner is accountable for maximizing the value of the product resulting from the Scrum Team's work. That accountability cannot be split across a committee, steering group, or project manager, even when many stakeholders influence the product.

Key Points

  • The Product Owner is accountable for maximizing the value of the product resulting from the Scrum Team's work. That accountability cannot be split across a committee, steering group, or project manager, even when many stakeholders influence the product.

Common Mistakes

No common mistakes are available for this section yet.

Exam Tips

No exam tips are available for this section yet.

Section 4 Scrum Master Role Preview
More in this section
  • Full summary in Pro version
  • 9 more key points in Pro version
  • 20 more related questions in Pro version

Summary

The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. That does not mean managing the team; it means helping the Scrum Team and organization understand and use Scrum theory, accountabilities, events, artifacts, and commitments.

Key Points

  • The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. That does not mean managing the team; it means helping the Scrum Team and organization understand and use Scrum theory, accountabilities, events, artifacts, and commitments.

Common Mistakes

No common mistakes are available for this section yet.

Exam Tips

No exam tips are available for this section yet.

Section 5 Sprint Execution Preview
More in this section
  • Full summary in Pro version
  • 9 more key points in Pro version
  • 10 more related questions in Pro version

Summary

A Sprint is the fixed-length container for Sprint Planning, Daily Scrums, development work, Sprint Review, and Sprint Retrospective. It creates a repeating cadence where ideas are turned into value and inspected at least every month.

Key Points

  • A Sprint is the fixed-length container for Sprint Planning, Daily Scrums, development work, Sprint Review, and Sprint Retrospective. It creates a repeating cadence where ideas are turned into value and inspected at least every month.

Common Mistakes

No common mistakes are available for this section yet.

Exam Tips

No exam tips are available for this section yet.

Section 6 Sprint Planning & Review Preview
More in this section
  • Full summary in Pro version
  • 9 more key points in Pro version
  • 16 more related questions in Pro version

Summary

Sprint Planning starts the Sprint by creating a plan through the collaborative work of the whole Scrum Team. The event is not a handoff where the Product Owner assigns tasks; it is where value, selection, and delivery approach come together.

Key Points

  • Sprint Planning starts the Sprint by creating a plan through the collaborative work of the whole Scrum Team. The event is not a handoff where the Product Owner assigns tasks; it is where value, selection, and delivery approach come together.

Common Mistakes

No common mistakes are available for this section yet.

Exam Tips

No exam tips are available for this section yet.

Section 7 Daily Scrum & Retrospectives Preview
More in this section
  • Full summary in Pro version
  • 9 more key points in Pro version
  • 13 more related questions in Pro version

Summary

The Daily Scrum is a 15-minute event for Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog. It is not a status meeting for the Scrum Master or Product Owner.

Key Points

  • The Daily Scrum is a 15-minute event for Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog. It is not a status meeting for the Scrum Master or Product Owner.

Common Mistakes

No common mistakes are available for this section yet.

Exam Tips

No exam tips are available for this section yet.

Section 8 Artifacts & Transparency Preview
More in this section
  • Full summary in Pro version
  • 9 more key points in Pro version
  • 19 more related questions in Pro version

Summary

Scrum has three artifacts: Product Backlog, Sprint Backlog, and Increment. Each artifact exists to make key information transparent so the Scrum Team and stakeholders can inspect the same reality and adapt from it.

Key Points

  • Scrum has three artifacts: Product Backlog, Sprint Backlog, and Increment. Each artifact exists to make key information transparent so the Scrum Team and stakeholders can inspect the same reality and adapt from it.

Common Mistakes

No common mistakes are available for this section yet.

Exam Tips

No exam tips are available for this section yet.

Section 9 Coaching & PSM I Prep Preview
More in this section
  • Full summary in Pro version
  • 9 more key points in Pro version
  • 16 more related questions in Pro version

Summary

Scrum Master coaching helps people understand and enact Scrum rather than depend on the Scrum Master for every decision. Strong coaching increases self-management, clarity of accountability, and the team's ability to inspect and adapt without permission seeking.

Key Points

  • Scrum Master coaching helps people understand and enact Scrum rather than depend on the Scrum Master for every decision. Strong coaching increases self-management, clarity of accountability, and the team's ability to inspect and adapt without permission seeking.

Common Mistakes

No common mistakes are available for this section yet.

Exam Tips

No exam tips are available for this section yet.