Continuous exploration
Continuous exploration is SAFe's umbrella term for ongoing discovery work — hypothesis generation, customer research, prototyping, experiments — that feeds the backlog of features and enablers. It's the upstream of the SAFe delivery flow: continuous exploration → continuous integration → continuous deployment → release on demand.
SAFe's continuous exploration framing addresses a recurring criticism that scaled-Agile frameworks over-emphasise delivery (the back half) at the expense of discovery (the front half). The practice cluster includes customer research, market analysis, hypothesis generation, design spikes, and lean MVPs. The teams responsible vary by ART: sometimes Product Management owns it solo; sometimes a dedicated UX Research team contributes; sometimes the engineering teams participate via spikes. The point is that exploration is treated as an ongoing investment, not a one-time pre-project activity.
Related terms
- Dual-track agile
Dual-track agile (sometimes called dual-track discovery and delivery) is a product-development model, codified by Marty Cagan and Jeff Patton, that runs two parallel workstreams: a discovery track that validates which problems are worth solving and what solutions will work, and a delivery track that builds the validated solutions.
- Discovery vs delivery
Discovery vs delivery is the foundational distinction in modern product development: discovery activities (research, prototyping, hypothesis testing) determine WHAT to build and why; delivery activities (engineering, QA, deployment) execute on the decision.
- Spike
A spike is a timeboxed research story — the team commits to spending a fixed amount of effort (1 day, 3 days, a sprint) exploring a question, with a defined deliverable (a recommendation, a prototype, a decision).