1.Why Foundations is worth getting right
From the pillars, the module moves to the five values, commitment, courage, focus, openness, and respect, and treats them as observable behaviour rather than posters on a wall. A short game asks you to match real team situations to the value being tested, which forces you to notice values in the moment instead of reciting them afterward. The module then covers the three accountabilities and the five events at a glance, building toward the fast diagnostic used throughout the rest of the course: ask a team to state its Product Goal, Sprint Goal, and Definition of Done in one sentence each, and you learn immediately whether the artifacts are doing real work or just decorating a board.
2.How it works in practice
A significant part of Foundations is dedicated to boundaries: when Scrum is the right tool, when it is not, and how it differs from Agile broadly and from Kanban specifically. This matters because a large share of the frustration people bring to Scrum comes from applying it to well-understood, repetitive work where a flow-based approach would serve better, or from expecting Agile principles and Scrum's specific rules to be interchangeable. Getting this distinction right early prevents the common interview mistake of conflating the two, and it prepares you for the flow-based and scaling modules later in the curriculum.
The module closes with common misconceptions and a walkthrough of how to actually read the Scrum Guide so you can catch, on your own, when a team's practice has drifted from the text. Two checkpoints and a set of scenario games force you to apply the pillars and values under pressure rather than just recognize them on a multiple-choice question, which is what the Foundations quiz at the end is built to test.
3.Role reality
| Textbook theory | Delivery reality |
|---|---|
| Scrum is a lightweight framework. | Lightweight means it gives you almost no cover. Most of what fails is the surrounding habits, not the framework itself. |
| Anyone on the team can learn the roles quickly. | Learning the words takes an afternoon. Learning to hold a boundary under pressure takes a few uncomfortable Sprints. |
| The mindset shift is from planning to adapting. | Most new teams keep planning like a waterfall and calling the ceremony a Sprint. The mindset shows up in what changes mid-Sprint, not in what is scheduled. |
| Certificates prove competence. | Certificates prove you can pass a quiz. Competence shows up the first time a stakeholder pushes back on a boundary you just set. |
4.Core delivery pillars
Trade a long, confident plan for a short one you revisit daily. The team that adapts fastest wins, not the team that predicted furthest ahead.
Before you improve anything, make sure the board reflects reality. A clean board that lies is worse than a messy one that is honest.
The instinct under pressure is to start more work. The disciplined move is to finish what is open before starting anything new.
Planning, Daily, Review and Retrospective are four separate chances to catch a mistake early. Skipping one removes a safety net, not a formality.
5.Early-Sprint health signals
Four things worth checking in your first few Sprints, before flow metrics become meaningful.
Can every team member state the Sprint Goal without checking a document.
Does the board match what people actually did yesterday, not what was planned.
How many days a blocked item sits before someone outside the team hears about it.
Are two items marked done actually held to the same bar, or is done negotiable.
6.Situations you will be asked to handle
The module puts you inside 6 decisions rather than asking you to recognise the right answer on a list. Each one is a situation practitioners meet, with several defensible options and consequences that follow from the one you pick. The scenarios below are the shape of the judgment the subject demands.
- Game: The Five Values
- Game: Spot the pillar
- Checkpoint: Live the values
- Checkpoint: Which pillar is that?
- Checkpoint: Values under pressure
- Checkpoint: Pillars in the wild
7.Common mistakes and why they fail
Confusing Agile with Scrum
Treating Scrum's specific rules, like the Sprint length or the Daily Scrum, as universal Agile principles. Agile is a set of values and principles; Scrum is one particular, deliberately minimal framework that implements some of them.
Applying Scrum to well-understood, repetitive work
Forcing Scrum onto support queues or maintenance work where the requirements are already known and the work arrives continuously. That is Kanban territory, and forcing Sprint boundaries onto it usually just adds overhead.
Reciting the values instead of living them
Being able to name commitment, courage, focus, openness, and respect without recognizing the moment a team is violating one, for example, silently absorbing scope instead of raising it, which is a courage and transparency failure at once.
Skipping the pillar behind the event
Running the Daily Scrum, Sprint Review, or Retrospective as a scheduled meeting without asking what is being inspected and what will change as a result, which turns real adaptation into a fifteen-minute status report.
8.Questions worth asking before you commit time to this
What is the actual difference between Scrum and Agile?
Agile is a mindset described by four values and twelve principles, favoring people, working software, collaboration, and responding to change. Scrum is one specific, lightweight framework, with defined roles, events, and artifacts, that helps a team live out some of those values. You can be Agile without using Scrum, and you can technically run Scrum's ceremonies without being Agile in spirit.
When should a team choose Kanban instead of Scrum?
When the work is continuous rather than plannable in fixed batches, support tickets, incident response, or a steady stream of small requests, a pull-based flow system with WIP limits usually serves better than Sprint boundaries. Scrum fits complex product work where a team benefits from a fixed timebox to focus, plan, and inspect.
Why does the module spend so much time on the three pillars?
Because nearly every anti-pattern later in the curriculum traces back to a pillar failure. Hidden information breaks transparency, a Sprint Review with no real stakeholder feedback breaks inspection, and a retrospective that never changes anything breaks adaptation. Understanding the pillars gives you one diagnostic that works across every event.
9.What to remember
- The mindset shift from following steps to running an empirical process
- Where the first hands-on decisions in a Sprint actually get made
- A checklist for the habits that separate certified from capable
10.Where this sits in the Scrumling course
What Scrum is, why it exists, and the mindset that powers it.
About 79 minutes of lessons and decision scenarios.
- What is Scrum?
- Empiricism & the three pillars
- A short history of Scrum
- The three accountabilities
- The five events, at a glance
- The three artifacts and their commitments
- The five values, in practice
- When Scrum is the right tool
- When Scrum is the wrong tool
- Common Scrum misconceptions
- Scrum vs Agile
- Scrum vs Kanban
- How to read the Scrum Guide
- Game: The Five Values
- Game: Spot the pillar
- Checkpoint: Live the values
- Checkpoint: Which pillar is that?
- Checkpoint: Values under pressure
- Checkpoint: Pillars in the wild
Assessment: Foundations quiz