Architecturally Significant Story

[ahr-ki-tek-cher-uh l ly sig-nif-i-kuh nt stawr-ee, stohr-ee]

Definition of Architecturally Significant Story

A Functional Story that causes the Team to make one or more architectural decisions, which is then validated by the fact that there is existing, working functionality using the decisions.

See:

Functional Story, A Story that produces working code that has actual, demonstrable user value. A Functional Story’s Acceptance Criteria usually consists of a single Acceptance Test, and verifying that the Test passes...
Architecture  The collection of decisions about how a system will be built – from Grady Booch in the early 80’s.

Examples

[Discussing types of stories] ‘Get a list of available Flights from CUTLASS,’ – an Architecturally Significant Story because it causes the Team to decide how to interface with CUTLASS (assuming this is the first Story that does so).

External Sources

5 Prioritization Factors

Cite This Term

"Architecturally Significant Story" ScrumDictionary.com. Accessed Oct 05, 2024. https://scrumdictionary.com/term/architecturally-significant-story/.