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....




Labels:

Comments

  1. Joe Brannan21 May 2013 at 03:39

    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. Gareth Waterhouse21 May 2013 at 05:31

      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. Srinivas Kadiyala21 May 2013 at 05:25

    Thanks for sharing the post.

    What is PBI's ?

    ReplyDelete
    Replies
    1. Gareth Waterhouse21 May 2013 at 05:34

      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. Phil21 May 2013 at 05:58

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

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

    ReplyDelete
  4. Amar G Deogirikar22 May 2013 at 06:33

    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. Gareth Waterhouse15 July 2013 at 03:44

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

      Delete
  5. Unknown10 October 2017 at 02:04

    Great blog. Thank you for sharing. The information you shared is very effective for learners.Keep Updating...

    Best Embedded System Training in Chennai | Embedded Course in Chennai | Embedded Training in Chennai | Best Embedded Training in Chennai | Embedded Systems Course in Chennai | Matlab Training in Chennai | LabVIEW Training in Chennai | VLSI Training in Chennai

    ReplyDelete

Post a Comment

Popular posts from this blog

What is a PBI?

After my last post, I had the question of what is a PBI... so I thought i'd write a short blog post about what they are and why they are used. A PBI is an acronym for Product Backlog Item. It is a description of a piece of work that your SCRUM team will develop and deliver. When you have a list of Product Backlog Items, you then refer to that collective list as a Product Backlog. The product backlog is often prioritised and yourteam will work through each PBI, and release on a regular schedule... I am however going deep into the world of Agile development, which isn't entirely what this post is about, so I will stop myself now. A Product Backlog Item is made up of the following: Title - This is often a one liner that gives the team an idea of what the PBI is about, although it can just be an ID for the item and the team work off of that. Description - Breaks down the PBI in a bit more detail, and can be written in any style, however I prefer it to be written as follow...
68 comments
Read more

Coding something simple.... or not! Taking a screenshot on error using Selenium WebDriver

I recently wrote a little function that takes a screenshot at the end of a test if it has errored. What sounded very simple at the start turned out to be quite a bit of work, and quite a few lines of code to handle certain scenarios! It's now over 50 lines of code! I'll start with what I had at the beginning, this was to simply take a screenshot in the working directory, we are using SpecFlow and Selenium to run the tests, so we are going to check if the ScenarioContext.Current.TestError isn't null, if it is, then using Selenium, take a screenshot (note the below code is a simplified version of what I had at the beginning). [AfterScenario]         public static void TakeScreenShotOnError()         {             if (ScenarioContext.Current.TestError == null) return;             var screenshotDriver = Driver as ITakesScreenshot;             if (screenshotD...
15 comments
Read more

The Stickman Tester... The full version complete with deleted "scenes"!

As some of you may have seen, a little while ago I performed a 99 second talk on the Stickman Tester for the Ministry of Testing. Owing to the fact that it had to be 99 seconds, this unfortunately meant that a verse was left out in order to keep it within the time frame! It's only now that I have found the time to put the deleted verse/scene back in, and re-record it and upload it! (It's now a 120 second talk!) It talks about a testers journey in an Agile team, about how not everybody has it as good as others, and basically talks about not giving up, keep searching, or trying to change your role to make it what you want it to be. Anyway, here it is, in all it's glory. Hope you enjoy it!
15 comments
Read more