Learn Agile, Scrum and Kanban
How teams build things in small pieces and change course as they learn. Nineteen lessons start with the Agile Manifesto and short, fixed blocks of time. Then comes Scrum, as its own guide sets it out: the three jobs, the five events and the three lists. After that, Kanban and how work flows. Then stories, sizing and the charts that track progress. It ends on other methods and on many teams at once. It assumes nothing.
Not started
0 of 19 lessons done
Level 1 Β· What agile is
score0100/4 wordsThe short text from 2001 that started it all. Then the fixed blocks of time that every agile method is built on.
- The Agile ManifestoWhat the Agile Manifesto says, who wrote it and when. Its four values and twelve rules. What the line about the right side really means.10 min2 terms
- Iterations and TimeboxesWhy agile teams work in short, fixed blocks of time, often one to four weeks. How a timebox stops work from stretching, and what happens to the rest.9 min2 terms
Level 2 Β· Scrum
score10470/17 wordsThe most used agile framework, as its own guide sets it out. Three jobs, the lists they work from, and five events with fixed time limits.
- Scrum Framework BasicsWhat Scrum is, where it came from and what its guide asks for. Sprints of one month or less, three pillars and the five values a team works by.11 min2 terms
- Scrum Team and RolesThe three jobs in a Scrum Team: Product Owner, Scrum Master and Developers. What each one is accountable for, and why there is no boss inside.12 min5 terms
- Product Backlog and GoalWhat the Product Backlog is, how it is ordered, and why the top is clear and the bottom is rough. How the Product Goal gives the whole list one aim.10 min2 terms
- Sprint Planning and BacklogHow Sprint Planning starts each sprint by asking why, what and how. How it makes the Sprint Goal and the Sprint Backlog, and how long it may take.11 min3 terms
- Daily Scrum MeetingWhat the 15-minute Daily Scrum is for, who goes, and why it is not a status report for a manager. How it keeps a sprint on course toward its goal.9 min1 terms
- Sprint Review vs RetrospectiveThe two meetings that end a sprint. The Sprint Review looks at the product with the people it is for, and the Retrospective looks at how the team worked.11 min2 terms
- Definition of DoneWhat makes work count as finished in Scrum. How the Definition of Done turns work into an Increment, and why half-done work never goes to the review.10 min2 terms
Level 3 Β· Kanban
score47580/8 wordsA way to run work with no sprints at all. A board, a cap on work in progress, and three numbers that show how fast work flows.
- Kanban Board and WIP LimitsHow Kanban shows work on a board and caps how much is in progress at once. Why a WIP limit makes a team finish more by starting less.11 min4 terms
- Lead Time and Cycle TimeThe three numbers that show how work flows: lead time, cycle time and throughput. How they fit together, and how a flow chart shows where work piles up.12 min4 terms
Level 4 Β· Stories, sizing and tracking
score58890/18 wordsHow work is written down, checked, sorted and sized. Then the charts that show whether a sprint or a release is on track.
- User Stories and EpicsHow a user story writes one need in one line, and why the detail comes from talking. How epics break into stories, and when a spike comes first.12 min4 terms
- Acceptance Criteria and INVESTHow acceptance criteria say when a story is done. How six INVEST letters check a story. What a ready check adds before a sprint.11 min3 terms
- Backlog Refinement and MoSCoWHow backlog refinement keeps the top of the list small, clear and sized. How the MoSCoW method sorts work into must, should, could and won't have.10 min2 terms
- Story Points and EstimationWhy agile teams size work by comparing it, not by guessing hours. Story points, planning poker and t-shirt sizes, and when each one fits.12 min4 terms
- Velocity and Burndown ChartsHow velocity uses past sprints to plan the next one. How a burndown and a burnup chart show work left and work done, and which one hides added scope.12 min3 terms
- Story Maps and ReleasesHow a user story map lays stories along the steps a user takes. How release planning cuts the map into slices and says about when each one ships.11 min2 terms
Level 5 Β· Other methods and scale
score891000/5 wordsOther agile ways to work, beyond the two most used. Then what changes when many teams build one product.
- XP, Lean and ScrumbanThree more agile ways to work. One is a set of strict coding habits. One is a war on waste. The last mixes Scrum events with a Kanban board.12 min3 terms
- Scaling Agile with SAFeWhat changes when many agile teams build one product. How a scrum of scrums links a few teams, and how SAFe groups 50 to 125 people to plan as one.12 min2 terms
Words in this course
The 52 glossary entries this course teaches, in the order it teaches them. Open any of them on its own.
- Agile
- Agile Manifesto
- Iteration
- Timebox
- Scrum
- Sprint
- Scrum Team
- Product Owner
- Scrum Master
- Developers (Scrum)
- Self-Organizing Team
- Product Backlog
- Product Goal
- Sprint Planning
- Sprint Goal
- Sprint Backlog
- Daily Scrum
- Sprint Review
- Sprint Retrospective
- Increment
- Definition of Done
- Kanban
- Kanban Board
- Work in Progress Limit
- Pull System
- Lead Time
- Cycle Time
- Throughput
- Cumulative Flow Diagram (CFD)
- User Story
- Epic
- Spike
- Story Splitting
- Acceptance Criteria
- INVEST Criteria
- Definition of Ready
- Backlog Refinement
- MoSCoW Method
- Relative Estimation
- Story Points
- Planning Poker
- T-Shirt Sizing
- Velocity
- Burndown Chart
- Burnup Chart
- User Story Mapping
- Release Planning
- Extreme Programming (XP)
- Lean Software Development
- Scrumban
- Scrum of Scrums
- Scaled Agile Framework (SAFe)