I’ve seen many teams that start only with developers and a very tight deadline. When that happens, teams are in a rush to deliver and quality might not be their priority, so it is usually sacrificed with the promise of taking care of it latter. This becomes a problem, to the point where team delivery slows down and adding new features requires more development work. By this time, teams start thinking about how they can increase the quality in their project, and they most commonly resort to hiring a QA person for this endeavour. However, without the proper team structure and support this is going to be a very difficult task for our new team member.
Many times the QA role is only introduced in teams when things are broken, so I started questioning myself whether it is a symptom of a dysfunctional team.
During this talk I want to go through my journey as a QA. I started as a manual QA, then I started doing automation, at some point I lead a QA department, I went back to automation and finally moved to software development. During this journey my role has changed a lot. I would like to explain tips and tricks that helped me build quality as a practise inside the team instead of making it a responsibility of the QA person.
-------------
¡Conoce Autentia!
-Twitter:
https://goo.gl/MU5pUQ
-Instagram:
https://lk.autentia.com/instagram
-LinkedIn:
https://goo.gl/2On7Fj/
-Facebook:
https://goo.gl/o8HrWX