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:

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