Jakub Kminek, Quality Assurance Lead at RWS, talks about how QA is an integral part of software development and how we are reducing the number of bugs in Agile software development by making QA a part of the development from the very beginning, from first discussions about the future product.
EH: Hello everyone and welcome to another AMI interview. I would like to welcome all of you who are watching this interview in the year 2021. Still from home. By the way I would like to welcome our Quality Assurance Lead, Jakub Kminek. Kubi, hi!
EH: Kubi, my first question for you would be, can you introduce yourself and tell us a little bit about you?
JK: Ok, my name is Jakub Kminek and I'm currently leading software quality assurance team in RWS. My work journey started as a skiing and snowboarding instructor many years ago and then I moved to IT, where I started actually in IT operations team. And then switched sides, moving to release management, release engineering, to the development teams and to DevOps team, and I was leading two teams, one of them was specialized in test automation framework development and from this position I moved to RWS where I'm currently leading the software quality assurance team for the third year.
EH: So my first question would be, how does QA fit into Agile software development?
JK: QA as a quality assurance is an integral part of software development, any software development, especially Agile software development. By making sure that expected quality is delivered to our customers, we are fulfilling their needs and fulfilling their requests, and helping them actually grow and maintain their business.
EH: Kubi, can you tell us basically if, if it's possible, and how we can prevent bugs?
JK: Software is being developed by humans. And humans do make errors, and software is a complex thing. It's never possible to deliver software without bugs, however we can reduce the number of bugs to acceptable level needed by our customers. In some cases, the request is to deliver the software quick and dirty, just basic functionality and we don't care about small issues. However, this approach won't work in more regulated industries like life science medical science or banking. This can work in gaming or simple applications. In our case it works that way that we try to be part of the development from the very beginning, from first discussions about the future product and to build the testability in. To do the static testing of the requirements in our case mostly user stories. And we are part of the whole development process till the end, till the delivery to the customers, to the reviews, demos and so on.
EH: Yeah, so that's a perfect solution! And as you can see also we take QA testers as a part of the team so they are present at every Scrum event, right? And we try to put them... They are not like a separate team member. We include them in all of the development work.
EH: Ok Kubi. So I think that was my last question. Thank you! And thank you guys so much for watching and I will see you next time, bye.