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:

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