Agile, Scrum and Kanban: A Plain Comparison
You will hear us talk about Agile, Scrum and Kanban throughout your project, and the words can sound interchangeable when they are not. This article explains what each one means and how we choose the right approach for the work in front of us.
Our aim is simple: pick the way of working that gives you the most visibility and the fastest feedback, without drowning either side in process for its own sake.
What the Three Terms Actually Mean
Agile is a mindset, not a method. Scrum and Kanban are two practical ways of putting that mindset into action, and we often blend them to suit your project.
- Agile: a set of values favouring small, frequent releases and close collaboration with you.
- Scrum: work organised into fixed-length sprints with set ceremonies and roles.
- Kanban: a continuous flow of work pulled from a prioritised board, with limits on work in progress.
How We Decide Which to Use With You
We base the choice on how your work arrives and how predictable it is, then confirm it with you at kick-off.
- If scope is well defined and steady, Scrum sprints give you a reliable rhythm.
- If priorities shift often or work is support-led, Kanban lets us react without breaking a sprint.
- If your project has both, we run a hybrid and review it together every few weeks.
Frequently Asked Questions
Do I have to learn all this terminology?
Not at all. We handle the mechanics; this is background so the language in our updates makes sense to you.
Can we change approach partway through?
Yes. We review how we are working at retrospectives and adjust whenever it would serve the project better.
If you need a hand with any of this, your Progressive Robot delivery team is ready to help. Raise a ticket from the Support area of your client portal or speak to your account manager and we will guide you through the next steps.