New: Roadmaps ordered paths through our cheat sheets and flashcards, so you always know what to study next.
Explore themSee what's new on GitHubFrom sitting in your first standup to facilitating retrospectives a team actually acts on.
A 13-step learning path. Follow it in order, or jump to what you need.
For developers, Scrum Masters, Product Owners, or anyone about to join a team that runs on sprints, who wants the ceremonies and practices to make sense instead of feeling like calendar rituals. Plan on about 6 weeks at a few hours a week. This path stays on delivery mechanics: it does not go deep on PMI-style scheduling, WBS, or earned value (see Project Management Fundamentals), or on product discovery, strategy, and roadmapping (see Product Manager). By the end you can run a full sprint cycle from planning to retro, estimate work as a team instead of guessing solo, and read velocity and cycle-time numbers without mistaking a vanity metric for real signal.
Expected: no formal background, though it helps to have worked on any team that ships something in stages. Helpful but not required: basic familiarity with project vocabulary like backlog or stakeholder.
Start here to pick up the vocabulary every later step assumes: values over processes, the frameworks Scrum and Kanban sit inside, and why 2001's four values still shape every standup you'll ever join.
This is where the philosophy from step 1 gets concrete: three roles, five events, three artifacts, and the empiricism holding them together; the self-managing team model trips up most newcomers, so expect to revisit it.
You know why Scrum trades documentation for working software, and you can name its three roles, five events, and three artifacts without hesitating. Next up: turning that vocabulary into a real sprint.
Finish this section to unlock.
+100 XP
Zooms into the first of step 2's five events: turning a backlog into a Sprint Goal and a plan the team actually commits to for the next one to four weeks.
Answers the sizing question Sprint Planning in step 3 leaves open: story points, planning poker, and the cognitive biases that make a solo estimate worse than the team's consensus.
Sets Scrum's fixed sprints from step 2 against a flow-based alternative: pull systems, WIP limits, and cycle time for work that arrives continuously instead of in batches.
Closes the loop that steps 3 through 5 opened: the Prime Directive assumes everyone did their best, and that assumption is the mindset shift that keeps a retro from turning into a blame session.
You can plan a sprint, size the work with the team instead of guessing alone, and close it with a retro that surfaces real problems instead of blame. Next up: owning the backlog and proving the sprint actually worked.
Finish this section to unlock.
+100 XP
Goes deeper on the accountability step 2 only sketched: backlog ordering, stakeholder trade-offs, and the boundary between owning outcomes and dictating tasks.
Turns the estimates from step 4 and the flow data from step 5 into numbers worth trusting: velocity, cycle time, and the vanity metrics that quietly reward the wrong behavior.
Puts steps 3 through 8 into the tool most teams actually run them in: boards, sprints, and the JQL queries that turn a backlog into a report a stakeholder can read.
You can manage a backlog like a Product Owner, read velocity and cycle time without falling for a vanity number, and run the whole cycle in the tool most teams actually use; a few minutes of due flashcards on Scrum's roles and events keeps chapter 1 fresh while you build on it here. Next up: working at the level people ask to coach them.
Finish this section to unlock.
+100 XP
Fits teams whose organization runs dozens of Scrum teams on one product: SAFe scales the roles and events from step 2 into Agile Release Trains and program-level planning.
Worth a look if you're weighing scale-up options against step 10's SAFe: LeSS keeps Scrum's original shape for multiple teams instead of adding new layers on top of it.
Matters most if you're accountable for team health, not just process: the trust and psychological safety work that makes the retro from step 6 actually land.
Pulls every ceremony and metric from this path into one practice: facilitating them well, coaching a team through the anti-patterns steps 2 and 6 warned about, and knowing when Kanban from step 5 fits better than Scrum.
You can facilitate ceremonies that change how a team works, coach a team through the anti-patterns that trip up most Scrum adoptions, and choose Scrum, Kanban, or a scaled framework based on context instead of habit. That's what the Agile & Scrum in Practice badge certifies: you can run agile delivery as a practitioner, not just a participant.
Finish this section to unlock.
+100 XP
Finish every required step, at least 70% of them genuinely done (not skipped), to earn this badge and 500 XP.