4.2 Discovery and Project Framing

Discovery and Project Framing is the early, exploratory stage of an agile project in which a team investigates the problem space, clarifies the intended value, and establishes enough shared understanding of direction to begin iterative work, without attempting to fully specify requirements or solutions in advance. It sits between initial authorization of a project and the start of regular delivery cycles, translating a broad vision into a workable starting point for planning while deliberately preserving flexibility for what is not yet known.

Purpose of Discovery

Reducing Uncertainty Before Committing Resources

Discovery activities aim to surface the most significant unknowns about a problem, its users, and possible solutions early, when the cost of exploring alternatives is low, rather than deferring this learning until substantial resources have already been committed to a particular direction.

Testing Assumptions

Teams use discovery to identify and examine the assumptions underlying a proposed project — about user needs, market conditions, technical feasibility, or business value — and to gather evidence that either supports or challenges those assumptions before large-scale investment begins.

Discovery Activities

Problem Exploration

Discovery begins with investigating the problem a project intends to solve, often through stakeholder interviews, user research, and analysis of existing data, aiming to understand root causes and the true scope of the need rather than accepting an initial framing at face value.

User and Market Research

Understanding who will use or benefit from a project's outcome, and what alternatives already exist to meet their needs, helps a team ground its framing in real evidence rather than internal assumptions, reducing the risk of building something that does not achieve genuine adoption or value.

Technical Exploration and Spikes

Where significant technical uncertainty exists, discovery may include short, time-boxed technical investigations, sometimes called spikes, intended to answer a specific question about feasibility or approach rather than to produce a finished deliverable.

Project Framing

Defining the Vision

Framing distills the outcome of discovery into a concise statement of the project's purpose and intended value, providing enough direction to align stakeholders and guide subsequent planning without prescribing every detail of the eventual solution.

Establishing Boundaries

Framing clarifies the boundaries of a project — what is explicitly in scope, what is explicitly out of scope, and what remains genuinely uncertain — helping the team and stakeholders share a realistic understanding of what will and will not be addressed.

Success Criteria

Framing typically identifies how success will be recognized, whether through specific metrics, qualitative outcomes, or stakeholder acceptance criteria, giving the team a reference point for prioritizing work throughout the project.

Outputs of Discovery and Framing

Problem and Opportunity Statements

A clearly articulated statement of the problem being addressed or the opportunity being pursued provides a shared reference point that the team can return to when evaluating whether specific work remains aligned with the project's original intent.

Initial Backlog and Hypotheses

Discovery often produces an initial, coarse-grained backlog of ideas, features, or hypotheses to be tested, understood as a starting point subject to significant revision rather than a fixed specification.

Lightweight Artifacts

Framing outputs in agile contexts tend to be lightweight — brief vision statements, sketches, or simple diagrams — favoring clarity and adaptability over comprehensive documentation that would need to be revised repeatedly as understanding evolves.

Relationship to Subsequent Work

Feeding Iterative Planning

The understanding produced during discovery and framing feeds directly into the first rounds of iteration planning, providing enough context for the team to prioritize early work meaningfully, even though many details will continue to be refined.

An Ongoing, Not Purely Upfront, Activity

While concentrated at the start of a project, discovery does not end once delivery begins; agile teams continue to investigate open questions and refine their framing throughout the project as new information emerges from each iteration.

Discovery and Project Framing establishes a well-grounded starting point for agile work, replacing detailed upfront specification with focused investigation of the problem and a clear but adaptable statement of purpose that guides the team through the uncertainty of early iterations.