Kiruthika Ganesan

Head of QA


I am currently the Head of QA at Deko with over 14 years of experience in the IT industry, working as a Developer, Tester, and Tutor. However, testing is what I am passionate about because I get to experience the best of both worlds, from understanding what the customer really wants, through to seeing how the magic really happens.

When I am not working, I love spending time with my kids and enjoy writing short stories.

The power of Example Mapping

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 encourage 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 increase in productivity.


  1. How to engage with various stakeholders and what type of working together will make sense in a particular context?
  2. Working together effectively involves planning, discipline and empathy. How to achieve this and what tools can help us?
  3. Productivity of this activity depends on the achieved results. How to report the results, gather feedback, learn and repeat it again.
  4. How not to overdo it and kill the innovation and creativity which are the inherent positives of this approach?