Now for video six in our series designed to jump-start your understanding of the core practices and principles of Agile software engineering (ASE). Here, one of our Lean-Agile thought leaders, Ken Pugh, talks about discovering story details with scenarios.

A scenario defines a system behavior from an external point of view. A story, a short description of a small piece of desired functionality, can have many scenarios. Watch as Ken breaks a story down into workflow steps and then details the scenarios for it, making it testable. He uses a story map to pull together the story, the workflow, and multiple scenarios.

To test a workflow both end to end and in individual steps, it’s key to break complex scenarios down into simpler ones. The end result? Improved testability!

Go here to learn more about scenarios.

Check back soon for the seventh video in our series: how Behavior-Driven Development creates shared understanding. 

And go here to watch Ken’s previous video about the magic of shift-left testing.

You can learn more about the Agile Software Engineering course here.   

Stay SAFe,

—Harry