Skip to main content

Don't worry, it'll hold together. You hear me, agile transformation? Hold together!

Things are getting interesting. 

Your organisation has been transforming itself to an agile way of working for, say, a year or so now. Now comes the critical moment, which I will hereafter refer to as ‘The Wobble.’

‘The Wobble’ is a series of questions and searching of souls. ’Is this transformation really working?’ and ‘Are we working on the right features, at the right pace, with the right value, at the right level of quality?’ are common. Now, here’s the trick and it sound a little woolly but bear with me, if your business sponsors don’t know that its working, then I’m afraid that this confusion is trying to tell you something. That something generally is that something is wrong.

Like most of life’s wobbles, ‘The Wobble’ itself not the key, the reaction to ‘The Wobble’ is critical. So what are common reactions?

Abandon Ship! Liberally distribute yourselves overboard and revert to chaos. By which I mean your previous methodology, which wasn’t even waterfall, just old fashioned chaos.
Measure everything! Try and enforce blanket metrics across teams which mean little to the business and try and ‘standardise’ progress across teams. Think back to why you wanted to transform your organisation. The prison of meaningless metrics probably had something to do with it.
More Resource! Forget you ever read the Mythical Man Month and fully embrace the law of diminishing returns in all its glory.

So, I hear your brains ask, smarty-pants, what would you do?

Don’t panic and add more process – making your teams ‘heavier’ only alienates them, and the business representatives just see more processes and less building of stuff they want. This cycle repeats itself until the team’s produce beautiful reports and documents but no working software. Sound familiar?

Cash Value. In Moolah, Dosh, Wonga, Sterling. In Production - Its time to get honest. It doesn't get more honest than cash. Its honesty tells you where you really are, in your transformation. A lot of features built but still takes two months to put a release together? £0. Building lots of technically interesting features but not what the business wants? £0. I am aware however; very few organisations are willing to be this honest. However, without acknowledging this, you limit your progress and strengthen the power of ‘The Wobble.’

Putting a monetary value on something that is yet to be is hard, but it forces you to ask a great question. If I don’t know what this is worth, then why am I building it. For me the key to agility is honesty, with your team, with your wider project community, with the business. Without it, ‘The Wobble’ becomes more earthquake than minor tremor and may be more than your agile transformation can withstand.


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…

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…