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:

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