Skip to main content

Helping


I’m currently experiencing something I never thought I would.

The technology team I work in isn’t the slightly odd, dysfunctional part of the business, tucked away in the corner, showing signs of madness, gibbering binary nonsense at anyone who strays within range. I believe we are a high functioning team and have gone further, we are reaching out and contributing to improving the wider organisational system. I know, I have fallen off my chair several times.

How are we achieving this state I hear you ask? I won’t provide an illusion of perfection but I think we are doing these things really well:
  • Saying yes, because technology is the art of the possible. Genuinely living the ethos that we can build what you need, share your priorities, help us understand, then we’ll get to it. Go to point 2.
  • Releasing stuff regularly to get feedback. I know this is old hat, but you’d be amazed what it can achieve. Roughly weekly, mostly when it’s valuable, not overloading. Asking if you want more stuff, not here’s more stuff.
  • Helping to determine what the organisation considers valuable over falling down the rabbit hole of what we can provide. The perennial conversation that we’ve all been involved with, I’ll tell you what I want, when you tell me what you can give me. Which usually results in the wrong solution to a poorly understood problem.
  • Providing coaching on the implications of technology. As in technology and what it means for the business proposition, not just how technology has been implemented. Where is it strong or weak? What choices did we make? 
  • Espousing the value of team. That every team should have everything it needs in order to succeed. If the team needs these skills, then let’s make that happen. Also, not just filling gaps. For example, not just hiring testers, but encouraging testers to encourage others to take responsibility in appropriate ways. If you hire more testers, you’ll more than likely get more testing, but less likely a great deal more value.
  • Genuinely hiring for behaviours. I’ve played at this before, but that urge to think ‘commercially’ has meant rushed decisions with months of pain. Making the hiring process equitable (you have to be happy with us, not just us happy with you) is much more pragmatic than the misery for both parties of being a square peg in a round hole.
  • Asking for clarity on the mission. Usually the technology teams are the last to know and/or understand the mission of the organisation. Not us. Rather than trying to hide on the periphery, we are front and centre of the mission, discussing how technology can enable us to realise that mission.
I personally love being a part of all this. I hope we can create an organisation which genuinely lives its values. Something I’ve been seeking for a long time.

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…

What if information isn't enough?

One of my aims for this year has been to attend/talk at what I will class for the purposes of this blog as 'non-testing' events, primarily to speak about what on earth testing is and how we can lampoon the myths and legends around it. It gets some really interesting reactions from professionals within other disciplines.

And usually those reactions (much like this particular blog), leave me with more questions than answers!

Huh?

After speaking at a recent event, I was asked an interesting question by an attendee. This guy was great, he reinvented himself every few years into a new part of technology, his current focus, machine learning. His previous life, 'Big Data', more on that later. Anyway, he said (something like):

'I enjoyed your talk but I think testing as an information provider doesn't go far enough. If they aren't actionable insights, then what's the point?'
This is why I like 'non-testing' events, someone challenging a tenet than has be…