QA is an essential part of the development lifecycle. The QA team tests your code and then the bugs they report return to you to get fixed. Sometimes that relationship can be a challenge as we argue over what is really a bug, try to reproduce the defects identified during QA, and determine the severity of each defect. Improving the relationship between QA and development will help your application development. Join Yaron Tsubery, president of the ISTQB, in Toronto Thursday evening November 23rd, to learn more about how you can work better with your QA team.
Yaron Tsubery is the CEO and Founder of Smartest Technologies Ltd. He will use his experience on complex projects with strict exit criteria and demanding deadlines to help you speed up your application lifecycle through better collaboration between the QA and development teams.
SELA Canada & Microsoft Canada present:
Shorten Release Cycles by Increasing QA and Developer Collaboration
Many (if not all of us) are searching for the best ways to do their job in order to improve the performance and achieve more. Yes, this is the era which we all are living – many results (which always must be the best results) shall be presented in a very short time – what business persons call TTM (Time To Market). One of our tasks as test engineers or as test managers is to find the path(s) that will lead to effective results based on efficient processes; in the 1st case we are searching for results in terms of better and improved test coverage and in the 2nd case we are searching for large scale, efficient and effective defect detection, both better to be achieved in a short time.
Many ways are suggested and visible for implementation of both the above paths; few methods are developed for them, but my objective is to present a parallel aspect, related to 'soft skills' and maturity elements, that can accelerate the time to market. I'll present collaboration challenges and actions required to be taken by both the QA and the Development departments. Questions like: How to do it? What is expected from us? Who is leading the collaboration? What's in it for me as a developer and/or as a test engineer? Where (if at all) are the borders between the departments? Tools to measure the progress and the success, and more will be tackled. The practice is focused on projects of complex systems, delivered to telecommunication companies under restricted rules and stiff exit criteria elements – which made this more complex and challenging to handle along with tense delivery timelines. You'll be able to understand what the impact that we achieved through this practice was.
Register today because you and I both know just telling the QA team “If I can’t reproduce it, I can’t fix it” isn’t really the best answer