One of the biggest anti-patterns I have consistently seen with SAFe enterprises is the misuse of the Large Solution level. Organizations (and yes Coaches) tend to misinterpret this extra level as required for inter-ART collaboration. They launch ARTs, realize that inter-ART dependencies exist, and immediately slap on the Large Solution as another level of overhead.
Stop the madness!
What Does SAFe Say?
Here are some quotes from SAFe guidance about appropriate use of the Large Solution level:
- “… the world’s largest and most sophisticated software applications, networks, and cyber-physical systems”
- “… meant for enterprises facing the biggest challenges”
- “… building large-scale solutions that are beyond the scope of a single ART”
- “… deliver the world’s largest and most complex systems”
I once heard Dean Leffingwell describe it as “the level needed for building the Mission to Mars spaceship”.
I’m sorry, but your need for some level of inter-ART collaboration is very unlikely to fit the scenarios described above!
Example: Supersonic Tactical Jet Fighter
Below is an example of where the Large Solution is truly needed. Imagine if our company is building the world’s most advanced tactical jet fighter complete with all modern technological advances such as supersonic speed, electronic threat detection, over the horizon radar, and artificial intelligence.
Notice how each ART focuses on building a single but extremely complicated subsystem – avionics, communications, radar systems, threat detection, or weapons systems. Additional ARTs might focus on artificial intelligence, fuel systems, and predictive analysis.
The subsystem produced by the ART is of little value in and of itself. The ART has no end-user customer other than the multi-ART integration environment. Each subsystem produced by an ART requires a highly technical integration effort into an airplane frame to finally achieve value – a new advanced supersonic fighter jet.
Don’t Do It!
If you are using the SAFe Large Solution level for inter-ART collaboration, you have imposed another layer of overhead onto your product development system.
Large Solution has the following 7 additional events: RTE Sync, PM Sync, Architect Sync, Solution Train PI Planning, Solution I&A, Pre-Planning Workshop, and Solution Demo.
Large Solution has the following 9 additional artifacts: Capabilities, Enabler Capabilities, Solution Epics (just in case Program Epics are not confusing enough!), Solution Roadmap, Solution Train PI Roadmap, Solution Train Backlog, Solution Kanban, Solution Intent, and Solution Vision.
Large Solution has the following 6 additional roles: Solution Architect, Solution Management, Solution Train Engineer, Solution Supplier, Solution Business Owner (different scope than Business Owner role), and Solution Customer (different scope than Customer role).
That’s right – 7 additional events, 9 additional artifacts, and 6 additional roles. Totally plausible when building the world’s most advanced fight jet or the Mission to Mars spaceship.
If you have implemented a Large Solution level for your inter-ART collaboration needs, you have just imposed an enormous amount of overhead on your organization. Don’t do it!
A Healthy Lean Alternative
Chances are your ART will have some dependencies on other ARTs and shared services. Look at that as a signal to adjust the ART team makeup for better alignment to value. If that is not plausible at this time, then explore ways to ensure the appropriate level of inter-ART collaboration is occurring. Some options might be:
- An additional brief recurring meeting
- Dependency visibility within your Agile tooling
- Multi-ART roadmap planning
- Dare I say it? – Face-to-Face communication
The Bottom Line
Ask yourself “Do our ARTs deliver value to our end users?” If the answer is yes, then SAFe’s Large Solution is NOT for you. Ask yourself “Do our ARTs deliver sub-systems to a complex multi-ART integration environment where the final product is packaged?” If so, then SAFe’s Large Solution might be appropriate.
Wrap
Avoid using the SAFe Large Solution level for simple inter-ART collaboration or dependency management. Figure out a good way to ensure healthy inter-ART collaboration without imposing another level of significant overhead. The Large Solution level is designed for building the Mars spacecraft. Chances are your needs are less than that!
For more on SAFe, visit here. For more on what all is typically involved in an Agile transformation, visit here.