Michał Krzyżanowski

An experienced QA Engineer. Test automation specialist, trainer, and evangelist. Technical testing, CI/CD, and Test/DevOps enthusiast. A QA Lead responsible for quality-related aspects throughout the project lifecycle, now also a consultant helping others with automating their work. He regularly searches how to improve even the good solutions.

Embraces his love of discussing things as one of the DebatQA co-hosts. Speaker at various meetups and conferences. Part of the TestWarez 2018 programme committee. Blogger at automatingguy.com.

Building rockets for cavemen – the reality of software development for corporate client

Working for big, well-known companies from Fortune 500 may sound like a prestigious thing. Ambitious initiatives with multiple-digit budgets, opportunity to work with numerous teams spread across the whole world sound amazing too. Everyone expects and waits for the project to be a grand success, pushing the client to the frontiers of innovation – something often dubbed ‘digital transformation’.

But how do you proceed when you realize your client is not in a Lean or Agile mindset, even though they claim differently? How do you assure quality along with an organization that is not focusing on it enough? What to do when instead of merely doing your job, you are forced to be involved in some internal corporate politics? How do you squeeze in any learning opportunities and innovation inside a ridiculously planned project? What about implementing a new, fancy technology that you know is not a good choice for the current situation, but the CTO of your client decided otherwise?

How do you proceed when you are tasked to build a rocket for someone that still has not discovered a wheel?

I would like to tell you about my experience as a QA and a project lead while working alongside such organizations and the brutal reality of corporate world that we do not discuss or silently accept. I am going to share how I’ve coped with it, what was a success and, most importantly, where I have failed.

– How can you approach an ‘enterprise-grade’ environment and what are your options
– How to influence your client with good practices and not get swayed by their bad ones
– Why sometimes we, the IT, are the ones creating problems with our tech solutions
– Why thinking in projects instead of products will not help you in assuring quality
– Why innovation, unfortunately, is not for everyone and that accepting the fact you can’t change everything will save your sanity

Język prezentacji (Presentation language): English
Poziom słuchaczy (attendee level): wszyscy (all)