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.
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 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.
A practical comparison
| Element | Purpose or question | Useful evidence |
|---|---|---|
| Pre-Plan | Create sufficient cross-ART readiness | Shared priorities, capabilities, constraints, and dependencies |
| ART planning | Develop credible team and ART plans | Objectives, capacity, dependencies, and risks |
| Integration | Combine solution elements frequently | Working interfaces and objective evidence |
| Solution Demo | Evaluate the whole with stakeholders | Integrated 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.
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.
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.
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.
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.
Apply the concept to an operating decision
Pre-Plan aligns ARTs and suppliers before individual PI Planning events; the Solution Demo provides integrated feedback on solution-level progress. They solve different coordination problems but share a need for timely capabilities, interfaces, milestones and decision owners.
A practical review
Build a cross-ART readiness board with capabilities, supplier commitments, architecture decisions, environments and unresolved dependencies. After the Solution Demo, convert feedback into owned decisions rather than distributing meeting notes. Review dependency age, decision lead time, integrated test coverage and risks discovered after planning.
A practical sequence to apply this guidance
- What Pre-Plan and Solution Demo mean in practice: Clarify the decision, people affected and evidence needed before acting.
- The common implementation mistake: Apply the guidance to one current example and record important constraints.
- A practical comparison: Choose one small action with an owner, boundary and review date.
- Worked enterprise example: Compare the result with the intended outcome and update the approach.
Use the sequence as a decision aid, not a rigid template. Preserve the article's context and adapt the steps when evidence, risk or authority differs.
