Beta This is new guidance. Complete our quick 5-question survey to help us improve it.
Agile methods: an introduction
There are many agile methods you can use when building your service, each has its own set of tools and techniques.
This guide introduces the 3 most popular agile methods:
Meeting the Digital Service Standard
Popular agile methods explained
Scrum is the most commonly used agile method.
It allows a highly structured model with clearly defined roles and responsibilities - this can be particularly useful for traditionally structured organisations that are moving to agile.
Learn more about the features of Scrum in the Scrum Guide, written by the developers of Scrum, Ken Schwaber and Jeff Sutherland.
Kanban as a development method was inspired by production systems that focus on reducing waste and improving quality, like those created by Toyota.
Kanban is a way of visualising and improving your current working practices so that work flows through a system quickly.
A fast and smooth flow of work means you can:
- deliver value quickly and predictably
- get early feedback to find out whether your product or service is meeting user needs
Read the following to learn more about Kanban:
Lean software development, like Kanban, is adapted from lean manufacturing principles like the Toyota Production System.
The principles of Lean aim to help your team focus on:
- reducing waste
- delivering quickly
- learning and improving
- using evidence and data to make decisions
Read the following to learn more about Lean:
Working with multiple agile methods
You don’t have to work with just one method, you can choose tools and techniques from several to meet your team’s needs.
Each method has its own language for describing basic tools and techniques, the important thing is to understand:
- why you’ve chosen a tool or technique
- its agile objective
Deciding which methods to work with
Scrum is a good starting point if your team is new to agile working.
Your team will generally find Scrum most useful when you’re:
- building a new product or service
- enhancing existing features
- adding new features in each ‘sprint’ (a fixed period of time)
When you’re running your live service and have urgent requests you may find sprints constraining and want to move to a flow-based method like Kanban.
But you can still keep using many of the activities associated with Scrum, like daily stand-up meetings, retrospectives and regular reviews of progress.
Kanban helps your team to:
- find the bottlenecks in your processes
- control the amount of work you’re doing
- predict your output based on actual delivery
It’s particularly useful if at times when your team needs to react quickly to changing priorities.
Lean allows your team to focus on learning as quickly as possible.
Lean’s tools and techniques are particularly useful when your team is first discovering what your users’ needs are and deciding how to address those needs.
You may also find these guides useful:
- Published by:
- Agile delivery community
- Last update:
Iteration based on SME feedback
Adam Maddison has asked for changes to this guide. We are also iterating it to improve it.