Skip to main content

Inadvertent Local Optimisation

I saw this tweet the other day:
Followed swiftly by:
This got me thinking about a process I am often involved in. 

Reviews of 'testing capability and maturity' are a common product offered by many lone consultants & consultancies. I myself have done them on a regular basis, creating a number of (I believe) thoughtful strategies and recommendations that a client can implement themselves and/or in conjunction with a partner.

I like to think, I've probably done some good too. Looking for root causes over the dreaded 'low hanging fruit' that so many consultants recommend (see drug dealer).

When I really reflect though, I'm pretty sure most things I have recommended are inadvertent local optimisation. Conducting a review into testing is a classic misdirection, as a great many problems in how testing is done in an organisation, are symptoms of wider problems. A subsconscious misdirection, but a misdirection nonetheless.

Next time, before engaging, I'll ask:

  • Where does attending to the needs of your people come on your priority list?
  • Does work get done based on value or who can shout loudest?
  • Have you got too much work in progress?
  • Do you have teams with all the skills needed to deliver and autonomy to solve their problems?

Once we've dealt with these root causes, then we can talk about testing. Or we might not need to, perhaps dealing with what is systemic will assist with clearing up those symptoms.

Maybe Doctors and Consultants should share the same oath:
"First, do no harm." 
 

Comments

Popular posts from this blog

A Lone Tester at a DevOps Conference

I recently had the chance to go to Velocity Conf in Amsterdam, which one might describe as a DevOps conference. I love going to conferences of all types, restricting the self to discipline specific events is counter intuitive to me, as each discipline involved in building and supporting something isn't isolated. Even if some organisations try and keep it that way, reality barges its way in. Gotta speak to each other some day.

So, I was in an awesome city, anticipating an enlightening few days. Velocity is big. I sometimes forget how big business some conferences are, most testing events I attend are usually in the hundreds of attendees. With big conferences comes the trappings of big business. For my part, I swapped product and testability ideas with Datadog, Pager Duty and others for swag. My going rate for consultancy appears to be tshirts, stickers and hats.

So, lets get to it:

3 Takeaways

Inclusiveness - there was a huge focus on effective teams, organisational dynamics and splitt…

Wheel of Testing Part 2 - Content

Thank you Reddit, while attempting to find pictures of the earths core, you surpass yourself.
Turns out Steve Buscemi is the centre of the world.

Anyway. Lets start with something I hold to be true. My testing career is mine to shape, it has many influences but only one driver. No one will do it for me. Organisations that offer a career (or even a vocation) are offering something that is not theirs to give. Too much of their own needs get in the way, plus morphing into a badass question-asker, assumption-challenger, claim-demolisher and illusion-breaker is a bit terrifying for most organisations. Therefore, I hope the wheel is a tool for possibilities not definitive answers, otherwise it would just be another tool trying to provide a path which is yours to define.


In part one, I discussed why I had thought about the wheel of testing in terms of my own motivations for creating it, plus applying the reasoning of a career in testing to it. As in, coming up with a sensible reflection of real…

Getting started with testability

At TestBash Netherlands, I said that, in my experience, a lot of testers don't really get testability. I would feel bad if I didn't follow that up with a starting point for expanding your mindset and explicitly thinking about testability day to day, and making your testing lives better! 

In large scale, high transaction systems testability really is critical, as compared to the vastness and variability of the world, testing done within organisations, before deployment, is limited by comparison. We need ways to see and learn from the systems we test where it matters, in Production.
Being able to observe, control and understand is central to testing effectively, and there are loads of resources and experience reports out there to help. I was/am inspired by James Bach, Seth Eliot, Matt Skelton, Sally Goble, Martin Fowler and a little bit of PerfBytes/Logchat, so lets see if it works for you! 

Overall Model:

Heuristics of Software Testability by James Bach

http://www.satisfice.com/tool…