Why QA?

M.4.O.
M.4.O.
Jul 24, 2017 · 1 min read

Even for those little projects the QA must be present, not only you would notice changes on the process but also your product would improve, evolve at the same time as it grows.

QA is not only for the code, will also make the communication a collaboration of the team better, in my experience a good QA comes along with a particular set of social skills.

Is important to have a couple more of eyes before we are ready to say, We are ready!

QA not only would see what you see but also would take the customers, developers and the owners side, so you can be sure main interests are present on our daily work.

QA would improve your software and your team is gonna feel more confident about it, back and forth during developing cycle can’t be avoided but for sure the unnecessary collecting and recollecting of data can be minimized following basic steps when writing Stories or ticket for development.

This goes to complement of course the tools we have at hand to create a stable and confident environment where all members of the team feel empowerment and access to do change.

Trust me IM a QA

M.4.O.

Written by

M.4.O.

@bout | Music | Food | Weirdo | Writer | Cook | Tech |

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade