SAFe Program Dependency Board Retrospective

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp
Program Board Discussion

Learning from the SAFe Program Dependency Board

The SAFe Program Board or Program Dependency Board is a key artifact used in PI Planning and Execution. The ART Teams and Stakeholders used it to align, anticipate risks, and adapt the plan accordingly.

This “inspection and adaptation” of the plan based on insights from the Program Dependency Board is “first loop learning” – making changes in the plan based on what we see.

Deeper Learning from the Program Dependency Board

What we rarely see, though, is deeper learning from what the Program Dependency Board shows us. It’s like the good old times when you would see a project manager / PMO working their MSProject Gantt Chart, moving things around, but rarely stopping to ask deeper questions about the base structure of their plans and why they’re based on a waterfall model.

Program Dependency Boards can drive deeper learning about the structure of our ART and its alignment with the kind of mission/vision we’re pursuing and the backlog of Features we’re working on. If we see too much red yarn on our boards it isn’t something to be proud of. Yes we can be proud that we identified the dependency and even more that we were able to massage our PI plan to deal with it in a reasonable way. But too much red yarn means too many dependencies. Too many dependencies mean our Value Stream Network isn’t configured well. It means we should probably look at ways to reconfigure the network (meaning restructure teams and maybe even the ART).

When to do this deeper learning

I get it. This sort of learning is hard to pursue in the heat of PI Planning. And all too often when PI Planning is done and we have a workable plan in hand its tempting to just move into execution. Resist the temptation. Let the dust settle, but find the time that makes sense to have a deeper retrospective that is based on the patterns you see on the Program Board. This can be a good discussion in your Scrum of Scrums or with an extended forum that includes the wider ART leadership.

There’s no need to wait for the next Inspect and Adapt. It’s fresh now and outcomes from this retrospective might anyhow require a lot of refinement and consideration before they’re actionable. Start the process early in the PI so hopefully, you’ll be in a position to reconfigure the network going into the next PI as needed.

A typical pattern is when such a retrospective raises the need to rerun a Value Stream Identification workshop.

Validating the Value Stream Design Hypothesis – A Key but often Skipped step

Speaking of the VSI workshop – one key element in it that many practitioners skip is the validation of your value stream design hypothesis. After identifying a Development Value Stream, run some water through the pipes – take some work in the form of Features or even higher-level Epics/Themes and explore how they will flow through this value stream/ART/Solution ART. If the work flows nicely with a minimal number of dependencies you found a good setup. If even in this “dry run” you already see you have too many dependencies – time to rework the design!

PI Planning Dry Run

And yes – what this means is that ideally, even in this early phase, before even launching the ART, you should consider doing a light version of PI Planning as a dry run with the value stream design you have in mind – to see that it makes sense. You don’t want to train everybody, spend a serious amount of time on preparing to launch the ART, and then find its not a self-sufficient ART or that it’s comprised of teams that aren’t self-sufficient.

Summary

I’ve talked about some recommended practices here, some are implicitly mentioned in SAFe, some complement the formal guidance. The key point I wanted to make is how important is it to aim for the right value stream network and to continuously inspect and adapt so that value can easily flow with minimal dependencies and slowdowns. And if your value stream network is configured well, everything else becomes much easier.

 

Subscribe for Email Updates:

Categories:

Tags:

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