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:

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