I've observed that many teams begin with just developers and an extremely tight deadline. When this occurs, the team is under pressure to deliver and quality is not always a priority, resulting in it being sacrificed with the promise of addressing it later. This can become a problem, causing the team's delivery to slow down and new features to require more development work. At this point, teams start thinking about how they can improve the quality of their project and often resort to hiring a QA person for this endeavor. However, without the proper team structure and support, this can be a very difficult task for the new team member.

Many times, the QA role is only introduced in teams when things have already gone wrong, so I began to question whether it is a symptom of a dysfunctional team.

During this talk, I want to share my journey as a QA. I began as a manual QA, then moved on to automation, led a QA department, returned to automation, and ultimately transitioned to software development. Throughout this journey, my role has changed significantly. I would like to share tips and tricks that helped me build quality as a practice within the team, rather than making it the sole responsibility of the QA person.