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

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…

The Team Test for Testability

You know what I see quite a lot. Really long-winded test maturity models. 

You know what I love to see? Really fast, meaningful ways to build a picture of your teams current state and provoke a conversation about improvement. The excellent test improvement card game by Huib Schoots and Joep Schuurkes is a great example. I also really like 'The Joel Test' by Joel Spolsky, a number of questions you can answer yes or no to to gain insight into their effectiveness as a software development team.

I thought something like this for testability might an interesting experiment, so here goes:

If you ask the team to change their codebase do they react positively?Does each member of the team have access to the system source control?Does the team know which parts of the codebase are subject to the most change?Does the team collaborate regularly with teams that maintain their dependencies?Does the team have regular contact with the users of the system?Can you set your system into a given state…