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