The Power of Example Mapping! with @kika
Who writes the acceptance criteria for your stories - Product owners, Business analysts or the entire team? If the Given-When-Then scenarios are already prewritten and presented to the team, their thought process is curtailed. It might also lead to preconceived ideas and notions. This also tips the responsibility towards a single stakeholder which can prove to be dangerous. What is the alternative then?
Discover the Power of Example Mapping!
Example Mapping is a great way to motivate the team to adopt Behaviour Driven Development. The whole practice is about encouraging communication and collaboration between the various stakeholders. It is of prime importance in an agile setup that the Product, Dev and Tester share the same understanding and have equal partnership in the stories/features delivered. Example mapping facilitates these conversations and also goes hand in hand with the shift left approach. In a nutshell, it is a great team activity which results in substantial gains and increases in productivity.
We will find out what Example Mapping is and how to do it.
- Understand the importance of Example Mapping and how the participants can use it in their teams
- Tips on convincing the entire team to try this approach
- Practical implementation with use cases for all kinds of stories whether it is a user story or a non-user story
- What more could be done with this mapping approach
- Limitations of Example Mapping and when not to use it
We’ll use this Club thread to share resources mentioned during the session and answer any questions we don’t get to during the live session.