liveBook · Manning

Incremental development

As explained in Effective Behavior-Driven Development

A software delivery approach in which functionality is delivered in small, planned increments.

Incremental development delivers functionality in small, planned steps. User stories act as placeholders for conversations; analysis can break them into smaller stories that support fine-grained prioritization and regular delivery. section 10.1

Keep delivery planning distinct from lasting product documentation:

  • Use refined stories to plan and track small functional increments. section 10.1
  • Capture lasting requirements as rules and scenarios, organized around coherent functionality rather than the order features were delivered. section 10.1

How Effective Behavior-Driven Development covers it

How deep it goes
Explains how analysis produces smaller stories for fine-grained prioritization and regular delivery, but gives no end-to-end procedure.
Examples
Contrasts stories with lasting rules and scenarios, using blocklisting and restricted-customer behavior as a feature example.
What you can do after
Apply it by refining stories into smaller units for fine-grained planning and regular functionality delivery.
How it connects
Links user stories with requirements analysis, prioritization, and living documentation.

Also explained in

Compare how 2 books explain incremental development →

Related concepts

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