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:

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