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:

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