Skip to main content

Mr Big Stuff, Who Do You Think You Are?


Ever worked on a project when you thought 'I wish the sponsors were more involved?' That would really help to clarify the vision and focus the team on what is truly valuable.

That is a noble wish, one I have echoed many times. However, experience is now telling me something a little different, that perhaps that desire is entirely dependant on the sponsor you wish to involve. Say hello to our old friend context again.

What happens if your sponsor (as they can be) is a real big hitter in the organisation? And god forbid, they are being judged on the delivery of your project by an even bigger cheese. So, your big cheese starts getting hot and heavy with the team, interrupting stand ups, looming over your shoulder and getting all judgemental.

As a Scrum Master, I've dealt with this a few times, so a little practical advice:

1. Cut the Shit - sponsors will want direct answers. This is the best way to deflect attentions from your team. Patience and seniority are sometimes not happy bedfellows.
2. Take the Heat - take one for the team. If the sponsor wants information and you don't have it, volunteer to get it. Then you can pick the timing of any actions required.
3. Role Power Matters - As much as people show a significant amount of bravado, role power hugely matters. Find out from your team whom it matters most to. If there is fear (rational or irrational) from one or more team members then you know who to shield most.
4. Post Storm Repair - Sometimes there is nothing you can do. You will be railroaded. But, these sponsor interventions come in bursts in reaction to a specific issue so they are finite. You may judge this as defeatist but sometimes you need to pick your battles, so have your recovery plan (people first, then project later) ready.

Unless you want one of these in the middle of your team, you'd better act and fast.



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…