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:

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