The document discusses employing role-based behavioral scenarios and complete user scenarios to map end-to-end behaviors for developing complex systems. It contrasts a goals approach limited by technology views with a customer-centric goals approach considering market and customer views. It also contrasts a traditional build-first approach with speeding time to market through formal testing during development and timely fixes.

1. 21 July 2016 Page 1 of 4 Rod Spencer - www.linkedin.com/in/rodspencer
Customer relatable requirements
Employing role based behavioral scenarios
From… To…
Given-When-Then
One condition to one
outcome is insufficient for
complex systems.
Complete user
Scenario– Maps to
complete end-to-end behaviors.
Demonstrable end-to-end.
Goals limited by
technology view
Work mis-focused on
“How” not the “Why.”
Excludes BAs, CEs, market
views.
Goals considers
Market – Customer centric
focused on “Why” not the
“How.” Relatable to BAs, CEs.
Supports market research.
Slower time to
market
from traditional build first
and deferred SQA at end
Speeds time to
Market – Formal tests
during development. Timely
fixes from fail fast strategy.
Work is done when required
behavior achieved.
Achieved by…

2. 21 July 2016 Page 2 of 4 Rod Spencer - www.linkedin.com/in/rodspencer
• Simple, practical,
understandable by common knowledge,
implementable by common Agile tools.
• Structures Behavior &
Design relationships for work
products
• Extensible for tracking
dependencies to & from other
projects, hardware and contracted
efforts.
The “Quad”
The archetype for structuring customer relatable work efforts
Structured by self organizing sprint teams using…

3. 21 July 2016 Page 3 of 4 Rod Spencer - www.linkedin.com/in/rodspencer
• Just-in-time PERT –style
diagrams, allowing sequential
organization as work proceeds.
Automatically generated as plans
evolve. Team simply defines before
& after stories in JIRA.
• Explicitly identifies direct
and derived
dependencies, speeding
planning, optimizing reuse,
establishing priorities.
• Ties to reporting
metrics, reporting on
completion toward business goals.
Dependency charts
Generated automatically from JIRA
Providing the basis for…

4. 21 July 2016 Page 4 of 4 Rod Spencer - www.linkedin.com/in/rodspencer
• Progressive estimation
starting with cursory top-level
Epics, evolving toward more
realistic estimates based on in-
project experience.
• Realistic schedule
outlooks while portraying
uncertainty.
• Outlooks rolls up into
customer expectations
aggregating technical work into
formally tested behavior.
Reporting Metrics
Generated automatically from dependencies.