Is quality really everyone's responsibility - The Quality Accountability conundrum
"Quality is everyone's responsibility" has to be one of those phrases which looks great on t-shirts and posters but when put into action, often fails.
There is a funny leadership story which goes like this " There was an important job to be done and Everybody was sure that Somebody would do it. Anybody could have done it, but Nobody did it"
Therefore assuming that everyone in your team (developers, designers, QEs or analysts) would be instinctively inclined to incorporating quality in their day to day work is a terrible assumption to make.
Quality is everyone's responsibility might be true but it cannot work in isolation, it has to be supplemented with an accountability framework.
In this talk, I am going to present exactly that framework and help people especially leaders - technical and people, implement proactive quality processes in their teams.
The information presented in this talk does not require audience to have any technical knowledge and applies to all the roles.
Outline/Structure of the Talk
How we as a team make wrong assumptions in terms of quality and who is responsible for it.
Establishing a framework for quality gatekeeping vs accountability
Q and A
A major takeaway for the audience would be learning about their role in the quality accountability framework.
Developers, QEs, Project Mangers and in fact everyone who is a part of software development process.
Prerequisites for Attendees
Basic knowledge of what Software development process is.
schedule Submitted 8 months ago
People who liked this proposal, also liked:
Tomasz Wojciechowski / Tomasz Wojtuń - How to run 2500 selenium tests in an hour.Tomasz WojciechowskiSr. QA EngineerStepStone Services Sp.z o.o.Tomasz WojtuńDevOps EngineerStepStone
schedule 8 months agoSold Out!
If you are tired of waiting for your selenium tests status and old fasioned ways of reporting tests status, you are in a good place.
We will show you our test environment setup and how we run over 2500 tests in about an hour. Not cool enough? Take a look how we make reports via slack.
Do you want to check if we can be even more faster?