Posts on Specification by Example

Using “Given-When-Then” to Discover and Validate Requirements

By Mary Gorman and Ellen Gottesdiener

In our book Discover to Deliver: Agile Product Planning and Analysis we discuss the usefulness of the “Given-When-Then” technique to explore (discover) and confirm (validate) product options. Here we summarize the technique*, brainchild of Dan North.

What it Is 

Given-When-Then (GWT) is a structured format for expressing scenarios with example data, including pre- and post-conditions.

Usefulness

GWT helps project stakeholders (business, customer and technology partners) communicate using business domain language. You can use GWT to explore product options and confirm selected options and confirm selected options, in a concrete, tangible way. Often called “specification by example,” GWT provides living documentation for your delivered product. It simultaneously specifies requirements while identifying acceptance tests, thereby streamlining discovery and delivery.

Continue reading

A Visual Language for Product Teams

In October, we wrote about big concepts for delivering an ever-evolving, high-value product. These Agile/Lean concepts are used in your daily work to rapidly discover product needs and deliver valued products:

* The Product, and the 7 Product Dimensions
* The Structured Conversation metaphor (explore-evaluate-confirm)
* Value
* Product Partners
* Planning Views

Continue reading

Experiencing Agile: 6 Agile Planning and Analysis Practices to Try

What practices can you adopt to help your team experience Agile?

This question was raised by a listener to the podcast we recorded on agile analysis practices with BA coach Yamo. (Find the podcast here.) The specific question that Katie Metcalf asked us was this:

“What Agile techniques would you suggest introducing to a software development team that is currently not using the Agile approach but would like to get a flavor for the methodology?”

Continue reading

Agile Analysis, Agile Testing: Synergies for Successful Software Solutions

My experiences working with agile teams have taught me that agile analysis and testing skills are truly synergestic.

So much so, that I put together a tutorial for the April 2011 Quest Conference (Quality Engineering Software & Testing) entitled, “Requirements Exploration with Tester Collaboration”. Subsequently, I had the honor to work with agile testing guru Janet Gregory to present this at Agile 2011.

Next month, EBG’er Sue Burk will co-present this tutorial with Janet at Software Testing Analysis & Review (STAR) conferences. So, you might be wondering, what are those synergies?

The Testing Mindset

Product needs evolve into requirements that define what will be built, what will be tested, and how the product needs will provide value for the organization. People with testing skills need to be involved in requirements for the same reason the other product stakeholders need to be involved: to boost the team’s ability to deliver a high-quality product.

Continue reading

EBG Product Agility Newsletter

Get tips, stories and news on product discovery & delivery

Join our community and receive periodic tips, stories, and news on agile product management, product ownership, backlog and value management, collaboration, teamwork, and more.

Sign up Here