This seems like an obvious question and many people have successfully conquered it and set up a standard for reporting. Every once in a while it falls apart and people get blindsided by extra requests that they did not expect but for the most part it works fairly well.
We first mentioned this question a couple of weeks ago. The obvious and simple answer is to provide what your stakeholders want to have provided. The only issue with that statement is that we find a lot of stakeholders:
- Do not always know what they want at the beginning of a project.
- Change their minds as the project changes it risk profile (Stakeholders start taking more interest as the project risk increases and commensurately less interest as the project risk decreases)
Since testers and Quality Assurance personnel are in the ‘Risk Reduction’ business we are in a good position to answer that question for them. As part of the anlysis of the project and the required testing, we will be judging the risk of the project and concentrating our testing on that. So we have a handle on the overall risk profile at the start. We can start with a level of reporting reflecting that risk profile.
Since Software Testers and Quality Assurance personnel are also the ‘canary in mine’ when things start to go wrong, we can ramp up the reporting preemptively when things start to go wrong. For example, if there is a sudden surge in severe defects in a project, then we can start providing more information and recommendations.
Most of the above seems obvious but when you are busy testing, the temptation is to leave the reporting at the same level (or even reduce it when we are busy). That is the exact opposite of what is needed.
Next week – Some specifics for reporting.
If you are in the Greater Toronto Area or Kitchener-Waterloo you might want to consider these events to network with other QA people or learn some of the new ideas in QA.N NVP Software Solutions will be participating in the following software testing and quality...read more
Following on from the theme of last month, many organisations are dissatisfied with their testing. They feel it is incomplete, or ineffective or costs too much. At the end of the testing effort they are left with a vague feeling of unease. Often it is difficult for...read more
Photo by Harry Sandhu on Unsplash We wanted to start the new-year off with a topic we hear a lot about from many, many people. A couple of weeks ago we talked about the issue of Software Testing being Ad Hoc and some of the reasons this might be the case. See the blog...read more
If you are in the Greater Toronto Area or Kitchener-Waterloo you might want to consider these events to network with other QA people or learn some of the new ideas in QA. NVP Software Solutions will be participating in the following software testing and quality...read more
Photo by Harry Sandhu on Unsplash We wanted to start the new-year off with a topic we hear a lot about from many many people. Our Software Testing is Ad-hoc (i.e. created or done for a particular purpose as necessary.). It is never reused.We are always...read more
So what is coming in 2019. No doubt, if that could be predicted accurately, we would not be doing this right now! We would be somewhere on a warm sunny beach. The easy answers are: Manual testing will continue.More automation will be done and much more will be wanted...read more
Review of the Year – Automationread more
Review of the Year - Manual Testing Manual Testing is something that seems to be on the minds of many Quality Assurance Managers and Test Leads. Usually they want out of the Manual Testing and view Automated Testing (Blog planned for next week) as the saviour of their...read more
QA with No Time One of the constant issues that comes up in discussions or classes is the lack of time for Quality Assurance and Quality Control. We seem to be under constant time pressure and with Agile and DevOps it has become worse rather than better. While Quality...read more
A Better Way - Case Study 5 - Distributed with Poor Testing In our last several blogs we have discussed 'A Better Way to Test". The issue is to apply this to actual situations. We have 5 Case Studies we plan to use over the next several weeks to address this. The...read more