Specification by Example
Specification by Example
is a collaborative way of getting to the right requirements and tests very very quickly in a short iterative process.
Trainer Gojko Adzic
Specification by example (also called Acceptance-test driven development, ATDD) is a collaborative approach to defining requirements and business-oriented functional tests for software products based on capturing and illustrating requirements using realistic examples instead of abstract statements.
With specification by example, requirements and tests become one, expressed as concrete, realistic examples.
- the key principles of specification by example, behaviour driven development, effect mapping
- how to create and maintain effective specifications and tests in agile and lean projects
- how to ensure a shared understanding of testers, developers, business analysts and stakeholders on future functionality
- 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
- best practices for designing specifications and automating them as testsø
- 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
- how to apply this process in your project
Every participant will be given Gojko Adzic's 2 popular books:
1. Fifty Quick Ideas To Improve Your User Stories
2. Fifty Quick Ideas to Improve your Tests.
- Specification by example
- Behaviour driven development (BDD)
- Agile testing
- Agile requirements
- Impact mapping
- Collaboration
- testers
- business analysts
- developers
- product owners working Scrum or Kanban projects and based on Gojko Adzic’s books Specification by Example and Bridging the Communication Gap.
Gojko Adzic is a strategic software delivery consultant who works with ambitious teams to improve the quality of their software products and processes. He specialises in agile and lean quality improvement, in particular agile testing, specification by example and behaviour driven development.
Gojko is the author of Specification by Example, Bridging the Communication Gap, Test Driven .NET Development with FitNesse and The Secret Ninja Cucumber Scrolls
It was great- don't miss an opportunity to attend- Tatiana Veremeeva, system analyst, Helmes
This training was pragmatic, interesting, fun-. Mart Sõmermaa, architect/scrum master/software engineer CGI Eesti AS
Three adjectives or phrases that describe this training are: 1. Communication is the key 2. Development speed is the speed of the slavest person 3. Always try to bring examples. -Margarita Artamonova, system analyst, Kühne - Nagel
I initially wanted to attend Gojko's course on Agile Acceptance Testing because I wanted to learn about test automation and how to do it well. As a product owner, I came to realize that I was going to have to change a lot of what I did. I needed to learn how to make requirements definite, unambiguous, atomic - not only so that they might be an input into an automation process but also because I want to create something the whole company can understand, something that is concise to read and something I can easily keep up to date.- Patrick O'Malley, Product Manager, Yahoo Inc.