Chapter 1 · How Software Gets Built
Agile, Scrum and Kanban
- Page 4 of 18
- 18 min read
On the previous page, Process Models: Waterfall, Incremental, RAD and Big Bang, the ClinicQueue team chose to work in increments and to improve each part through feedback. That choice raises practical questions. How long is each cycle? Who decides what comes next? How does the team know whether it is getting better? Agile is a set of values and principles that answers the "why" of this way of working, and Scrum and Kanban are two widely used ways to put it into daily practice.
This page quotes the Agile Manifesto exactly, clears up common misunderstandings, and then walks through one Scrum sprint and one Kanban board for ClinicQueue. It describes Scrum as the 2020 Scrum Guide defines it, which is stricter than how the word is often used at work.
What you will learn
- The four values of the Agile Manifesto (2001), word for word, and the idea of its twelve principles.
- Why Agile is a mindset rather than one method, and why "Agile means no documentation or no planning" is wrong.
- Scrum per the 2020 Scrum Guide: three accountabilities, five events, three artifacts and their commitments, shown in a ClinicQueue sprint.
- Kanban: visualise work, limit work in progress and manage flow, with a text board.
- How Scrum and Kanban differ, and which suits a small team or a solo freelancer.
The Agile Manifesto
The four values
In February 2001 (11 to 13 February), seventeen software practitioners met at Snowbird, Utah, and wrote the Manifesto for Agile Software Development. Its core is four values. Here they are exactly as published:
"Through this work we have come to value:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the left more."
Read the last sentence twice. The Manifesto does not say processes, documentation, contracts and plans are bad. It says that when they compete, the items on the left win. Here is what each value meant in practice for ClinicQueue.
| Value | What it does not mean | ClinicQueue in practice |
|---|---|---|
| Individuals and interactions over processes and tools | No process, no tools | When Kwame finds a confusing bug, he walks over to Farhan instead of only filing a ticket and waiting |
| Working software over comprehensive documentation | No documents | Nadia judges progress by trying the booking screen every two weeks, but the data-privacy decisions are still written down |
| Customer collaboration over contract negotiation | No contract | Nadia and Lena meet regularly to adjust priorities instead of arguing over the original wording |
| Responding to change over following a plan | No plan | When walk-in patients turn out to matter, the plan for the next weeks changes; there is still a plan |
The twelve principles
Behind the values are twelve principles. A few, quoted exactly:
- "Our highest priority is to satisfy the customer through early and continuous delivery of valuable software."
- "Welcome changing requirements, even late in development."
- "Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale."
- "Working software is the primary measure of progress."
- "Simplicity--the art of maximizing the amount of work not done--is essential."
- "At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly."
The other principles cover close daily work between business people and developers, motivated people who are trusted, face-to-face conversation, a pace the team can keep up indefinitely, attention to technical excellence and good design, and self-organising teams. The full list is short and worth reading on the Manifesto's website (agilemanifesto.org).
Agile is a mindset, not one method
The Manifesto does not tell you which meetings to hold or how long a cycle is. It is a set of values and principles. Specific methods, such as Scrum and Kanban, are ways of applying them. A team can follow Scrum's rules perfectly and still not be agile (for example, by ignoring what users say at every review), and a team can be agile without using any named method.
| Misunderstanding | What is actually true |
|---|---|
| "Agile means no documentation." | The Manifesto says there is value in documentation; it values working software more. Write the documents someone will use. |
| "Agile means no planning." | Agile teams plan often and in small steps: every cycle has planning, and the longer plan is updated as they learn. |
| "Agile means no deadlines." | Short fixed cycles make dates more visible, not less. What changes is that scope adapts to the date. |
| "Agile and Scrum are the same thing." | Scrum is one framework that applies Agile values. Kanban and others are different ways. |
| "The customer can change anything at any time." | Change is welcome, but through an agreed route, such as reordering the backlog, not by interrupting developers mid-task. |
Scrum, as the 2020 Scrum Guide defines it
Scrum is a lightweight framework for building products in short cycles. Its official definition is The 2020 Scrum Guide (published November 2020 on scrumguides.org). Many workplaces add their own practices on top and still call it Scrum; this section describes only what the guide itself contains.
Three accountabilities
A Scrum Team is small, "typically 10 or fewer people", and has three accountabilities. The 2020 guide deliberately calls them accountabilities, not roles: they describe what someone is answerable for, not a job title. The guide describes each one in more detail; the table gives only the gist in plain words.
| Accountability | In short (plain words) | On ClinicQueue (for this walkthrough) |
|---|---|---|
| Product Owner | The value of the product; in practice, keeping the Product Backlog ordered and clear | Nadia, who knows what the clinic needs most, with Lena helping her write backlog items |
| Scrum Master | Helping the team use Scrum well and work effectively, for example by getting obstacles out of the way | Lena |
| Developers | Building a usable Increment each sprint and planning that work | Farhan and Aiko; when the team uses Scrum it also counts Kwame (tester) and Omar (designer) as Developers, because they help build each Increment |
Notice what is missing: the guide never mentions a project manager. It says only that "Each Sprint may be considered a short project." Project Management and the Roles in a Software Team looks at how project management fits around a Scrum team.
Five events
The Sprint is a fixed-length event of one month or less, and it "is a container for all other events". Two weeks is a common choice, but it is a choice, not a rule.
| Event | Purpose | Maximum time-box (for a one-month sprint) |
|---|---|---|
| Sprint | Contains all the work and the other four events | One month or less |
| Sprint Planning | Decide why this sprint is valuable (the Sprint Goal), what can be done and how | 8 hours |
| Daily Scrum | The Developers check progress towards the Sprint Goal and adjust the plan | 15 minutes, every day |
| Sprint Review | Show the result to stakeholders and decide together what to do next | 4 hours |
| Sprint Retrospective | The team looks at how it worked and picks improvements | 3 hours |
For shorter sprints, these events are usually shorter.
Three artifacts and their commitments
Scrum has three artifacts (the guide's spelling), and each one has a commitment that gives it a clear purpose.
| Artifact | What it is | Its commitment | ClinicQueue example |
|---|---|---|---|
| Product Backlog | The ordered list of everything that might be needed in the product | Product Goal | "Patients can book and be reminded without phoning the clinic" |
| Sprint Backlog | The Sprint Goal, the items chosen for this sprint, and the plan to deliver them | Sprint Goal | "A patient can book a slot online and Rina sees it in today's list" |
| Increment | A usable step towards the Product Goal, added to all earlier increments | Definition of Done | "Done" = reviewed, tested by Kwame, works on a small phone, deployed to the test server |
A ClinicQueue sprint, walked through
Invented scenario:
Sprint 1, two weeks (10 working days). Product Owner: Nadia. Scrum Master: Lena.
Day 1 SPRINT PLANNING (3 h)
Nadia explains the top backlog items. Team agrees the Sprint Goal:
"A patient can book a slot online and Rina sees it in today's list."
Developers pick 5 items and split them into tasks.
Day 2-9 DAILY SCRUM (15 min, same time each day)
Day 4: Aiko says the slot picker is slow on old phones; Omar and Aiko pair
on it after the meeting. Kwame says he needs test data by Day 6.
Day 7: Farhan finds double bookings are possible. The team agrees this
blocks the Sprint Goal and moves "confirmation SMS" out of the sprint.
Day 10 SPRINT REVIEW (1.5 h)
Nadia and Rina book real-looking slots on a phone. Rina asks for the
list to be sorted by time. Nadia adds it to the Product Backlog.
SPRINT RETROSPECTIVE (1 h)
Went well: pairing. Problem: test data arrived late.
Improvement for sprint 2: Kwame and Farhan prepare test data on Day 1.Look at what Scrum gave the team here. The Sprint Goal let them drop a less important item without arguing about the whole plan. The Daily Scrum surfaced two problems within a day. The Review put the software in front of the customer and a real user. The Retrospective turned a problem into one concrete change.
What is not in the Scrum Guide
Many teams use story points (relative sizes for backlog items) and velocity (how many points the team usually finishes per sprint). These are common practices, and Planning, Estimation and Scheduling shows how to use them, but they are not part of the 2020 Scrum Guide. The same is true of task boards, burndown charts and fixed two-week sprints. They can be useful, but a team that does not use them can still be doing Scrum.
Kanban: visualise, limit, flow
Kanban takes a different route. It has no sprints and no required roles. It starts from the work the team already does and improves the flow of that work. Two published guides describe it, from different bodies, and they list practices differently:
- The Kanban Guide from Kanban University lists six general practices: "Visualize", "Limit Work in Progress (WIP)", "Manage Flow", "Make Policies Explicit", "Implement Feedback Loops" and "Improve Collaboratively, Evolve Experimentally".
- The Kanban Guide (kanbanguides.org, version May 2025) lists three practices: defining and visualizing a workflow, actively managing items in a workflow, and improving a workflow.
Both share a common core, which this page uses: visualise the work, limit work in progress, and manage the flow. The Kanban Guide defines work in progress (WIP) as "The number of work items started but not finished".
A Kanban board for ClinicQueue maintenance
After version 1.0 is released, the work changes. Instead of planned features, the team gets a steady stream of bug reports and small requests from Rina and Nadia. It cannot wait two weeks for the next sprint to fix a broken reminder. Lena suggests a Kanban board for this maintenance work.
Board:
ClinicQueue maintenance board (invented) WIP limits in [brackets]
TO DO | IN PROGRESS [2] | REVIEW + TEST [2] | DONE
---------------------+-------------------------+-------------------------+------------------
Holiday dates shown | SMS not sent for 07:00 | Sort today's list by | Typo in reminder
as open slots | bookings (Farhan) | time (Aiko / Kwame) | Logo too large
Add clinic phone to | Booking for a child | | on small phones
the confirmation | (Aiko) | |
Export monthly list | | |
for Nadia | | |
Policy: pull from the column on the left only when your column is below its limit.
Urgent bugs that stop booking go to the top of TO DO.Here is how the three core ideas work on this board.
- Visualise: everyone, including Nadia, can see what is waiting, what is being worked on and what is done. Hidden work, like Farhan quietly fixing something nobody asked for, becomes visible.
- Limit WIP: "In progress" has a limit of 2 and already has 2 items. Nobody may start "Holiday dates" until one of them moves on. This feels slow, but it stops the common pattern of five half-finished items and nothing done. Anyone who is free helps Kwame test instead.
- Manage flow: the team watches how long items take from start to done and where they wait. If items keep piling up in "Review + test", the bottleneck is testing, and the fix is to help Kwame, not to start more work.
The Kanban Guide names four flow measures that teams can track: WIP, throughput (items finished per period), work item age (how long a started item has been in progress) and cycle time (how long an item took from start to finish). For ClinicQueue, a simple start is to write the start and finish date on each card and look at the numbers once a week.
Scrum or Kanban?
| Question | Scrum (2020 guide) | Kanban |
|---|---|---|
| Rhythm | Fixed sprints of one month or less | Continuous flow; no sprints |
| Roles | Three accountabilities: Product Owner, Scrum Master, Developers | No required roles |
| How much work at once | What the team plans for the sprint | WIP limits per stage of the workflow |
| Changing priorities | Usually between sprints; the Sprint Goal protects the current sprint | Any time: the next item pulled is the top of the list |
| Fixed meetings | Five events, with time-boxes | None required; teams add regular reviews as they need |
| Fits well | Building a product in planned increments with a customer who can review regularly | Support, maintenance and work that arrives unpredictably |
Practitioners argue about which is better, and both sides have reasons. Scrum's fixed rhythm gives regular moments to plan, show and improve, which helps a new team. Kanban's flexibility suits work that cannot wait for a sprint and avoids meetings a team may not need. Many teams combine them, for example Scrum events with a WIP-limited board. ClinicQueue did both at different times: Scrum while building version 1, Kanban for maintenance afterwards.
A small team of three to six people building a new product, with a customer who can attend a review every two weeks, will usually get more from Scrum's structure. A solo freelancer cannot fill three accountabilities in any meaningful way and does not need a Daily Scrum with themselves. A personal Kanban board with a WIP limit of one or two, plus a short weekly review with the client, applies the same Agile values at a cost that fits one person.
Where this shows up at work
- Job advertisements often ask for "experience with Agile/Scrum". In interviews, being able to explain the accountabilities, events and artifacts accurately stands out.
- Support and operations teams often use Kanban boards because incidents and requests do not arrive on a schedule.
- Freelancers who show a client working software every week or two, and let the client reorder the remaining list, are applying the Agile values even without Scrum.
- Teams in transition commonly say they "do Scrum" while skipping retrospectives or reviews. Knowing what the guide contains helps you notice what is missing.
Common mistakes
- Using Agile as an excuse for no documents or no plan. It bites when nobody can explain a decision months later. Fix: quote the Manifesto's last sentence; keep the documents and plans that someone will use, and update them.
- Treating the Daily Scrum as a status report to a manager. It turns into a long meeting where people defend themselves. Fix: keep it to 15 minutes, for the Developers, focused on the Sprint Goal and on what blocks it.
- Saying "a sprint must be two weeks" or "Scrum has a project manager". Neither is in the 2020 Scrum Guide. Fix: say sprints are one month or less, and use the three accountabilities.
- A Kanban board without WIP limits. It shows the work but does not improve flow, so everyone starts new items and few finish. Fix: set a limit for each "in progress" column and pull only when below it.
- Using velocity to compare teams or to pressure people. Points are a team's own relative scale, so the numbers stop being honest. Fix: use velocity only for the team's own forecasting.
Try it yourself
- Easy: Label each statement as true or false according to the Agile Manifesto or the 2020 Scrum Guide, and correct the false ones: (a) The Manifesto says documentation has no value. (b) A Scrum sprint can be three weeks long. (c) The Daily Scrum is a 15-minute event for the Developers. (d) Story points are one of Scrum's artifacts. (e) The commitment for the Increment is the Definition of Done.
- Medium: Kwame's test column on the maintenance board has a WIP limit of 2. Today it holds 2 items. "In progress" also holds 2 items, one of them Aiko's, and she has just finished coding it. What should Aiko do, and why? Then give two possible longer-term fixes if this keeps happening, and the trade-off of each.
- Hard: Omar is also a freelance designer. A client asks him to build a small portfolio website with a booking form, over six weeks. The client wants weekly updates and keeps getting new ideas. Choose Scrum, Kanban or a mix for Omar, design the process in a few lines (rhythm, board columns and WIP limit, how the client changes priorities, how Omar reviews his own way of working), and explain how your design reflects at least three of the four Agile values.
Answers
- (a) False: it says there is value in the items on the right, including documentation, but working software is valued more. (b) True: sprints are fixed-length events of one month or less, so three weeks is allowed. (c) True. (d) False: the three artifacts are the Product Backlog, the Sprint Backlog and the Increment; story points are a common practice outside the guide. (e) True (Product Backlog: Product Goal; Sprint Backlog: Sprint Goal).
- Aiko should not push her item into "Review + test", because that column is at its limit. She should help clear it, for example by testing one of Kwame's items together with him, or by reviewing code there; her finished item waits in "In progress" until there is space, and she does not start a new item. Helping finishes work sooner than starting more. Possible longer-term fixes: (1) developers regularly help with testing, which keeps the limit but needs Kwame to share test know-how; (2) raise the limit to 3, which reduces waiting but hides the bottleneck and increases unfinished work; (3) write more automated tests during coding, which needs time now but makes testing faster later. A good answer respects the WIP limit, explains why (finish before starting), and gives fixes with their costs.
- Model answer: A mix, mostly Kanban, because one person cannot fill three accountabilities and the client's ideas arrive unpredictably. Rhythm: a 30-minute call every Friday where Omar shows the working site (like a Sprint Review). Board: To do, Doing (WIP 1), Waiting for client, Done. The client's new ideas go into a separate "Ideas" list; on Friday the client reorders the top of "To do", so changes are welcome without breaking work in progress. After each call, Omar spends 10 minutes noting one thing to do better next week (like a retrospective). Values: customer collaboration (weekly calls and client-ordered list instead of arguing over the original quote); working software (the client sees the site, not a report); responding to change (new ideas enter the list each week); individuals and interactions (a short conversation instead of long email threads). A good answer justifies the choice for a solo worker, includes a WIP limit, gives the client a clear route for changes, includes a regular improvement step, and links the design to named Agile values.
Summary
- The Agile Manifesto (2001) has four values and twelve principles; its last sentence says the items on the right still have value, so Agile does not mean no documents or no plans.
- Agile is a mindset; Scrum and Kanban are ways of applying it.
- The 2020 Scrum Guide has three accountabilities (Product Owner, Scrum Master, Developers), five events (the Sprint of one month or less plus Planning, Daily Scrum, Review and Retrospective), and three artifacts with commitments (Product Goal, Sprint Goal, Definition of Done).
- Kanban visualises work, limits work in progress and manages flow; it has no sprints and no required roles. Name the guide when you list its practices.
- Scrum suits planned product building with regular customer reviews; Kanban suits maintenance and unpredictable work; a solo freelancer usually needs a light Kanban board with a weekly client review.
Next: Requirements Engineering: Finding Out What to Build starts chapter 2: how to discover what Nadia, Rina and the patients actually need before it goes into any backlog.

