Scaled Agile

Pre-Plan, Solution Demo, and Cross-ART Readiness in SAFe

Understand Pre-Plan activities and Solution Demos that align ARTs, expose dependencies, and create integrated evidence across a Solution Train.

Pre-Plan, Solution Demo, and Cross-ART Readiness in SAFe

Pre-Plan is easy to memorise as a definition and harder to use in a real enterprise. This guide is designed to show how a Solution Train prepares ARTs for planning and evaluates integrated progress without turning coordination into a phase gate.

The subject matters because SAFe connects strategy, people, product decisions, technical work, and governance. A local interpretation can appear reasonable while creating delay somewhere else in the value stream.

What Pre-Plan and Solution Demo mean in practice

Pre-Plan covers activities that prepare and align ARTs within a Solution Train before PI Planning. It develops shared context around vision, priorities, capabilities, architecture, dependencies, and planning inputs. The Solution Demo provides stakeholders with an integrated view of contributions from multiple ARTs and suppliers and gathers objective feedback.

The useful question is not whether an organisation can repeat the glossary language. It is whether people make a different and better decision when the concept is applied. Context, authority, evidence, and feedback determine whether the practice produces value.

The common implementation mistake

Pre-Plan becomes big up-front planning when leaders attempt to remove all uncertainty before teams engage. A Solution Demo becomes theatre when each ART shows separate slides rather than an integrated solution.

This is why copying a role, event, template, or metric is insufficient. Teams and leaders should preserve the purpose of the practice, make policies explicit, and examine its effect on the wider system.

A practical comparison

ElementPurpose or questionUseful evidence
Pre-PlanCreate sufficient cross-ART readinessShared priorities, capabilities, constraints, and dependencies
ART planningDevelop credible team and ART plansObjectives, capacity, dependencies, and risks
IntegrationCombine solution elements frequentlyWorking interfaces and objective evidence
Solution DemoEvaluate the whole with stakeholdersIntegrated performance and feedback

Worked enterprise example

Four ARTs build one logistics solution. Pre-Plan identifies a shared identity dependency, and early Solution Demos reveal workflow gaps while the design can still change.

The example should be discussed with the people who perform and receive the work. A decision made only from a framework diagram can miss constraints, customer needs, regulatory obligations, or technical realities known elsewhere in the system.

How to apply the concept without creating ceremony

  • Prepare decisions and context without fixing every detail.
  • Invite suppliers and architects where dependencies require them.
  • Demonstrate an integrated solution.
  • Feed evidence back into backlogs and plans.

Start with one value stream, ART, portfolio decision, or customer journey where the problem is visible. Record the current condition and choose a review date. A bounded experiment makes learning possible without presenting an untested change as enterprise policy.

How the glossary terms connect

Pre-Plan, Solution Demo, Solution Train, Integration Point, Solution Vision belong in the same conversation because an enterprise rarely experiences them separately. One term may describe a role or structure, another the decision being made, and another the evidence needed to inspect the result. Reading each definition independently can hide that relationship.

Draw the connection on one page: show where demand enters, who makes the relevant decision, what moves through the system, and where feedback returns. Then mark every handoff or approval that can delay learning. This simple view helps participants challenge different interpretations before those interpretations become competing processes or tool configurations.

Measures and evidence to review

  • Customer or stakeholder outcome affected by the change.
  • Elapsed time, waiting, work in process, or decision delay.
  • Quality, risk, compliance, or reliability evidence relevant to the context.
  • A behaviour or policy that changed, not merely attendance at an event.
  • An unintended effect on another team, value stream, or customer group.

No single metric proves that the practice worked. Review quantitative signals with the people involved and capture what changed in the operating context. Trends and decision quality are usually more informative than a target number viewed alone.

Questions leaders and practitioners should ask

  • What problem are we trying to solve with Pre-Plan?
  • Which decision or behaviour should change?
  • Who has the authority and knowledge required?
  • What assumption is least certain?
  • How will we know whether value flow improved?
  • When will we inspect and adjust the approach?

Connection to SAFe learning

RTE certification training provides a broader learning context for these decisions. Certification can establish shared language, but capability develops when learners apply the ideas to real work, inspect evidence, and receive support from leaders and peers.

Use the glossary term as a doorway into the system, not as the finish line. The aim is a clearer decision, faster learning, and a more reliable flow of value.