Three Ways Testers Are Better Able To Resolve Conflict

I’m not talking about “scary conflict”. There is lots of healthy conflict at work when you have a diverse and inclusive team. It might be technical decisions (tabs or spaces?), product plans (high risk or high return first?) or casual choices (where do we go to for lunch today?). When I think of “scary conflict” I think of personal grudges, unprofessional behaviour or confronting office politics. Those conflicts need to be resolved but are much more confronting.

Continue reading “Three Ways Testers Are Better Able To Resolve Conflict”

Testing as a Holistic Exercise

Early on when trying to apply Agile methods to software development I found a lot of the challenges were in the area of software testing. Not just because a lot more automated testing was being done, but because requirements would shift and change rapidly. Many levels of rapid feedback needed to be in place to ensure the development didn’t misstep for too long.

I started exploring more places a focus on testing and quality could be applied. And that led me on a journey earlier and earlier in the development timeline.

Continue reading “Testing as a Holistic Exercise”

Avoiding Giving Advice

There is a famous experiment in behavioural science called the Marshmallow Experiment. In the simplest version of this experiment they sat down a child in front of a marshmallow, the instructor told the child that if they sat there and waited the instructor would come back with an additional marshmallow and they could have both. However if they took the one marshmallow before the instructor returned then that was all they would get. Once the child understood the instructions they were left alone for 15 minutes.

Continue reading “Avoiding Giving Advice”