Why do you need QA people and you need them NOW!

• How many times have you get tired of the back-and-forth on bug reporting and fixing after months of development?
• How many times have a project go overbudget because developers didn't really get all necessary scenarios covered in their tests?
• How many unsatisfied emails did you get from angry clients that just wanted their projects delivered on-time with the expected quality?

If you've answered several for any of this questions, it is probably time to review your QA (Quality Assurance) strategy!

In this talk we're going to show you how a dedicated QA person could partner with the PM and the Tech lead/Architect in order to ensure a better coverage of the use cases/test scenarios on multiple projects and how it would help on controling the quality of the software delivered by your developers.

Throughtout the talk we'll see how to take better advantage of several well-know tools and also talk about simple scripts, internal tools and sets of rules for pre-screening and managing projects deployments to either stage or production.

Besides that, we also need to teach customers that QA is an important thing and we should spend some money earlier on this to avoid spend lots of time and/or losing tons of money later. How-to?

Test early, Test often.

I can ensure a QA person involved on projects from discovery phase will cost much less than handling tests and bug fixing later, situation where budgets are gone and margins usually get burnt.

It's not an attack to developers. I'm a developer too!
But it's past the time where QA should be taken more seriously during development.