For a long while now I’ve worked on close-knit teams that need to be high functioning in order to stay productive and deliver work at the pace employers and customers…
Read More
All posts by Simon Knight
One of the things you’ve probably noticed when you’ve been software testing for a while, and particularly when you’ve been testing the same product for any length of time, is that your brain starts to settle into some established ways of thinking about the software you’re testing.
After a while you already know where lots of the more challenging areas of your product are, and when you begin to do some testing you make a beeline for those areas because they’ve already proven themselves to be the most fertile hunting grounds for juicy bugs.
But how did you get into that area of they system? What route did you follow, and what might you have missed along the way?
What if instead of making that beeline – you branched out in a completely different direction?
What might you find instead?
cunning strategies for being super tight-focused with work; AKA how to maintain an awesome level of productivity in the face of unrelenting distractions.
I thought this was a good read from Marty Cagan: https://svpg.com/product-vs-feature-teams/ TLDR; feature teams just facilitate the delivery of features requested by stakeholders; they’re not really doing product discovery – just…
I enjoyed this insightful post from testing commentator James Christie, analysing the recent Boeing 737 crashes and their implications for developers, testers and organisational leaders alike: An abdication of managerial responsibility? “If…
