Specification By Example: Why It’s Hard, Why It’s Worth It, and How You Can Get Started
Suppose someone from support drops by your team with a question. No one on the team can remember exactly how that feature from the last release works. The document you created to guide development is out of date. Jira tickets lack detail. The developers start digging into the source code for answers.
There has to be a better way. There is. Itʼs called Specification by Example.
Hear the story of how a sceptical Product Owner and an experienced Agile Developer used Specification by Example to radically increase shared understanding and team collaboration.
In the second part of the session, everyone is invited to use our toolkit to build a plan to introduce Specification by Example to your own team.
Leave empowered to educate your team and others on why and how to get started.
Outline/Structure of the Talk
- Introduction and Agenda (5 mins)
- What is Specification by Example? (10 mins)
- Relation to the Agile Test Quadrants
- Adoption according to VersionOne State of Agile Survey
- Driver for Cross-Functional Team Collaboration
- Common Blockers to Successful Introduction of Specification by Example (5 mins)
- Our success story using Specification by Example on our last project (15 mins)
- Organized as a Timeline
- Activities that helped our team
- Resources used
- Toolkit for participants to start Specification by Example (20 mins)
- Distribute index cards with Common Blockers, Potential First Steps, and Adoption Milestones.
- Individuals, pairs, or colleagues use the provided toolkit to build their own plan to start Specification by Example.
- Close Activity/Share (5 mins)
- Participants will learn what Specification by Example is and how it can help their teams
- Participants will leave with concrete steps to help their team start implementing Specification by Example to level up their collaboration
- Participants will be directed to the best resources to help them succeed in implementing Specification by Example
Agile Coaches and Agile Team Members (Product Owners, Testers, and Developers)
Prerequisites for Attendees
Work on or with software development teams