Over the years I have started to notice patterns of problems and what they’re related to. This is a post exploring those thoughts and how I tend to approach software development projects. There are lots of techniques I use, however, one of those is something that I’m calling GAM. It…

In the back of my head sometimes I start to think “Oh I don’t know about Automation” so I can’t have a say in it. However, when I sit down and really think about it — I do know a lot. …

I’ve been hearing some new terminology from my team that is related to data modelling. In particular different types of data models, such as conceptual, logical or physical. So I thought I’d do some research and read around on what these actually mean. …

This question is on my mind after an experience where I have raised a problem, however, I struggled to get understanding and action taken from it. It was only when the stakeholder experienced the problem first hand that they really understood it and was able to then take action from…

Lately I’ve found myself talking more to my team about quality and how we are going to be building it in, rather than quality being an afterthought. Prior to this, the past month or so I have found myself, to be quite frank, very reactive to situations and not thinking…

Lately I’ve been swirling around thoughts of how awkward calling out problems are, especially the ones where everyone thinks there is no problem or perhaps a few have noticed the problem, yet no one is calling for action. Say for example you are creating a User Guide to support users…

Have you been on a project where non functional requirements are an afterthought? I dislike the terms functional and non functional requirements (NFRs) because it starts to divide requirements discussions into two parts. This is why in my opinion, using this terminology is a cause of NFRs becoming an afterthought. …

In my previous blog post I wrote about the One Page Test Plan. At the end I openly said that I was using this format for my current project and it simply wasn’t working. So I spent some time evaluating to find a way forward. I found a good question in a well known testing book that was “Why bother testing?”. I’ve found it a valuable question. It has made me think and articulate the concept of risk, how testing activities should be focused around risk and the overall value add of testing activities in a project. I can clearly explain to stakeholders on what exactly the plan is.

At the beginning of the week on LinkedIn I recommended the One Page Test Plan. I never imagined the amount of reaction it would get. To date it has over 600+ Likes, 52 comments, 42 reposts and over 90,000 impressions. …