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:

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