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:

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