How to use these notes: section numbers (§1.1, §1.2 ...) match the question bank. "Slide L06-S07" means slide 7 of this lecture. Difficult words are explained in "Word help" boxes and in the word bank at the end.
Learning outcomes
By the end of this lecture you should be able to:
SLO | Learning outcome | CLO | Bloom | Slides |
|---|---|---|---|---|
SLO 6.1 | Explain Kanban: visualising work, WIP limits, flow, and lead time, cycle time and throughput. | CLO1 | C2 Understand | L06-S06 to S09 |
SLO 6.2 | Describe Lean, DSDM, Agile Modeling and the Agile Unified Process in brief. | CLO1 | C2 Understand | L06-S10 to S13 |
SLO 6.3 | Choose a suitable agile model for a given project and justify the choice. | CLO1 | C3 Apply | L06-S14, S15 |
We now know three agile ideas in depth: the values (Lecture 3), XP (Lecture 4) and Scrum (Lecture 5). Today we meet the rest of the agile family. The main one is Kanban, which you will use in Practical 06. Then we look briefly at Lean, DSDM, Agile Modeling and the Agile Unified Process, and finish by choosing the right model for a project.
§1 The agile family
Slides L06-S02, L06-S05
§1.1 Recap: Scrum in one minute
Slide L06-S02
Scrum: Product Owner, Scrum Master, Developers; product backlog, sprint backlog, increment; sprint, planning, daily scrum, review, retrospective. Work is planned in fixed sprints. Today's first model, Kanban, works without sprints.
§1.2 Many methods, one set of values
Slide L06-S05
Model | Main focus | Best known for |
|---|---|---|
XP | Engineering practices | Test-first, pair programming, refactoring |
Scrum | Managing work in sprints | Roles, events, artifacts |
Kanban | Flow of work | Visual board, WIP limits |
Lean | Removing waste | Seven principles from Toyota thinking |
DSDM | Fixed time and cost | MoSCoW, timeboxing |
Agile Modeling | Useful, light models | "Travel light" |
Agile Unified Process | Agile inside UP phases | "Serial in the large, iterative in the small" |
All of them share the Agile Manifesto values. They differ in what they focus on, so teams often mix them, for example Scrum + XP, or Scrum + Kanban ("Scrumban").
§2 Kanban
Slides L06-S06 to L06-S09
§2.1 What Kanban is
Slide L06-S06
Kanban is a Japanese word meaning signboard or visual card. It comes from the Toyota Production System (Taiichi Ohno), where a card signalled that a part was needed. David J. Anderson adapted it for software teams (book *Kanban*, 2010).
Kanban has no sprints and no fixed roles. Work items flow continuously across a board. Its core practices are:
1. Visualise the work: every item is a card on a board with columns for each stage.
2. Limit work in progress (WIP): each column has a maximum number of cards.
3. Manage flow: watch how fast cards move and remove blockages.
4. Make policies explicit: write the rules, e.g. what "ready" and "done" mean.
5. Improve collaboratively: use feedback and measurements to improve step by step.
Kanban is a pull system: a person pulls a new card into a column only when there is space under the WIP limit, instead of work being pushed onto them.
Word help WIP = work in progress: items started but not finished pull system = new work is taken only when there is free capacity |
§2.2 WIP limits
Slide L06-S07
A Kanban board for the cafeteria app: Backlog | Ready (max 5) | In Progress (max 3) | Testing (max 2) | Done. If Testing already has 2 cards, nobody may move a third card into it. The developers must first help test the cards already there. This is how WIP limits expose bottlenecks and make the team finish work before starting new work.
Real-world example: the dhaba kitchen A dhaba has 3 stoves, so at most 3 dishes can cook at once (WIP limit 3). If the waiter takes 15 new orders in a rush, nothing cooks faster; orders just wait longer and customers get angry. Good kitchens take new orders only as fast as they can finish them. Kanban teams work the same way: stop starting, start finishing. |
Word help bottleneck = the slowest stage, where work piles up capacity = how much work can be handled at the same time |
§2.3 Flow metrics and Little's Law
Slide L06-S08
Metric | Meaning | Example |
|---|---|---|
Lead time | Time from when an item is requested (enters the board) until it is done. | Card added on day 1, done on day 4: lead time 3 days. |
Cycle time | Time from when work starts on the item until it is done. | Started day 2, done day 4: cycle time 2 days. |
Throughput | Number of items finished per unit of time. | 10 cards finished in 5 days: 2 per day. |
WIP | Number of items started but not finished. | 6 cards between Ready and Testing. |
Little's Law links them: average lead time = average WIP ÷ average throughput.
Situation | Calculation | Average lead time |
|---|---|---|
6 items in progress, 2 finished per day | 6 ÷ 2 | 3 days |
WIP limit lowered to 4, still 2 per day | 4 ÷ 2 | 2 days |
So with the same team speed, less work in progress means each item finishes sooner. This is the main argument for WIP limits. (The law holds for averages over a stable period.)
Word help lead time = request-to-done time cycle time = start-to-done time throughput = how many items are finished per day or week |
§2.4 Scrum and Kanban compared
Slide L06-S09
Scrum | Kanban | |
|---|---|---|
Rhythm | Fixed-length sprints | Continuous flow, no sprints |
Roles | Product Owner, Scrum Master, Developers | No required roles |
Limit on work | Per sprint: what fits the sprint goal | Per column: WIP limits |
Change | New work waits for the next sprint | New work can enter any time there is space |
Key measure | Velocity, burndown | Lead time, cycle time, throughput |
Good for | New product development with regular demos | Support, maintenance, operations, unpredictable requests |
Many teams combine them (Scrumban): sprints and a sprint review, plus WIP limits on the board.
§3 Lean software development
Slides L06-S10
§3.1 Seven principles
Slide L06-S10
Lean thinking also comes from Toyota. Mary and Tom Poppendieck (2003) applied it to software with seven principles:
Principle | In simple words |
|---|---|
Eliminate waste | Remove anything that gives the customer no value. |
Build quality in | Prevent defects (tests, reviews) instead of finding them at the end. |
Create knowledge | Learn through short cycles and feedback. |
Defer commitment | Make big, irreversible decisions as late as responsibly possible. |
Deliver fast | Small batches reach users quickly. |
Respect people | Trust and empower the team. |
Optimise the whole | Improve the complete flow, not one stage alone. |
Waste in software includes partly done work, extra features nobody asked for, waiting (delays), hand-offs between people, task switching, relearning, and defects.
Real-world example: waste in a fee-challan system A team builds a fancy PDF designer that no one uses (extra feature), waits a week for the finance office's approval (delay), and fixes the same rounding bug three times (defects). Lean asks the team to remove these first. |
Word help waste = effort that adds no value for the customer defer = to delay until later |
§4 DSDM
Slides L06-S11
§4.1 Dynamic Systems Development Method
Slide L06-S11
DSDM was created in the UK in 1994 by a consortium of companies. Its key idea: fix time and cost, and let the features vary. It follows a version of the Pareto principle: about 80% of an application can often be delivered in 20% of the time it takes to deliver the complete (100%) application.
- Timeboxing: each piece of work has a fixed deadline that does not move.
- MoSCoW prioritisation decides what is dropped if time runs short (Must, Should, Could, Won't). You used MoSCoW in Practical 2.
- Active user involvement and frequent delivery.
DSDM life cycle activity (Pressman) | What happens |
|---|---|
Feasibility study | Basic business requirements and constraints; is DSDM suitable? |
Business study | Functional and information requirements; basic architecture |
Functional model iteration | Incremental prototypes that show functionality to the customer |
Design and build iteration | Prototypes revisited so they are engineered properly |
Implementation | Latest increment placed into operation |
Word help consortium = a group of organisations working together Pareto principle = the 80/20 rule: a small part of the effort gives most of the result |
§5 Agile Modeling and the Agile Unified Process
Slides L06-S12 to L06-S13
§5.1 Agile Modeling (AM)
Slide L06-S12
Scott Ambler's Agile Modeling gives principles for making models (diagrams such as UML) in an agile way:
Principle | Meaning |
|---|---|
Model with a purpose | Know why you are drawing the model and who it is for. |
Use multiple models | Use only the few models that add real insight. |
Travel light | Keep only the models that will provide long-term value; discard the rest. |
Content over representation | A useful whiteboard sketch beats a perfect but empty diagram. |
Know the models and tools | Understand each model's strengths and weaknesses. |
Adapt locally | Fit the approach to your team's needs. |
This matters for the UML lectures later in the course: draw diagrams that help the team think and communicate, not diagrams for their own sake.
Word help model = a simplified picture of a system, such as a UML diagram |
§5.2 Agile Unified Process (AUP)
Slide L06-S13
AUP (also Scott Ambler) keeps the four phases of the Unified Process (Lecture 9 covers UP fully) but works in short iterations inside them: "serial in the large, iterative in the small".
- Phases (in order): inception, elaboration, construction, transition.
- Inside every iteration: modeling, implementation, testing, deployment, configuration and change management, project management, environment management.
- Fits organisations that need visible phases and milestones (e.g. banks, government) but want agile iterations.
§6 Choosing an agile model
Slides L06-S14 to L06-S15
§6.1 Which model fits?
Slide L06-S14
If the project ... | Consider |
|---|---|
Builds a new product with a small team and regular demos | Scrum (often with XP practices) |
Needs strong code quality, frequent change and close customer contact | XP |
Handles a stream of unpredictable requests (support, maintenance) | Kanban |
Has a fixed deadline and budget, but flexible features | DSDM |
Must show formal phases and milestones in a large organisation | AUP |
Is very large, with many teams | A scaling framework (e.g. LeSS or SAFe) built on Scrum and Lean ideas |
As in Lectures 2 and 3: there is no best model, only the best fit, and mixing is normal.
§6.2 Worked activity: choose the model
Slide L06-S15
Project | Good choice | Reason |
|---|---|---|
A. UAF IT help desk: bug reports and small requests arrive every day, no fixed releases | Kanban | Continuous flow; WIP limits keep the queue moving; lead time measures service. |
B. Punjab land-record update: fixed go-live date and budget set by the government; some features negotiable | DSDM | Fix time and cost; MoSCoW decides what is dropped; timeboxes. |
C. New farmer marketplace app by a 5-person startup that demos to investors every 2 weeks | Scrum (+ XP) | Sprints with reviews match the demo rhythm; XP keeps code quality. |
D. Bank's core system upgrade: management wants formal phases and sign-offs, team wants iterations | AUP | Serial phases with milestones, iterative work inside. |
Accept other choices with good reasons (e.g. Scrumban for A).
§7 Common mistakes
Slides L06-S16
§7.1 Five mistakes
Slide L06-S16
Mistake | Correct idea |
|---|---|
"Kanban means no rules." | Kanban has WIP limits and explicit policies; it just has no sprints or fixed roles. |
"A Kanban board is any to-do list." | Without WIP limits and flow measurement it is only a task list. |
"Lead time and cycle time are the same." | Lead time starts at the request; cycle time starts when work begins. |
"DSDM fixes the features." | DSDM fixes time and cost; features vary using MoSCoW. |
"Agile means no models or diagrams." | Agile Modeling: make useful models with a purpose, and travel light. |
Summary
- The agile family shares the manifesto values but differs in focus: XP (engineering), Scrum (sprints), Kanban (flow), Lean (waste), DSDM (fixed time and cost), Agile Modeling (light models), AUP (agile inside UP phases).
- Kanban: visualise the work, limit WIP, manage flow, make policies explicit, improve; a pull system with no sprints.
- Flow metrics: lead time (request → done), cycle time (start → done), throughput; Little's Law: lead time = WIP ÷ throughput.
- Lean: seven principles, starting with eliminate waste.
- DSDM: fix time and cost, vary features (MoSCoW, timeboxing, 80/20).
- Agile Modeling: model with a purpose, travel light. AUP: serial in the large, iterative in the small.
- Choose the model that fits the project; mixing is normal.
- Before Lecture 07: revise Lectures 1-6 for Quiz 1 (week 4); read Pressman Ch. 1 and 2.1 for Lecture 07.
Word bank
Word | Simple meaning | Example |
|---|---|---|
Kanban | a visual system for managing the flow of work | a Trello board with WIP limits |
WIP limit | maximum number of items allowed in a column | In Progress (max 3) |
pull system | take new work only when there is capacity | a developer pulls the next card when free |
bottleneck | the stage where work piles up | five cards waiting in Testing |
lead time | time from request to done | added day 1, done day 4 = 3 days |
cycle time | time from start of work to done | started day 2, done day 4 = 2 days |
throughput | items finished per unit of time | 2 cards per day |
Little's Law | lead time = WIP ÷ throughput | 6 ÷ 2 = 3 days |
Lean | an approach focused on removing waste | dropping a feature nobody uses |
waste | effort that adds no value | waiting a week for an approval |
DSDM | agile method that fixes time and cost and varies features | government project with a fixed go-live date |
timebox | fixed deadline that does not move | 2-week build iteration |
Pareto principle | 80/20 rule | 80% of value in 20% of time |
Agile Modeling | principles for light, useful models | a whiteboard sketch photographed |
AUP | Agile Unified Process: UP phases with agile iterations | a bank upgrade with formal milestones |
Scrumban | a mix of Scrum and Kanban | sprints plus WIP limits |
Self-check questions
Try each question without looking. Then check your answer in the section shown.
# | Question | See |
|---|---|---|
1 | Name four members of the agile family and the main focus of each. | §1.2 |
2 | What does the word kanban mean, and where did Kanban come from? | §2.1 |
3 | List the five core practices of Kanban. | §2.1 |
4 | Why do WIP limits help a team finish work faster? Use the dhaba example. | §2.2 |
5 | Differentiate lead time from cycle time with an example. | §2.3 |
6 | A team has 8 items in progress and finishes 4 per day. What is the average lead time? What if WIP drops to 4? | §2.3 (2 days; 1 day) |
7 | Give four differences between Scrum and Kanban. | §2.4 |
8 | List the seven principles of Lean software development. | §3.1 |
9 | What does DSDM fix and what does it allow to vary? What is the 80/20 idea? | §4.1 |
10 | Explain "travel light" in Agile Modeling. | §5.1 |
11 | What does "serial in the large, iterative in the small" mean in AUP? | §5.2 |
12 | Which agile model would you choose for a university IT help desk, and why? | §6.2 |
Further reading
- Pressman & Maxim, 8th ed., sections 5.5.2-5.5.4 (DSDM, Agile Modeling, Agile Unified Process).
- Sommerville, 10th ed., section 3.4 (Scaling agile methods).
- Kanban and Lean: teacher notes (these notes); optional: Anderson, *Kanban* (2010), chapter 1.