Example mapping - slice any story into testable examples - SoCraTes 2022.pdf
0 likes109 views
The document discusses the process of example mapping to enhance user story clarity and validation in software development. It emphasizes the importance of creating rules and examples collaboratively among testers, programmers, and product owners to surface hidden assumptions and identify acceptance criteria. Additionally, it outlines best practices for conducting example mapping sessions efficiently and effectively.
Example mapping - slice any story into testable examples - SoCraTes 2022.pdf
- 1. Example mapping - slice any story into testable examples Seb Rose Twitter: @sebrose Blog: https://cucumber.io/blog/ E-mail: seb.rose@smartbear.com
- 2. @sebrose seb.rose@smartbear.com “The hardest part of building a software system is deciding precisely what to build.” -Fred Brooks, The Mythical Man-Month
- 5. @sebrose seb.rose@smartbear.com • Do we meet our De fi nition Of Ready? • Shared understanding of outcome of user story • Empathy for our different roles • User story statement • Requirement • Technical details • Candidate acceptance criteria Inputs / outputs
- 6. @sebrose seb.rose@smartbear.com Example map https://cucumber.io/blog/2015/12/08/example- mapping-introduction https://youtu.be/EtoTML8cuko Story Rule Rule Example Example Example Question Example Rule Question Question Example Example Introducing Example Mapping
- 7. @sebrose seb.rose@smartbear.com Rules vs Examples AKA, The Passwords Game
- 8. @sebrose seb.rose@smartbear.com Form teams • Need an even number of teams • 2-4 people per team
- 9. @sebrose seb.rose@smartbear.com In order to prevent passwords from being guessed, Users creating or changing a password must be forced to use a strong password
- 10. @sebrose seb.rose@smartbear.com Create 3 rules • In your team, invent 3 rules for what makes a valid (i.e. “strong”) password • Keep the rules secret from the other team • Be imaginative, and have a bit of fun • Examples: • "It must have an @ in it" • "It must not be the name of a fruit"
- 11. @sebrose seb.rose@smartbear.com “@ntelope" => valid "apple" => invalid "tom@to" => invalid Create 3 examples • Create 3 examples that illustrate your rules. • Scribble each one on a post-it note • Examples:
- 12. @sebrose seb.rose@smartbear.com Guess the rules! • Pass your examples to another team. • Let them try to work out what your rules might be.
- 13. @sebrose seb.rose@smartbear.com Clarify with examples • As a guessing team, you can create new examples and ask them to be checked by the team whose rules you're trying to guess. • One example at a time. • How many examples will it take to guess?
- 14. @sebrose seb.rose@smartbear.com What was missing?
- 15. @sebrose seb.rose@smartbear.com Which is more important - example or rule?
- 16. @sebrose seb.rose@smartbear.com Rules: • Faster to write • Clarify boundaries; concise • Closer to the code • Close down conversations • Can be vague / ambiguous Examples vs Rules Examples: • Clarify the rules • Generate empathy for the customer • Tease out bad rules • Allow for conversation • Expose different perspectives
- 17. @sebrose seb.rose@smartbear.com We need rules and examples
- 18. @sebrose seb.rose@smartbear.com Use examples to illustrate the rules
- 19. @sebrose seb.rose@smartbear.com Use examples to validate the rules
- 20. @sebrose seb.rose@smartbear.com Writing better stories
- 21. @sebrose seb.rose@smartbear.com What challenges have you had with stories? • Discuss your experiences with your team • Keep a note of what you hear
- 22. @sebrose seb.rose@smartbear.com What can you deduce from this example map? Story Rule Rule Example Rule
- 23. @sebrose seb.rose@smartbear.com What can you deduce from this example map? Story Rule Rule Example Question Example Rule Question Question Example Example Example Example Question
- 24. @sebrose seb.rose@smartbear.com What can you deduce from this example map? Story Rule Rule Example Example Rule Example Example Example Example Example Example Example Example
- 25. @sebrose seb.rose@smartbear.com What can you deduce from this example map? Story Rule Rule Example Example Rule Example Example Example Example Example Example
- 26. @sebrose seb.rose@smartbear.com What can you deduce from this example map? Story Rule Rule Example Example Rule Example Rule Rule Rule Rule Example Example Example Example Example Example Example Example Example Example Example
- 28. @sebrose seb.rose@smartbear.com Example mapping can help! • Clarify requirements • Surface hidden assumptions • Identify acceptance tests • Split user stories • Gain empathy for other roles • Shorten iteration planning and “grooming”
- 29. @sebrose The three practices of BDD | Examples of system behaviour are documented using business terminology | The documentation is automated, creating living documentation that verifies the system’s behaviour | Create a shared understanding of the requirements through collaboration, typically achieved through a structured conversation centered on rules and examples https://cucumber.io/docs/bdd/ Proprietary & Confidential BDD approach
- 30. @sebrose seb.rose@smartbear.com Keep example mapping short (less than 30 minutes) Not everyone need attend (6 or fewer) All unanswered questions should have owners Schedule example mapping daily (after stand-up) Business, dev, & test needed to be quorate (3 amigos) PO/BA brings story & candidate rules (not examples) Try to write examples fi rst, rather than talk Give team at least 24 hours notice about story being discussed (select relevant expertise) In my experience … High bandwidth is priority (don’t use Given/When/ Then) during Discovery
- 31. Seb Rose Twitter: @sebrose Blog: https://cucumber.io/blog/ E-mail: seb.rose@smartbear.com http://bddbooks.com https://cucumber.io/blog/2015/12/08/example- mapping-introduction https://youtu.be/EtoTML8cuko Introducing Example Mapping