Cambridge Lean Coffee – April 2015

2015-04-29 08.26.51Held at DisplayLink on the 29th April – there were a whopping 18 people in attendance!

This isn’t a write up about the discussions we had, but we decided that it would be cool to list topics that were discussed/on the backlog.

We talked about

  • Regression testing – what to cut?
  • Test strategies – what real value have you found in them?
  • How do you make sure testing takes place early enough in a sprint?

Left on the backlog

  • Scrum teams cross-functionality and tester vs developer tasks?
  • Running internal test community without a test manager?
  • Android/IOS App testing experiences
  • Testing for negatives – where do you stop?
  • Showing the value of exploratory testing to “non-testers”
  • How do you decide how to compatibility test
  • Requirement management/traceability

Next one at Redgate on the 27th May- meetup

One thought to “Cambridge Lean Coffee – April 2015”

  1. The lean coffee is a #agilistic forum . April was my first one attended , hope they all follow this format. Accessible by all levels of skill in test, manual and automation, design and strategists alike. We split into 2 groups and compiled a list of hot topics, voted on them and were give a few minutes each to “expound” what we knew on a topic and then allowed some time to field questions before rapidly moving onto the next voted item. Covered a lot of ground actually, including unofficial “qualification/certification” bashing ala ISTQB and IEC standards. But used that to establish concensus, to swordplay and keep the ball rolling; which it really did feel like. Almost being in an Indiana Jones scene with a large stone chasing us down a tunnel. Why regression suites have to slowly get trimmed when tests that cover old behaviours in automation-test become fragile. Some automation flaws and; even disgreement with James Bach perhaps? How automation finds (arguably) more defects during it’s creation than it does during automated test execution later on. How clear separation of language is vital (and IMO the only good thing in the ISTQB) in order to get your point across as a tester. How to understand the value of your work, and brag when it goes right or delivers value.

Leave a Reply

Your email address will not be published. Required fields are marked *