Are you interested in creating more structured requirements and tests? Do you want to improve your communication bridge and avoid common mistakes? Join Gojko Adzic for this exciting two day workshop!
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.
Learn how to:
- 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
- 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
- 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
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.