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:

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