Overview¶

A broad, end-to-end course covering Scrum fundamentals through to certification-level readiness — intended as a single comprehensive resource for someone starting from little or no prior Scrum knowledge.

Who it's for: Complete beginners to Scrum wanting a single, thorough foundation before choosing a specific certification path (PSM I, CSM, or similar).

Core Topics Breakdown¶

1. Why Agile, Why Scrum¶

• The problem with traditional waterfall delivery: requirements are gathered once upfront and rarely revisited, so late-discovered problems are expensive to fix.
• Agile Manifesto's four values and twelve principles as the philosophical foundation Scrum implements.
• Scrum as the most widely adopted agile framework — lightweight, prescriptive about roles/events/artifacts, but silent on technical practices (which is where XP practices often fill the gap).

2. The Scrum Team¶

• Product Owner: accountable for maximizing the value of the product resulting from the Scrum Team's work; owns and orders the Product Backlog.
• Scrum Master: accountable for establishing Scrum as defined in the Scrum Guide; serves the Developers, Product Owner, and Organization.
• Developers: the people committed to creating any aspect of a usable Increment each Sprint; self-managing in how they turn Product Backlog items into an Increment.

3. The Scrum Events¶

• The Sprint: a fixed-length container (typically 1–4 weeks) within which all other events occur.
• Sprint Planning: the team plans the work for the Sprint, producing a Sprint Goal and initial Sprint Backlog.
• Daily Scrum: a 15-minute event for the Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog.
• Sprint Review: inspecting the outcome of the Sprint with stakeholders and adapting the Product Backlog if needed.
• Sprint Retrospective: the team inspects itself and plans improvements for the next Sprint.

4. The Scrum Artifacts and Their Commitments¶

• Product Backlog → commitment: Product Goal (the long-term objective).
• Sprint Backlog → commitment: Sprint Goal (the single objective for the Sprint).
• Increment → commitment: Definition of Done (the quality standard the Increment must meet).

5. Estimation and Planning Techniques¶

• Story points and relative sizing (why "how big compared to this other story" is often more reliable than "how many hours").
• Planning Poker as a technique to reach group consensus while reducing anchoring bias.
• Release planning: forecasting delivery dates using historical velocity, with appropriate uncertainty ranges rather than false precision.

6. Preparing for Certification¶

• PSM I is self-study + Scrum.org's proctored exam, drawn directly from the Scrum Guide — no expiration once passed.
• CSM requires an instructor-led Scrum Alliance course plus an exam, and requires renewal every two years.
• Recommended path for beginners: master this foundational material first, then choose PSM I or CSM based on budget, employer preference, and whether instructor-led training is valued.

Study Tips¶

• Read the official Scrum Guide (free, ~13 pages) multiple times — it is short enough to internalize fully and is the primary source for most certification exams.
• Practice explaining each of the three accountabilities and five events out loud, in your own words, without looking at notes — teaching it back to yourself (or someone else) surfaces gaps quickly.
• Take free open assessments (e.g., Scrum.org's Scrum Open) repeatedly before committing to a paid certification exam.

Common Pitfalls¶

• Confusing Scrum (a framework) with Agile (a broader philosophy/mindset) — Scrum is one way to implement agile values, not a synonym for them.
• Assuming Scrum prescribes specific technical practices (TDD, CI/CD) — it doesn't; those come from XP and are commonly paired with Scrum but aren't part of the Scrum Guide itself.
• Skipping the Scrum Values (Commitment, Focus, Openness, Respect, Courage) in study — they show up more in exams than beginners expect.

Quick Reference Cheat Sheet¶

Further Practice¶

Write a one-page "Scrum in plain English" explainer as if teaching a brand-new hire — cover all three accountabilities, five events, and three artifacts in your own words.