Testing the Waterhouse

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

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