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:

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