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:

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