Kanban Service Level Expectations and how to use them in Scrum


One of the new concepts we introduce in the Kanban Guide for Scrum Teams is the Service Level Expectation, defined as:

An SLE forecasts how long it should take a given item to flow from start to finish within your workflow. The SLE itself has two parts: a period of elapsed days and a probability associated with that period (e.g., “85% of work items will be finished in 8 days or less” which can also be stated as “8 days with 85% confidence/probability”).

The term expectation is key here. We’re not talking about commitments or promises. While it seems like an SLE is mainly serving the team’s stakeholders its primary purpose is actually internally focused. The Development Team is using that expectation as a flow transparency, inspection, and adaptation mechanism. The team can start to actually compare active in-flight work to their SLE and look for items that are at risk of missing the SLE.

As work ages without completing, it becomes more and more likely this work item would not meet the team’s SLE. For example, once a work item reaches a point where its age is now at the point where half of the team’s work items have already been completed, it’s a clear indication that there’s more risk for this item than the typical item. We basically learn about the increased risk to specific items the more time passes without them completing. Common sense, no? The idea is that by visualizing these items and that growing risk we can focus the team’s tactical inspection and adaptation during the Daily Scrum on tackling these risky items.

Let’s look at an example. Let’s assume that indeed we have a Development Team that learns from their cycle time scatterplot that 85% of their work items finish in 8 days or less and 50% of the items actually finish within 4 days. They have item A which has been active for 5 days already and item B which has been active for 3 days. Which of these items should the team feel more confident they can finish within their 8 days or less SLE? Without further information about where each of the items is in their workflow, they should feel more confident about item B aged less. Item A has already been active more than it takes for 50% of the cards to finish, so it’s quite a strong signal that there’s a flow risk to it. Basically, with each day that passes in which a work item doesn’t finish, the probability that a work item will not meet its SLE increases”.

Beyond its usefulness for in-Sprint flow focus, SLEs are also useful during Sprint Retrospectives. The “surprise” or “anomaly” of missing your SLE can drive an improvement discussion. I previously wrote about the Sprint Forecast as an expectation and the learning/improvement value of having an expectation that you miss vs having no expectations.

This “no expectations” problem is actually a common concern for Scrum practitioners when they look at Kanban. The Sprint Forecast/Commitment provides that expectation. Kanban without SLEs indeed is missing something. Having WIP limits as expectations improves flow but doesn’t help with specific items that aren’t flowing well.

How should a Scrum Team come up with their SLE? First of all – The SLE relates to the Development Team. They should figure out what their SLE should be. If possible based on historical cycle times. If there isn’t enough data, make the best guess and replace it with empirical data-based information as soon as possible. If it isn’t based on historical cycle times, you cannot really expect to make any educated confidence-level determinations (like the one above) based on your SLE.

Also, SLEs aren’t SLA (Service Level Agreements). SLA is a loaded term that means different things in different contexts but generally is an external commitment about the service levels a team will provide. As mentioned an SLE is mainly internally focused.

Bottom line – SLEs are used by Scrum Teams to set flow expectations for themselves. SLEs are ideally created based on actual historical cycle time data. They are then used by teams to focus their flow inspection and adaptation effort – during the Sprint in the Daily Scrum and following the sprint in the Sprint Retrospective. They can also use in the Sprint Review when the team is working with stakeholders that care about the team’s cycle time.

Subscribe for Email Updates:



Agile Risk Management
Program Increment
Agile Program
Systems Thinking
Applying Agile Methodology
Agile Outsourcing
AI Artificial Intelligence
Large Scale Scrum
Kaizen Workshop
Agile Games and Exercises
Nexus Integration Team
Sprint Planning
Manage Budget Creation
Business Agility
PI Objectives
Perfection Game
Agile Basics
Jira admin
Professional Scrum Product Owner
Change Management
Lean Agile
RTE Role
Agile Testing Practices
Games and Exercises
Managing Risk on Agile Projects
Risk Management in Kanban
Lean Agile Leadership
Limiting Work in Progress
Product Ownership
Coaching Agile Teams
Lean Startup
Legacy Enterprise
Scrum Guide
Scrum Master Role
Lean and Agile Principles and Practices
Scrum and XP
Artificial Intelligence
Managing Projects
Built-In Quality
Effective Agile Retrospectives
speed at scale
Product Management
The Agile Coach
Agile and DevOps Journey
Software Development Estimation
What Is Kanban
Legacy Code
Kanban Basics
Continuous Integration
Lean Agile Management
Continuous Delivery
Story Slicing
Risk Management on Agile Projects
Agile Contracts Best Practices
Implementation of Lean and Agile
Scaled Agile Framework
Advanced Roadmaps
Agile Release Planning
Release Train Engineer
Sprint Iteration
SAFe DevOps
Lean Budgeting
System Team
Agile in the Enterprise
Agile Product Ownership
Reading List
Principles of Lean-Agile Leadership
Sprint Retrospectives
lean agile change management
Iterative Incremental Development
Nexus vs SAFe
Professional Scrum with Kanban
Risk-aware Product Development
Rapid RTC
ALM Tools
Engineering Practices
Introduction to ATDD
Agile Product Development
Continuous Improvement
Agile Project Management
Agile for Embedded Systems
Enterprise DevOps
Accelerate Value Delivery At Scale
Agile Community
Agile Mindset
Development Value Streams
Portfolio for Jira
Achieve Business Agility
Lean Software Development
ART Success
Daily Scrum
Agile Project
Scrum With Kanban
Agile Development
Scrum Values
Software Development
Agile Games
Agile Marketing
Jira Plans
Agile Israel
Process Improvement
Scrum Primer
Jira Cloud
Agile Assembly Architecture
A Kanban System for Software Engineering
Agile Israel Events
Hybrid Work
Scrum Master
An Appreciative Retrospective
Nexus and SAFe
Lean Agile Basics
IT Operations
Test Driven Development
Lean Risk Management
Lean-Agile Software Development
Releases Using Lean
PI Planning
ScrumMaster Tales
Acceptance Test-Driven Development
Quality Assurance
Lean Agile Organization
Operational Value Stream
System Archetypes
Kanban Game
Entrepreneurial Operating System®
Pomodoro Technique
Kanban Kickstart Example
Agile Exercises
The Kanban Method
Agile Release Management
System Integration Environments
Value Streams
Agile Delivery
Introduction to Test Driven Development
Certified SAFe
Kanban 101
speed @ scale
Continuous Deployment
Continuous Planning
Professional Scrum Master
Nexus and Kanban
Agile Techniques
Lean-Agile Budgeting
Elastic Leadership
Implementing SAFe
Agile India
Lean and Agile Techniques
Enable registration in settings - general

Contact Us

Request for additional information and prices

AgileSparks Newsletter

Subscribe to our newsletter, and stay updated on the latest Agile news and events

This website uses Cookies to provide a better experience
Shopping cart