Project Management

How Disciplined Agile and FLEX Improve SAFe

From the Manifesting Business Agility Blog
by
This blog concerns itself with organizations moving to business agility—the quick realization of value predictably and sustainably, and with high quality. It includes all aspects of this—from the business stakeholders through ops and support. Topics will be far-reaching but will mostly discuss FLEX, Flow, Lean-Thinking, Lean-Management, Theory of Constraints, Systems Thinking, Test-First and Agile.

About this Blog

RSS

Recent Posts

What is a Lean-Agile Coach?

My Approach to Sensemaking in Knowledge Work

Why if you are a PMP who understands the value of Agile your next workshop should be the Disciplined Agile Value Stream Consultant

My views (past posts) on cause and effect in complex systems

Transcend the thinking that scope, time and cost are in opposition to each other with Lean-Thinking

Categories

lean, value streams

Date

linkedin twitter facebook Request to reuse this  


I'm working on a 2-day subset of the DA Value Stream Consultant workshop called Disciplined Agile for SAFe. Here's a list of main changes & additions:

  • The goal is not coordination of teams but decoupling of teams
  • Focus on creating a network of semi-autonomous, cross-functional team or groups of teams (dedicated product team - DPT)
  • Use flow/kanban to manage work between teams
  • Use dedicated product teams instead of ARTs
  • View SAFe from a value stream (Lean's definition) perspective
  • How to improve value streams
  • Use MBIs and MVPs (Ries’ meaning) as MVPs can't be done in a 3 month cycle
  • Use FLEX's simpler budgeting, portfolio & product management method aligned around products (true project to product shift)
  • Middle-up-down management
  • calculate cost of delay on MBIs, not epics or features
  • take a systems-thinking perspective
  • one size does not fit all - look where to start
  • attend to culture
  • Use Big Room Planning to identify dependencies and to guide DPT creation - BRP deals with symptoms not root cause so don’t have it be your central method of planning
  • Agreements to make across the organization
  • Why you must start your improvements with test-first methods
  • Use Goldratt's inherent simplicity to deal with complexity

Posted on: April 10, 2020 05:53 PM | Permalink

Comments (3)

Please login or join to subscribe to this item
avatar
Eduin Fernando Valdes Alvarado Project Manager| F y F Fabricamos Futuro Villavicencio, Meta, Colombia
Thanks for sharing

avatar
Alexandre Costa Scrum Master| Integer Consulting - Pictet technologies Loures, Portugal
Hi AI,

It's curious, how this is applied, having DA it's own lifecycles , more specifically the program lifecycle when you have the case of multiple teams, in the process goal evolve your wow , in the decision more lifecycle we can choose lifecycles that are not DAD lifecycles like SAFe Less ( or you are already limited to what is implemented) etc...

I suppose that in this particular cases we are limited only to improve all that is not pescrived by SAFe or Less etc...

Alexandre

avatar
Al Shalloway Founder and CEO| Success Engineering Edmonds, Wa, United States
Great question. I'm in the process of writing this up.

Basically, you could say DA is creating a new lifecycle to use based on FLEX - one of improving SAFe.

One of the key aspects is to go beyond the large planning events and decompose the ARTs into dedicated product teams with fewer dependencies between them.

I've opened up a study program on DA/FLEX with 2 Q&A sessions on it. You can learn more at:

https://portal.netobjectives.com/pages/books/the-disciplined-agile-value-stream-consultant/da-vsc-qa-program/

Please Login/Register to leave a comment.

ADVERTISEMENTS

"If you would be a real seeker after truth, it is necessary that at least once in your life you doubt, as far as possible, all things."

- Rene Descartes

ADVERTISEMENT

Sponsors