Coursya originals · Free PDF ebook

60 Essential Agile, Scrum, and Kanban Terms

Learn 60 Agile, Scrum and Kanban terms through plain-English definitions, booking-team examples and illustrated notes in a free 23-page PDF.

Agile, Scrum & Kanban

A traveller chooses a flight, reaches checkout, sees an unexpected fee and leaves. How would a product team work out what to change? This free illustrated handbook uses that booking problem to teach 60 essential Agile, Scrum, and Kanban terms. Each term has a short meaning and a worked example. You can follow the team from its first customer conversation through planning, delivery and measurement, or use the PDF bookmarks to jump straight to a topic.

Start with the decision in front of you

If you want to find out why people leave, begin with feedback loops, user stories and acceptance criteria. The examples show how a vague request to fix checkout becomes something the team can test. For example, a traveller choosing a $100 fare with a $20 fee should see a total of $120 before payment. That concrete example helps the team decide what to build and how to tell whether it works.

For a conversation about value, turn to the page on outputs and outcomes. A new price label is an output. An increase in the share of travellers who complete checkout is an outcome worth investigating. The guide keeps the two separate so readers can ask what changed for customers after a release.

Understand the Scrum conversations

Several pages follow a booking change through the Scrum framework. Readers meet the Product Owner, Scrum Master and Developers, then see how a Product Goal gives direction to the Product Backlog and how a Sprint Goal guides a shorter stretch of work. A Daily Scrum example shows Developers changing their plan when a tax check holds up the goal. A Sprint Review example brings travel agents into the conversation about the result.

The guide also covers increments, quality and estimation. One case shows why a screen that still fails the team’s agreed accessibility check cannot count as Done. Another shows how a team might use its own history of completed story points to discuss future work. Estimation practices such as story points and velocity are presented as optional techniques.

Read a board and interpret its numbers

The Kanban pages start with the team’s choice of work item and its agreed start and finish. Those choices matter when someone asks how long changes take. In the worked clock example, the team receives a request on Monday, starts work on Tuesday and finishes on Friday. At the same time of day, that gives four calendar days from request to delivery and three from start to finish. While the item is open on Thursday, its age is two days.

The remaining cases show how a queue grows, how a WIP limit changes the next decision, and how to discuss a time forecast with a probability. Each chart concept is paired with a question the team can investigate. On the last page, the team designs an experiment to reduce waiting while checking whether the change is sustainable.

Inside the handbook

  1. One booking problem, three ways to help — Agile, Scrum, Kanban.
  2. Build a little, learn a little — Incremental development, Iterative development, Feedback loop.
  3. Write a change small enough to try — User story, Acceptance criteria, Story splitting.
  4. Measure what the change achieves — Minimum viable product (MVP), Output, Outcome.
  5. Make a decision from evidence — Transparency, Inspection, Adaptation.
  6. Know who owns each decision — Product Owner, Scrum Master, Developers.
  7. Give the backlog a direction — Product Goal, Product Backlog, Backlog refinement.
  8. Give the Sprint a purpose — Sprint, Sprint Goal, Sprint Backlog.
  9. Choose the right conversation — Sprint Planning, Daily Scrum, Sprint Review.
  10. Agree what is ready to use — Sprint Retrospective, Increment, Definition of Done.
  11. Use estimates with care — Estimation, Story points, Velocity.
  12. Define the journey of a ticket — Work item, Workflow, Definition of Workflow.
  13. Make the board guide action — Kanban board, Explicit policy, Pull.
  14. Count work that is still open — Work in progress (WIP), WIP limit, Blocked item.
  15. Find where the work is waiting — Queue, Bottleneck, Swarming.
  16. Read three different clocks — Cycle time, Work item age, Lead time.
  17. Count deliveries over time — Throughput, Batch size, Cadence.
  18. Make a time forecast — Service level expectation (SLE), Percentile, Cycle time scatterplot.
  19. Spot a growing queue — Cumulative flow diagram, Arrival rate, Flow efficiency.
  20. Choose the next improvement — Hypothesis, Experiment, Sustainable pace.

How to use the guide

Read a page before the next team conversation and ask a colleague to apply one of its terms to a current item. When using a time metric, write down the boundary and unit first. For example, state whether the clock starts when a customer asks for a change or when the team begins working on it. This makes comparisons easier to interpret.

Frequently asked questions

Who is the PDF for?

It is written for project managers, product teams and readers encountering Agile, Scrum or Kanban vocabulary for the first time. The examples use a booking product, but the questions about value, quality and waiting apply to other workflows.

How many pages are in the download?

The English PDF contains 23 pages. There are 20 numbered learning pages, one cover and two advertisement pages. Each learning page explains three terms.

Where are the promotional links?

A templates advertisement follows content page 5. A Coursera Plus advertisement follows content page 15. The entire image on each advertisement page is linked. A purchase is optional and promotional links may earn Coursya a commission.

Share this article