QA, Quality Assurance
Introduction
Hello everyone! I hope you had a wonderful work week, and I wish you a restful weekend. This week a colleague and I were talking about the role of QA. We’re trying to figure out internal processes and how we want to tackle gaps that we see in our current approach. She opened my eyes to new possibilities for the role of QA, and it blew my mind! I want to share pieces of knowledge from that conversation with all of you.
QA or Quality Assurance has been one of my favourite teams working at software companies. I think it is one of the most underappreciated teams and processes. The importance of QA is immeasurable, and I think it is time to change that perspective.
Scoping out the work and Requirements Gathering
Back in the day, when I was working for companies that hadn’t adopted an Agile Methodology, one of the main things I used to ask for while gathering requirements was, “What are the outcomes you’re expecting from this feature?”. I would not only compile the list of wants but the expected outcomes. We called these test cases. It’s an extensive list of inputs and expected outputs. It might not be a complete list of all the scenarios that might happen…
