4.5.2 · D1Software Engineering

Foundations — Agile — Scrum (sprints, roles, ceremonies), Kanban

2,098 words10 min readBack to topic

This page assumes you know nothing. We build every word, arrow, and letter the parent Agile — Scrum & Kanban note leans on, in an order where each idea rests on the one before it.


0. What is "software work" even made of?

Before any math, picture the raw material. A software team turns requests ("let users reset their password") into working features. Each request is a little card. The whole game is: cards come in, cards go out, and we care about how long each card takes and how many are stuck in the middle.

Look at the figure. Three zones — waiting, being worked on, done. Everything below is just names for the quantities you can see here: how many cards sit in the middle, how fast they leave, how long one card lingers.


1. "Batch" and "increment" — the size of a chunk of work

The parent's word "potentially shippable increment" just means: one cupcake that is actually edible — a slice complete enough to hand to a user.


2. Counting time in "sprints" and "days"

Why do we need a letter for it? Because in a moment we'll ask "how much work should be left on day 3 of 10?" — and to answer that we compare a running day-count against the total .


3. "Story points" — measuring size without measuring hours

Here is the first real notation you must not fear.


4. Summation — the "add all of these up" symbol

The parent writes . Let's earn every mark.


5. The mean — one number that stands for many

Velocity is just this : a measured fact about the team, not a target.


6. The ceiling — "round up, because you can't have half a sprint"

The parent forecasts with . Two new things: and the bracket.


7. A line that falls: the burndown, and


8. Flow letters: , , — the Kanban trio

Now the second cluster of symbols, for the flow world. Go back to the figure in §0 — the same three zones.


9. Two words that connect to the wider map

  • SDLC — the Software Development Life Cycle (SDLC) is the overall lifecycle (plan → build → test → release) that Agile is one way of running.
  • Waterfall — the Waterfall Model is the "big dam" the parent contrasts Agile with: do every phase once, in order.
  • CI/CDContinuous Integration & Delivery (CI-CD) is the machinery that makes tiny increments actually shippable often.

Prerequisite map

Cards of work

Batch and increment

Story points

Summation sigma

Mean v-bar velocity

Ceiling forecast sprints

Function R of d

Burndown line

WIP L

Little's Law L equals lambda W

Throughput lambda

Lead time W

Scrum math

Kanban math


Equipment checklist

Cover the right side; can you answer each before revealing?

What does mean?
The story points completed in sprint number .
What does expand to?
— add every sprint's points.
What is the bar in telling you?
It's the average of the values.
Why do we use the ceiling when forecasting sprints?
You can't run a fractional sprint, so any leftover work needs a whole extra sprint — round up.
In , what is and ?
(all work remains); (nothing left).
Why is the ideal burndown a straight line?
It assumes a constant burn rate per day — a baseline ruler for reality.
What do , , each stand for?
= items in progress (WIP); = throughput (finished per unit time); = time one item spends in the system.
State Little's Law and its picture.
— items on the road = exit-rate × time each stays.
To deliver faster (smaller ) which lever does Kanban actually pull?
It caps (WIP limit), since and is hard to force up.
Why are story points relative, not hours?
Humans compare sizes well but estimate absolute time badly; points capture relative effort only.