Skip to main content

Scrum Master Mind Map

Just remembered I built this mind map a while ago on a Scrum Master contract. There are a few things that I have learn't since and would probably change. Its always interesting to look back though and see how you felt about something at the time.

I guess the main thing that leaps out at me is that I saw it as a leadership role, without the 'servant' bit in front of it. I may well have 'frustrated' other team members with my domineering attitude.

You'll be delighted to know that I haven't changed a bit.......


  1. I can second that last line... :-)

    You may have seen it as a leadership role at the time, hence some of the strong statements. One thing that really stands out, though, is the emphasis at every stage on being positive and conveying that to the team. I know many a manager and lead who could benefit from that top tip alone.

  2. A good summary... A few 'lessons learned' over the years.

    1. Plan to stabilise your demo/showcase at the end of the iteration. Don't assume you can carry on coding until 5 mins before the deadline :-)

    2. Have a defect triage process and follow it periodically. Is the 'defect' really critical for this iteration? Is it really a defect or a requirements issue (new story).

    3. Consider technical debt. Re-factoring should be par for the course but this is 'hidden' from estimates.

    4. When to do the stand up. Keep it regular and permanent. There is never an excuse not to hold a standup, even if the build is broken.

  3. I love mind maps! I'm working in the testing/development software industry and I'm finding the tool so super helpful.

    Also, I'm passing this on to my friend who's a scrummaster. She'll find it really cool, I think.


  4. Hi there,
    Love your article .Specially the Map featuring part.Scrum study also has interesting ways to teach the students for agile scrum certification ( Scrum Master Certification ) courses. check their website for some free introductory course in scrum

    1. Hi Angelina

      I do keep meaning to update the map based on my experience of the last couple of years. Plus I have done Product Ownership since too, have a different point of view.

      It might be fun to do the whole exercise again and compare the two. See how much my perception of the role has changed!

      All the best,



Post a Comment

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…