Specification By Example

Specification By Example

Specification by example is a collaborative approach to defining requirements and tests for based on capturing realistic examples instead of abstract statements. It is the cornerstone of any successful requirements and testing and requirements strategy with agile and lean processes, such as Scrum, Extreme Programming and Kanban. This workshop teaches you how to apply specification by example to bridge the communication gap between stakeholders and implementation teams, build quality into software from the start, design, develop and deliver systems fit for purpose.

Since 2007, more than 9000 people have benefited from this workshop.

The workshop is aimed at delivery team members (programmers, testers, business analysts and product owners) mostly working in iterative delivery, such as Scrum or Kanban.  Prior experience in delivering software iteratively is useful when attending this workshop, but not required.

This workshop is based on Gojko Adzic’s books Specification by Example and Bridging the Communication Gap. Through facilitated exercises and discussion, you will learn:

  • how to extend specifications with examples to create a single source of truth for testing and development
  • how to avoid functional gaps and inconsistencies in specifications and tests
  • how to run specification workshops to facilitate collaboration
  • good practices for designing specifications with examples and acceptance tests for agile teams
  • how to create a living documentation system to facilitate change and improve your process long-term
  • how other teams, from small web startups to large distributed teams in investment banks, apply specification by example in their contexts

Schedule

Day 1:

  • Facilitating specification workshops
  • Getting the right examples, quickly
  • Avoiding the most common mistakes in product backlog refinement
  • Why/when to do specification by example, and when not to do it
  • What teams that do this really well do differently from those that just waste time

Day 2:

  • What are the most popular tools/how they differ
  • What makes a good specification/test for this context
  • How to clean up legacy specifications/tests
  • How this fits into Scrum/Kanban/…
  • How to start changing the process in your company

Duration:

2 days.

Language:

English

Important:

Participants are awarded 16 Scrum Education Units (SEUs) towards Certified Scrum Professional (CSP) certification.

To apply for the training you need to accept Training Terms and Conditions.

"

[Translate to English:]

“I had the fortunate experience of attending Gojko Adzic’s workshop at Booster 2014 on improving user stories. I must say, that for me it was more like ‘radically rethinking the way you’re doing user stories’”  

Ørjan Taule

"

[Translate to English:]

“Clearly loads of insight and value + well worth doing”

Rory MacDonald

"

[Translate to English:]

“Thought provoking! Inspired to try and implement the ideas in my team”

Gavin Bussey

"

[Translate to English:]

“Amazing, totally reshapes my mind about user stories"

Ben Hughes, Equinox IT