Slide 2
Last lecture: Scrum in one minute
Accountabilities
Artifacts
Events
Product Owner · Scrum Master · Developers
Product backlog · Sprint backlog · Increment
Sprint · Planning · Daily scrum · Review · Retrospective
Exit ticket check: "Scrum Master: must not assign tasks to Developers." Good. "Product Owner: must not code." Wrong: a PO may also be a developer.
Today: Scrum works in fixed sprints. Kanban works with NO sprints, as a continuous flow. Then Lean, DSDM, Agile Modeling and AUP.
SE Lecture 6
Recap
Sheet 02 of 19
Slide 3
Learning outcomes
SLO 6.1
Explain Kanban: WIP limits, flow, lead time, cycle time, throughput
→ CLO1 · C2 Understand
SLO 6.2
Describe Lean, DSDM, Agile Modeling and AUP in brief
→ CLO1 · C2 Understand
SLO 6.3
Choose a suitable agile model for a project and justify it
→ CLO1 · C3 Apply
CLO1: Explain application of software engineering processes and techniques to various types of software.
SE Lecture 6
Outcomes
Sheet 03 of 19
Slide 4
Today's plan: 50 minutes
0-5 min
Recap and exit tickets
Coming up
5-8 min
Outcomes and plan
- Practical 06: your own Kanban board with WIP limits
- Quiz 1 next week: Lectures 1-6
- Lecture 07: the nature of software
8-22 min
The agile family; Kanban, WIP limits, flow
22-32 min
Lean, DSDM, Agile Modeling, AUP
32-35 min
Choosing a model
35-43 min
Activity: choose the model
43-48 min
Common mistakes and recap quiz
48-50 min
Homework and exit ticket
SE Lecture 6
Plan
Sheet 04 of 19
Slide 5
The agile family: one set of values, different focus
XP
Scrum
Kanban
Lean
Engineering practices
Managing work in sprints
Flow of work, WIP limits
Removing waste
- Mixing is normal
- Scrum + XP
- Scrum + Kanban = "Scrumban"
DSDM
Agile Modeling
AUP
Fixed time and cost
Useful, light models
Agile inside UP phases
Light cards: studied already. Dark cards: today.
SE Lecture 6
Agile family
Sheet 05 of 19
Slide 6
Kanban: visualise the flow of work
- Kanban = Japanese for "signboard" or "visual card".
- From the Toyota Production System. Adapted for software by David J. Anderson (2010).
Five core practices
Visualise the work
Limit work in progress (WIP)
Manage flow
No sprints. No required roles. Work flows continuously; a person PULLS the next card only when there is space.
Make policies explicit
Improve collaboratively
Word help
WIP = work in progress: started, not finished
SE Lecture 6
Kanban
Sheet 06 of 19
Slide 7
WIP limits: stop starting, start finishing
Backlog
- Ready
- max 5
- In Progress
- max 3
- Testing
- max 2
Done
Menu
Order
Pay
Report
Rate
Order
Pay
Report
Rate
Menu
Pay
Report
Rate
Order
Testing is FULL (2 of 2): nobody may add a card. Developers help test first.
Real-world example: the dhaba kitchen
Three stoves = WIP limit 3. Taking 15 orders in a rush does not cook food faster; orders only wait longer. Good kitchens take new orders as fast as they can finish them.
SE Lecture 6
Kanban
Sheet 07 of 19
Slide 8
Measuring flow, and Little's Law
Lead time
request → done
Added day 1, done day 4: 3 days
Cycle time
start → done
Started day 2, done day 4: 2 days
Throughput
items done per day
10 cards in 5 days: 2 per day
- Little's Law
- Lead time = WIP ÷ Throughput
- 6 in progress, 2 done per day → 6 ÷ 2 = 3 days
- WIP limit 4, still 2 per day → 4 ÷ 2 = 2 days
- Less WIP = each item finishes sooner
SE Lecture 6
Flow
Sheet 08 of 19
Slide 9
Scrum and Kanban compared
Scrumban: sprints and reviews from Scrum, plus WIP limits from Kanban.
SE Lecture 6
Comparison
Sheet 09 of 19
Slide 10
Lean software development
Mary and Tom Poppendieck (2003), from Toyota's Lean thinking: seven principles
Eliminate waste
Build quality in
Waste in a fee-challan system
Create knowledge
Defer commitment
- A fancy PDF designer nobody uses (extra feature).
- A week waiting for finance approval (delay).
- The same rounding bug fixed three times (defects).
Deliver fast
Respect people
Optimise the whole
Word help
waste = effort that gives the customer no value defer = delay until later
SE Lecture 6
Lean
Sheet 10 of 19
Slide 11
DSDM: fix time and cost, vary the features
DSDM life cycle (Pressman)
Time: FIXED
Feasibility study
Cost: FIXED
Business study
Features: VARY (MoSCoW)
Functional model iteration
80/20 (Pareto): about 80% of an application can often be delivered in 20% of the time needed for 100%.
Design and build iteration
Implementation
UK, 1994 · timeboxing · active users
Word help
timebox = a deadline that does not move
SE Lecture 6
DSDM
Sheet 11 of 19
Slide 12
Agile Modeling (Scott Ambler)
- Model with a purpose
- Know why and for whom
- Use multiple models
- Only the few that add insight
- Travel light
- Keep only models with long-term value
- Content over representation
- A useful sketch beats a pretty empty diagram
- Know the models and tools
- Strengths and weaknesses of each
- Adapt locally
- Fit your team's needs
Why it matters: from week 9 we draw UML. Draw diagrams that help the team think and talk, not diagrams for their own sake.
SE Lecture 6
Agile Modeling
Sheet 12 of 19
Slide 13
Agile Unified Process (AUP)
"Serial in the large, iterative in the small"
Inception
Elaboration
Construction
Transition
Phases in order (serial) · short iterations inside each phase (amber circles)
Fits: banks, government and large firms that need formal phases and milestones but want agile iterations. Full UP comes in Lecture 9.
- Inside every iteration
- Modeling, implementation, testing, deployment
- Configuration and change management
- Project management, environment management
SE Lecture 6
AUP
Sheet 13 of 19
Slide 14
Which agile model fits?
Remember (Lectures 2 and 3): no best model, only the best fit. Mixing is normal.
SE Lecture 6
Choosing
Sheet 14 of 19
Slide 15
Activity: choose the model
Each row gets one project. Choose a model and give ONE reason.
A. UAF IT help desk
B. Land-record update
Bug reports and small requests every day; no fixed releases.
Government fixes go-live date and budget; some features negotiable.
C. Farmer marketplace startup
D. Bank core system upgrade
minutes
5 developers; demo to investors every 2 weeks.
Management wants formal phases; the team wants iterations.
- 6 min in groups
- 2 min to share
SE Lecture 6
Activity
Sheet 15 of 19
Slide 16
Common mistakes
"Kanban means no rules."
✗
WIP limits and explicit policies are rules
"Any to-do list is a Kanban board."
✗
Without WIP limits and flow it is only a list
"Lead time = cycle time."
✗
Lead: request → done; cycle: start → done
"DSDM fixes the features."
✗
Time and cost fixed; features vary
"Agile means no diagrams."
✗
Model with a purpose; travel light
SE Lecture 6
Mistakes
Sheet 16 of 19
Slide 17
Recap quiz: hands up
What does the word "kanban" mean?
Lead time vs cycle time: what is the difference?
WIP = 6, throughput = 2 per day. Average lead time?
What does DSDM fix, and what does it vary?
AUP in five words?
SE Lecture 6
Recap quiz
Sheet 17 of 19
Slide 18
Before the next lecture
Quiz 1 next week
Read and do
- Covers Lectures 1-6
- Process models, agile values, XP, Scrum, Kanban and others
- Revise the comparison tables in your notes
- Pressman 5.5.2-5.5.4 (DSDM, AM, AUP)
- For Lecture 07: Pressman Ch. 1 and 2.1
- Team: add WIP limits to your board's In Progress and Testing lists (Practical 06)
- Next: Lecture 07, The Nature of Software
SE Lecture 6
Homework
Sheet 18 of 19
Slide 19
Exit ticket
On a small piece of paper, with your name and roll number:
Which agile model (or mix) suits YOUR semester project best, and why? One sentence.
One question you still have.
Questions?
SE Lecture 6
Exit ticket
Sheet 19 of 19