liveBook · Manning

Why stack

As explained in BDD in Action, Second Edition

A why stack is an iterative questioning technique that traces a requested feature through successive reasons until it reaches an underlying business goal or value.

A why stack traces a requested feature through successive reasons until the team identifies an underlying, measurable business goal. It clarifies value, supports prioritization, and helps teams adapt features as circumstances change. section 4.2.8

Frequent Flyer cards

A team asks why its system must integrate with a banking partner. The answers progress from issuing cards, to selling Frequent Flyer points, to generating revenue from banks that provide member benefits to their customers. The resulting goal gives the team a basis for evaluating the feature’s value. section 4.2.8

How BDD in Action, Second Edition covers it

How deep it goes
Explains the questioning process through a worked scenario, but stops short of prescribing a formal question count or checklist.
Examples
Uses banking integration, Frequent Flyer cards, point sales, and partner revenue as the worked example.
What it assumes
Assumes a feature request and collaborative business discussion, while demonstrating the analysis from the initial request onward.
What you can do after
Apply it to uncover measurable value behind feature requests and support prioritization or adaptation.
How it connects
Connects business goals with feature requests, BDD, Impact Mapping, Pirate Canvases, and Feature Mapping.
Cover of BDD in Action, Second Edition
liveBookmanning.com
Read BDD in Action, Second Edition on liveBook Get the book at manning.com

Related concepts

This explainer was generated by Manning's knowledge graph from the text of BDD in Action, Second Edition. The section links point to the parts of the book it draws on.