Xqfzz8l4hskygglhqc6g
2 DAY COURSE

Gojko Adzic's Specification by Example: From User Stories to Acceptance Tests

Topics covered at SPEC-EXAMPLE-01-02
View Schedule & Book More dates available

Next up:

Are you interested in creating more structured requirements and tests? Do you want to improve your communication between stakeholders and product owners and avoid common mistakes? Join Gojko Adzic for this exciting two day workshop!

We're trying out a new design for this course page! Check out the trial below and give us your feedback on our Contact Us tab in the lower right hand corner.

Specification by example is a collaborative approach to defining requirements and tests for systems, based on capturing realistic examples instead of abstract statements. It is the cornerstone of any successful requirements and testing strategy with agile and lean processes, such as Scrum, Extreme Programming and Kanban.

In this workshop you'll learn how to apply specification by example to bridge the communication gap between stakeholders and implementation teams. You'll learn how to build quality into software from the start and to design, develop and deliver systems fit for purpose.

Learn how to:

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

About the Author

Gojko Adzic

Gojko is a partner at Neuri Consulting LLP. He is the winner of the 2016 European Software Testing Outstanding Achievement Award, and the 2011 Most Influential Agile Testing Professional Award. Gojko's book Specification by Example won the Jolt Award for the Best Book of 2012, and his blog won the UK Agile Award for the best outline publication in 2010. Gojko is a frequent speaker at software development conferences, including NDC, Agile Days, Oredev, and YOW!, and is one of the authors of MindMup and Claudia.js.

Thanks to our partners

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

Audience

Are you a delivery team member? This course is aimed at 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.

Prerequisites

Overview

Are you interested in creating more structured requirements and tests? Do you want to improve your communication between stakeholders and product owners and avoid common mistakes? Join Gojko Adzic for this exciting two day workshop!

We're trying out a new design for this course page! Check out the trial below and give us your feedback on our Contact Us tab in the lower right hand corner.

Specification by example is a collaborative approach to defining requirements and tests for systems, based on capturing realistic examples instead of abstract statements. It is the cornerstone of any successful requirements and testing strategy with agile and lean processes, such as Scrum, Extreme Programming and Kanban.

In this workshop you'll learn how to apply specification by example to bridge the communication gap between stakeholders and implementation teams. You'll learn how to build quality into software from the start and to design, develop and deliver systems fit for purpose.

Learn how to:

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

About the Author

Gojko Adzic

Gojko is a partner at Neuri Consulting LLP. He is the winner of the 2016 European Software Testing Outstanding Achievement Award, and the 2011 Most Influential Agile Testing Professional Award. Gojko's book Specification by Example won the Jolt Award for the Best Book of 2012, and his blog won the UK Agile Award for the best outline publication in 2010. Gojko is a frequent speaker at software development conferences, including NDC, Agile Days, Oredev, and YOW!, and is one of the authors of MindMup and Claudia.js.

Thanks to our partners

Program

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
Audience

Audience

Are you a delivery team member? This course is aimed at 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.

Prerequisites