Zbyszek Mockun
Clan Head / Engineering Manager
Cognifide
location_on Poland
Member since 3 years
Share
Zbyszek Mockun
Specialises In
He started his career years ago working for Motorola corporation, then moving to medium size company – CapeTechnologies to finally land at a startup called Cognifide, where he has worked for over 11 years. In this International company, he has taken a reverse journey from startup to corporation (like Tolkien’s “There and back again”). He understands the importance of values and ranks them higher than processes which often contradict those values especially as the company grows. He can also see the big picture and understands that grow gives new opportunities.
Co-Founder of the oldest Polish testing meetup – PTAQ, and a series of podcasts (TestingParrot), and frequent speaker. Currently working as Clan Head / Development Manager, previously as Global Head of QA Practice at Cognifide. He also helps other companies as a consultant for grow and transformation processes.
-
keyboard_arrow_down
Automation in the world of projects
45 Mins
Case Study
Intermediate
The world of a software house is a constant search for compromise between quality and costs. In many cases, the cost-cutting starts from the test automation. Then you start to talk about ROI but recognize that numbers are not on your side. We were there and what we have found out is that only a complete change in our approach allows us to find common ground with our clients. I will reveal one detail from the presentation - we are not talking about test automation with clients anymore - as a result we do it more and more.
Are you surprised that success automatically generates new challenges which we further translate into opportunities? We had to reconsider our approach to the test automation environment, internal frameworks and the way we share them between projects, including code ownership, … And again, one simple but unobvious solution allows us to both deliver what we promise and to earn more on our projects.
As we have been reshaping our approach to the test automation, we had to change the way of delivery too. One of the main decisions was skip out the role of test automation engineer (or software developer in test). We decided to go with the whole team approach which is consistent with the way we sell it.
Find it interesting? Join me and listen to our story about how we have transformed test automation.
-
-
No more submissions exist.
