By Lisa Crispin
After consolidating my notes and photos from Agile Testing Days (so many devices! Plus sketch notes!), I realized it’s way too much for one post. I’m taking the advice of tweeps and serializing this novel. First up: the workshop I facilitated on Advanced Topics in Agile Testing. I must emphasize that I was only a facilitator. I organized brainstorming exercises, and we all shared our experiences. We generated some interesting ideas!
We had 18 participants including myself, and they were truly advanced, lots of experience in both agile and testing, working in a variety of domains. I was so happy to meet so many people who have improved their process and product. Most work in globally distributed companies.
Goals and Purpose
We started by setting SMART goals around the testing-related problems and obstacles each participant faces on their own teams. For example, one team had a goal “get faster feedback with automated tests in three months using nightly builds”, another had “automate regression tests which cover the work of several teams”. Not everyone managed to follow the whole SMART pattern, but we had plenty of interesting issues to address. Topics ranged from how to get started with ATDD to “dev and QA love”.
Then we tried different brainstorming techniques to come up with small experiments that participants could try back at work. The first one was impact mapping. Most people weren’t familiar with it, so I gave an introduction.
Each table group took their highest priority topic and started out by explaining the “why”, the purpose of the goal. Next, they brainstormed about who could help attain the goal, or who might get in the way of success. The next step was to consider each “who” and decide how they could help or hinder, the impacts. Finally we discussed deliverables, the “what” for each “why, who, how” combination. After each ‘round’, the groups shared their outcomes. To wrap up, each team chose one or two experiments to try when they get back to work. The general feeling was that these were doable experiments worth trying.
The exercise generated lots of interesting ideas. One group came up with the idea to pair across teams in order to improve communication and get a better understanding of the product. Another team proposed creating a definition of done for each epic to improve test coverage.
To address the next highest priority goal for each group, we used a simpler technique, mind mapping. The free-form discussion with everyone adding nodes to the group mind map stimulated helpful thoughts. The groups ended up using sticky notes as the nodes, which was a bit more practical with five or six people working on the same map.
After lunch, everyone self-organized into new table groups, and we tried another brainstorming technique, “brainwriting“, to come up with experiments around the next highest priority goal. This works in five minute intervals. Each person starts writing ideas on a piece of paper. At the end of five minutes, they pass it on to the person on their right, read the ideas on the new piece of paper they received, and see if that sparks more ideas.
The room was quiet for 30 minutes as everyone wrote. I was surprised how many unique ideas each group came up with. And I was surprised how creative people got, using mind maps and graphics to illustrate their ideas. This proved the most popular brainstorming technique. As one participant commented, it’s fair, because everyone gets an equal chance to contribute.
The next go-round, teams used the “super powers” technique, where you dream what you’d do if you had super powers such as x-ray vision or the ability to teleport, or SWOT analysis – What are the Strengths, Weaknesses, Opportunities and Threats currently relevant to your goal?
Some groups tried both. The SWOT was confusing, the difference between weaknesses and threats for example is a blurry line. These techniques weren’t as popular as brain writing, but led to some creative experiments.
In between brainstorming sessions, we had large group discussions on topics that emerged. I enjoyed hearing the different experiences team members shared. Since I was facilitating, I couldn’t easily take notes, but I learned some insights into tough areas such as working in a highly regulated domain. Pore over the photos for some inspiration.
Try it yourself
See more photos from the workshop, sorry they aren’t more organized, but maybe they’ll inspire you to try some of these techniques yourself, with your own team! Identify the areas where you want to improve, set SMART goals, and brainstorm small experiments to try. Learn from those experiments to chip away at obstacles and achieve your goals of high-quality software that delight your customers!
The post Agile Testing Days, part 1 of ?: Brainstorming! appeared first on Agile Testing with Lisa Crispin.
Comments are off
By Lisa Crispin