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