Search
Close this search box.
Search
Close this search box.
Search
Close this search box.

Kanban Service Level Expectations and how to use them in Scrum

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp

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:

Categories:

Tags:

Kaizen Workshop
Legacy Code
Jira
Lean Agile Leadership
Implementing SAFe
lean agile change management
RTE
Quality Assurance
Value Streams
Nexus vs SAFe
Acceptance Test-Driven Development
Manage Budget Creation
Scrum Primer
Achieve Business Agility
QA
Kanban Basics
RSA
Scrum and XP
Nexus
Effective Agile Retrospectives
Scaled Agile Framework
Iterative Incremental Development
LAB
The Kanban Method
Agile India
Introduction to ATDD
Enterprise DevOps
Agile Product Ownership
Atlassian
Scrum.org
Program Increment
Coaching Agile Teams
Agile Testing Practices
Reading List
GanttBan
TDD
Scrum With Kanban
Slides
Amdocs
Agile Risk Management
IT Operations
Applying Agile Methodology
Agile and DevOps Journey
Product Management
Agile Assembly Architecture
Continuous Planning
Continuous Delivery
Continuous Integration
Nexus Integration Team
Covid19
Agile Project Management
Agile Contracts Best Practices
Scrum Master Role
Agile Project
DevOps
Lean Risk Management
PI Planning
Webinar
Professional Scrum Product Owner
Introduction to Test Driven Development
Professional Scrum Master
Artificial Intelligence
SAFe
Agility
Product Ownership
Elastic Leadership
speed @ scale
Nexus and SAFe
ScrumMaster Tales
User stories
Sprint Retrospectives
Kaizen
Release Train Engineer
RTE Role
PI Objectives
Kanban Kickstart Example
Agile
Video
ALM Tools
ART Success
A Kanban System for Software Engineering
Lean and Agile Principles and Practices
Lean Agile
Agile in the Enterprise
Agile Development
Business Agility
Atlaassian
Lean Startup
Continuous Deployment
Lean Agile Management
Code
SA
System Team
ARTs
Nexus and Kanban
Agile Mindset
predictability
What Is Kanban
Risk-aware Product Development
Portfolio for Jira
BDD
An Appreciative Retrospective
Managing Risk on Agile Projects
Releases Using Lean
SAFe DevOps
AgileSparks
ATDD vs. BDD
SPC
Agile Basics
Lean Agile Organization
SAFe Release Planning
Advanced Roadmaps
Scrum
Scrum Master
Professional Scrum with Kanban
Agile Release Management
Accelerate Value Delivery At Scale
Operational Value Stream
POPM
Continuous Improvement
WIP
Lean-Agile Budgeting
Agile Marketing
AI
agileisrael
Agile Games
LeSS
Scrum Guide
Kanban
Jira Plans
Agile for Embedded Systems
Risk Management in Kanban
Risk Management on Agile Projects
Agile Program
Agile Release Planning
Rapid RTC
Sprint Planning
Tips
Scrum Values
chatgpt
Managing Projects
Lean Budgeting
Agile Israel Events
Agile Games and Exercises
speed at scale
Planning
Agile Israel
Process Improvement
Lean Software Development
Entrepreneurial Operating System®
Spotify
Self-organization
Jira Cloud
Certified SAFe
Pomodoro Technique
Software Development
System Integration Environments
Presentation
Implementation of Lean and Agile
Limiting Work in Progress
NIT
ATDD
Certification
Sprint Iteration
Software Development Estimation
Lean-Agile Software Development
Agile Exercises
Agile Outsourcing
Agile Delivery
Hybrid Work
Principles of Lean-Agile Leadership
Tools
System Archetypes
Lean and Agile Techniques
EOS®
Engineering Practices
Agile Community
Kanban Game
Agile Techniques
Kanban 101
Agile Product Development
Development Value Streams
Change Management
Games and Exercises
Lean Agile Basics
Systems Thinking
Jira admin
LPM
Built-In Quality
ROI
Daily Scrum
Perfection Game
Test Driven Development
Story Slicing
Legacy Enterprise
The Agile Coach
AI Artificial Intelligence
Large Scale Scrum
AgileSparks
Logo
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