liveBook · Manning

Business context

As explained in Spec-Driven Development

The set of purpose, scope, user, problem, and success information that explains why a feature or change is needed.

Business context records why a feature or change is needed: its purpose, scope, and acceptance criteria. It turns a high-level idea into durable guidance before technical design or execution begins. section 2.2.1

Interrogate the idea with questions such as:

Keep this conversation at the level of what to build. Technical choices belong in design; execution details come later. section 2.2.1

Figure 2.2 The first interaction between human and agent is a discovery discussion, focused on business concerns to draft purpose, scope, etc. This then forms the basis of second interaction which focuses on design to decide technology stack, and architecture. Both of these together guide the drafting of the task list. The agent then uses the task list, to autonomously execute and generate the implementation.

Shows how discovery establishes business intent before design and task planning guide implementation. section 2.2.1

How Spec-Driven Development covers it

How deep it goes
Defines the discovery questions and resulting specification, stopping short of technical design and execution details.
Examples
Uses questions about the intended user, problem, timing, and definition of success.
What it assumes
Starts from a high-level idea or intuition and deliberately defers technical and execution decisions.
What you can do after
Apply it by eliciting purpose, scope, and acceptance criteria from a high-level idea before design begins.
How it connects
Connects specification-driven development with acceptance criteria, technical design, and task planning.

Also explained in

Compare how 4 books explain business context →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Spec-Driven Development. The section links point to the parts of the book it draws on.