Search
Close this search box.
Search
Close this search box.
Search
Close this search box.

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:

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