Skip to main content

MindMaps 101

Apologies for the lack of updates, it's been a busy week, had my 3 year wedding anniversary last week, so was busy sorting stuff out for that, and had a bit of a hectic weekend! :)

Anyway, I've recently been reading a lot about mindmaps, and how they are useful when brainstorming and coming up with areas that may or may not need testing when a story/pbi comes in.

I started to wonder what the fuss was about, so I recently created a MindMap for a recent blog post here and found it extremely useful.

So let me go over how they work, and then I'll explain how I personally find them helpful and hopefully you will too.

They are an extremely simple concept, you have your theme in the middle and off of that branches anything that you think is related or want to investigate, and then you can have branches off of them too... And so on... I find that the mind will naturally flow from one area to the next, and you won't have to think too hard and you won't forget important areas.

So let me give a brief example, say you want to discuss performance testing, you could then branch off and discuss why it's important, and then off of that discuss common performance issues. 



As you can see you can branch off a number of times, and can create quite the interesting mindmap. I've seen some with so many points on, for instance this one here around android testing is massive and extremely useful to anyone who wishes to know more about testing on an android device. This illustrates that it doesn't matter how big or how small a mindmap is, it can be useful to you, and will be useful to you and hopefully others will also find it useful and learn something from it.

I currently use bubbl.us but am on the look out for a free version which will allow me to save as much as I want, so if anyone has any suggestions shout :)

I don't use mindmaps all the time for pbis and test planning, as some are so small that it's not necessary, and I'm still quite new to them, so am trying to use them as efficiently as possible, I am using them whenever I think of a new blog post, and I try and share them with you when I can. The one for this blog post is at the bottom of this post... so enjoy! In a future post I'll take an example PBI and come up with a mindmap for it....




Comments

  1. I'm very similar - I've seen a lot about mindmaps on twitter, but haven't really used them since university days. Then I came across an example where I thought they might come in useful, thanks to twitter I found the free software 'Freemind' and now have a dozen mindmaps covering a variety of topics.

    ReplyDelete
    Replies
    1. I had a look at FreeMind, and I guess I'll have to play about with it some more in order to understand it's powers fully, but there are definitely tools about there. Bubbls.us was just easy and intuitive to use.

      Delete
  2. Thanks for sharing the post.

    What is PBI's ?

    ReplyDelete
    Replies
    1. PBIs are Product Backlog Items, they are often a User story, and written in the following context:

      As a User
      I want to have something available to me/some new functionality
      So that I can do something

      They are effectively an item of work that the team will have to work on. Commonly found in an Agile environment. I'll try and write a blog post about them in the future....

      Delete
  3. Mindmaps spread - have you seen the 101 from Darren McMillan?

    http://www.bettertesting.co.uk/content/?p=956

    ReplyDelete
  4. Nice one, I have been trying to find out more about "lean and mean" test case design using mind maps techniques, because I am lazy to write detailed long and meaningless test cases. The business requirements where I work change day to day and I need to edit/rewrite test cases frequently. It is a big task to keep up with everything! Is this something you can extend with an example in your future posts! :)

    ReplyDelete
    Replies
    1. There is one in the works! Just been really busy lately!!! Hopefully I can deliver it soon!

      Delete

Post a Comment

Popular posts from this blog

Testers: Be more like a Super-Villain!

Who doesn't love a Super Hero? Talk to my son, and he'll tell you how much he loves them, talk to many adults and they'll say the same! Deep down, we all love to be the Super Hero, we all want to save the day! However, I want to talk about the flip side of Super Heroes, the Super Villains... I often play Imaginext with my son, and I (unfortunately?) am nearly always the Super Villain! Be it Lex Luthor, Joker, Two Face, Mr Freeze or The Riddler! These are all great characters and great Super Villains, but why would I want to write about Super Villains? A while ago where I worked, we had a few Super Heroes, people who would be able to come in and "fix" things that had broken and help deliver projects on time. We then shifted, we decided to do away with the Super Hero culture and try and prevent from being in that position in the first place, whilst we didn't go as far as wanting to hire Super Villains, it's definitely a story that has stuck with me and t...

QA is Awesome!

No real point to this post other than I have had the song stuck in my head and figured I could change it slightly and quite easily make QA is Awesome! Oh and I haven't even seen the movie all the way through! But for some reason that song is incredibly catchy! Not much point to this post in fact, just thought I'd put it out there :)

Measuring QA Key Skills and Competencies

I have been thinking about how I can help encourage self improvement within my team, as I understand it, everyone wants to improve, it's just that often there are a number of things that hold people back. I believe one of these things that hold people back are around identifying skills that they are perhaps weak in or that they could/should improve on. So I thought about how I can help tackle that problem. One solution that I want to try with people is to identify the key skills for a QA, what key skills should every QA have, or at least what key skills make up a good QA? If I can identify these then I can start helping people identify if they are lacking in an area. Sure there is a competency matrix that we have, but it has things like "An excellent understanding of XXX", it's often very difficult to quantify what an excellent understanding actually is. So I sat down and came up with the following key skills: OOP Test Documentation Manual Testing Automated...