I’m super happy to work with a company that puts a lot of energy into the quality assurance part of every single software development project.
Quality assurance is a discipline that’s overlooked and under-appreciated. We produce software, share it with the team, test it, collect feedback, ask beta testers and then do it over again. Share, test, collect, ask, repeat. Yup, that’s pretty much it.
Yet people treat quality assurance as something superficial – a few tests here, a few user feedback there, and with one big eye staring at the release button.
The traditional waterfall approach of QA
Software development, in general, used to follow the traditional waterfall model. And QA and testing have always been one of the last steps before going live.
As one might imagine, being one of the last steps in the project chain, sometimes meant making up time for previous delays.
Or even worse: Sometimes QA & testing activities showed that the product was not working for the target group.
More agile QA.
The agile movement helped a lot. And although there’s still a lot of room left for a more agile approach to QA, agile testing established a continuous collaboration between development and QA teams. And it makes sure throughout the entire project that QA efforts are undertaken.
The middle man
The best, bug-free software comes from excellent programmers with a lot of practical experience.
But excellent programmers don’t automatically make good testers. It requires someone to have a variety of soft and hard skills. And it is a balancing act to be part of a QA team.
Quality assurance people (or sometimes just referred to as “software testers”) serve as proxies for the company’s audience. They understand what your users need and appreciate. And are able to help developers build what is necessary to reach their users.
What is Quality Assurance?
When developing hardware or software, quality assurance (QA) is “any systematic process of checking to see whether a product or service being developed is meeting specified requirements.”
Or as Wikipedia states:
Tools and standards like ISO 9000 help companies to establish and maintain effective QA workflows when building a product. I know this sounds unpractical. However, I recommend you to take a closer look at those ISO 9000 standards and you’ll find a lot of practical guidance and advice when building a new software or hardware.
One example: The first principle stated inside ISO 9000 is about customer focus. It is made clear that you can only succeed if you “strive to exceed customer expectations”.
And QA is there to help you along the road.
There’s more than one approach of QA
Quality assurance isn’t a single process. There are a number of different types, frameworks, and stages.
A common mistake is only focusing on one of these areas. Especially as a small software company, it’s easy to bury your head into stress- and failure tests, then setting up continuous testing.
QA is about culture
The easy thing for development teams is to avoid QA at all. You’ll avoid spending time and resources that way, but you’ll avoid your users too. And therefore success.
If you have a solid quality assurance process in place, and developers and testers are willing to engage, and bounce feedback, you’ll notice an increase in users using your software (or hardware).
5 Types Of User Acceptance Testing
This article is brought to you by Usersnap, a user testing tool that helps you to communicate visually. Get a 15-day free trial here. The methodology of User Acceptance Testing (UAT) is pretty straight-forward. The implementation itself requires some in-depth knowledge on the available types of User Acceptance Testing, though. User Acceptance Testing is the…
Designing a language switch: Examples and best practices
Building a global SaaS product isn’t easy. You have to localize your product, translate your website, and make sure that everything’s still up and running. And there might be a major interface problem, which looks like a tiny thing at first but is actually something to think about a little longer. What I’m talking about…
GitLab vs GitHub: Key differences & similarities
This article is brought to you by Usersnap. Usersnap helps you to communicate visually. And the best part? It connects with GitLab and GitHub. Get a 15-day free trial here. Version Control repository management services are a key component in the software development workflow. In the last few years, GitHub and GitLab positioned themselves as…
6 Ways for Web Product Managers to Collect Customer Feedback
You’ve just launched your new product or you just finished building a new website, and now you wonder what your customers think about those changes. How do you collect customer feedback in the best way possible to answer your questions? Can customer feedback really provide insights to improve your product? Let’s see 6 ways you can approach…
How to be a faster programmer: 7 helpful tips for being faster & more successful.
A while ago, I published some ideas on how to become a faster programmer on Quora. Since then, people have left comments and wrote follow-up questions. I think I have dipped into an interesting topic and decided to collect my tips in a blog post. I hope you’ll find it helpful and it will make…
Is Email the best customer support channel?
A lot has been written on how companies can grow their business through customer success. The terms “customer success” or “customer experience” seem to be the new buzzwords in the growth-driven tech world. These discussions are great, and we at Usersnap believe that customer support and customer success are important factors when it comes to business…
Get experts insights & cutting edge ideas for digital product development.
We have asked six experts to bring you lessons learned about user testing and product development.