Handling scope change during a SAFe Program Increment (PI)

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp

How do we handle Scope Changes in a SAFe Program Increment?

A question about handling scope changes in SAFe was posed recently on a forum I’m participating in (The SAFe Community Forum). This is a question posed regularly in training and on ARTs I’m coaching so I thought I’d provide my thoughts here.

How do you handle a scope change in a program increment? Specifically when it comes to switching one feature for another. And what’s the impact on PI Objectives and Predictability Score?

A lot of people somehow get the notion that SAFe advocates for “limiting/controlling changes during the PI”. The main source of this notion is that we “Plan the Program Increment” and commit to a set of PI Objectives as part of PI Planning.

But remember one of the key SAFe principles is “Assume Variability- Preserve Options”. This applies within a PI as well. While it makes sense to create a baseline plan for the Program Increment, we should also be prepared for adjustments. After all, we want to “Welcome changing requirements, even late in development.”, remembering that Agile processes harness change for the customer’s competitive advantage.” 

Some people are worried about the Predictability Score – “We would lose points since we won’t tackle some of our planning PI objectives and won’t get credit for them”. Yes some PI objectives won’t be achieved but new objectives should be added or objectives can be changed to align with the changed scope. (Think for example we didn’t manage to hit the “Deploy MS Teams” but we added “Enable all clinicians to provide telehealth meetings using Zoom” as a change made in a PI during the first couple of months of the covid19 pandemic)

Another important question is how do we run a PI in which it is relatively easy to switch some features midway?

We do it by following strong priorities and small batches going into the PI and limiting the number and size of features in progress in early iterations so lower priority Features / PI Objectives are kept as options rather than already started.

The goal is to avoid situations where we want to change direction but there’s already sunk cost since we already started the low priority Feature. We don’t take the sunk cost into consideration when prioritizing, but it will mean that continuing down the planned path will win the WSJF more often. Might be easier for the ART but isn’t necessarily maximizing the value delivered.

Even more important than the mechanics of the answer is the mindset. If a question like this comes up – go back to the principles. Lean, Agile, and SAFe principles will help you think about the situation and what might be the right systemic way to address it.

So let’s say Product Management is considering a change. They have a Feature that wasn’t in the original Program Backlog or was and there’s something that changed about it. Product Management should use WSJF to consider what to do. The Cost of Delay and Job Size of these suggested changes should be compared to the Cost of Delay and (remaining) Job Size of the existing PI Scope.

And if at this point the WSJF score for the considered change is higher than continuing down the current path then it makes sense to go for the change.

Some people are worried about the Predictability Score – “We would lose points since we won’t tackle some of our planning PI objectives and won’t get credit for them”. Yes some PI objectives won’t be achieved but new objectives should be added or objectives can be changed to align with the changed scope. (Think for example we didn’t manage to hit the “Deploy MS Teams” but we added “Enable all clinicians to provide telehealth meetings using Zoom” as a change made in a PI during the first couple of months of the covid19 pandemic)

Another important question is how do we run a PI in which it is relatively easy to switch some features midway?

We do it by following strong priorities and small batches going into the PI and limiting the number and size of features in progress in early iterations so lower priority Features / PI Objectives are kept as options rather than already started.

The goal is to avoid situations where we want to change direction but there’s already sunk cost since we already started the low priority Feature. We don’t take the sunk cost into consideration when prioritizing, but it will mean that continuing down the planned path will win the WSJF more often. Might be easier for the ART but isn’t necessarily maximizing the value delivered.

Even more important than the mechanics of the answer is the mindset. If a question like this comes up – go back to the principles. Lean, Agile, and SAFe principles will help you think about the situation and what might be the right systemic way to address it.

Subscribe for Email Updates:

Categories:

Tags:

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