Search
Close this search box.
Search
Close this search box.
Search
Close this search box.

Working towards Sustainable Pace in Scrum, SAFe and Kanban

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp

Aiming towards Sustainable Pace

“Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.” – The Agile Manifesto Principle

“programmers or software developers should not work more than 40 hour weeks, and if there is overtime one week, that the next week should not include more overtime.” – Extreme Programming

An unsustainable pace is unhealthy. It contributes to burnout, quality issues, and unpredictable results.

If you are an agile leader – do you know whether your teams are currently operating at a sustainable pace? Do you care? Would you rather not know because you’re afraid of the answer?

Measuring Sustainable Pace

Beyond having a general idea of the sustainability of pace, perhaps it would help to have a concrete KPI related to it?

If we use the language of OKRs, maybe something along these lines:

Objective Achieve a healthy sustainable pace

KR1 – People working reasonable hours AMB (as measured by) hours per week

KR2 – People happy about their pace AMB continuous survey 

KR3 – Plans don’t assume unsustainable pace AMB ability to achieve forecasts without resorting to unsustainable pace measures

Forecasting towards Sustainable Pace by inspecting sustainability of past pace

The last KR relates to the planning/forecasting approaches we use in agile. Agile approaches leverage empirical planning approaches. They look at the past (Yesterday’s weather) to try and forecast the future. Whether it is PI Planning, Sprint/Iteration planning. Whether by looking at Velocity, Throughput, or Cycle/Flow Times – most approaches tend to ignore how these past results were achieved when using them to predict future capacity.

For example, if our velocity in previous Sprints was 15-20 points, we will probably take on about 15-20 points. But what if these 15-20 points required a herculean effort that wasn’t sustainable?

Similarly – if we just concluded a PI in which the ART achieved a Program Predictability Score of 85% we will be tempted to assume we have a pretty serviceable approach to planning/forecasting. But what if this required killing it through nights and weekends and skipping any sort of Innovation in the IP iteration? Where does this come into the calculation?

If our cycle/flow times are 7-10 days 85% of the time we will be tempted to set that as an SLE (Service Level Expectation) to ourselves. But does that make sense if this was achieved while working 60 hour weeks?

Planning/Forecasting using a Sustainability Factor

What I’m advising teams/organizations I’m working with is to consider the “sustainability factor” when considering any past results for the purpose of forecasting the future and adjusting accordingly. This isn’t trivial. It requires making sustainable pace an explicit “citizen” of the measurement dashboard and conversation.

We have learned that speed and quality are related. We now understand that inappropriate speed might be at the expense of quality, so we look at a balanced scorecard of speed and quality. Moving forward, we need to add pace sustainability to this scorecard and to the conversation around how much work does it make sense to forecast.

A metric I’ve been toying with is Weighted Predictability/Sustainability:

Predictability(Un)SustainabilityWeighted
80%150%53%
80%100%80%
60%100%60%
100%150%67%

As you can see here, achieving reasonable predictability scores is weighted down by the unsustainable pace required to achieve them. so a score of 80% is actually weighted down to 53%. This 53% is what should be used for future planning purposes. For example in SAFe I&A and PIP.

Moving Forward – Treating Pace Sustainability as a first-class citizen

First, we need to come up with a good name for this metric / KPI. Flow Sustainability? Pace Sustainability? Work Sustainability? Burnout Risk?
Are you explicitly measuring anything related to Sustainable Pace? Do you have goals around it? Do you take it into consideration when planning? Please share in the comments!

Subscribe for Email Updates:

Categories:

Tags:

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