14/05/2024
There has been a marked reduction on the number of testing roles out there over the last couple of years, but this isn't because less software is being written.
🟣 Does that mean that Shift-Left is actually working, with development teams testing their software sufficiently before releasing it? We can hope, but I doubt it.
🟣 Does this mean that more issues are being caught through CI/CD? I am sure there is some truth to this; automated testing is more likely to catch obvious regression than manual testing because it is less prone to human error - as long as it is properly maintained.
🟣 I think what it does mean is that organisations now feel more confident in their development processes. And yet bugs still make it through to production...
This is where Quality Assurance is just as important as it always was, maybe even more so given the complexity of so much software these days.
🟢 If you have got your development and release processes nailed, then it's time to make the small changes likely to have the biggest impact on the quality of your releases. It is time to focus on your requirements.
🟢 If your processes use documented requirements then implement SMART, INVEST, 7-point checks, 5-Whys etc.
🟢 If you follow agile ways of working then introduce regular reviews of backlog items, only starting development when everyone is agreement on what the task requires. 3-Amigos is a great technique to follow.
🟢 Using a hybrid approach? Then pick the bits from above that work for you, just don't do anything for the sake of it. Everything should add value.
I say it a lot, but Software Quality is everyone's responsibility. Get buy-in from BAs, Project Managers, Product Owners and End Users and you might just see those production bug numbers come down even further.
The image? Nothing to do with my post. One of the bunches of grapes we have on our grape vine this year. Fingers crossed we'll have a reasonable harvest.
