| || |
A quality presentation for developers?
I am the only quality resource in my company and I have been asked to make a quality presentation for the new developers so they can understand the quality aspects from the very beginning.
So what should I be talking about in the presentation that might help the developers know more about my role and help them do their work better in regarding of quality?
Can you please provide me with topics to be mentioned in the presentation..
Your help will be much appreciated
I always enjoy examples of defects that cost a ton of money to fix when just a slight amount of QA would have been useful.
The space telescope used a combination of metric and British measurements and the lens did not work.
Huge systems blew up because of one missing character in code.
There are a lot of examples on the internet.
You can give examples of people going to the wrong place or time for a meeting.
Then show how QA with a process or by Explorative means could have caught this.
That would be my presentation. However you may want to be more detailed and show technically how you would do the QA. If so, let us know more about what you want to accomplish in the meeting.
Those examples would be a good start for your presentation, and I see those a lot over here as well.
However, I would go beyond that and stress what you do as a QA person and how you are going to collaborate with the development team in order to achieve the common goal of delivering high quality software.
Point out what:
- You are going to bring to the table;
- You can do for the developers to make their life easier and better;
- You expect from the developers in order to achieve the project goals.
Presentations like this are an excellent opportunity for that.
Giving example of quality cost is brilliant.. I'll definitely going to mention that in the presentation. So thanks a lot Kevin
I'm going to upload the presentation here once it's done so everyone can use it
Great points @basd ... Now I can see how the presentation is going to look like after reading your points, so thank you very much basd
I have posted a reply to basd, but it wasn't posted form some reason..
I was saying how your points are great and it how they cleared up my vision for the presentation
Thank you very much basd
You're welcome, good luck
I would hope in this day and age all developers would be familiar with the qa process.
One thing you may add, if you are using any sort of automation tool, a demo of how it interacts and what elements it can see and what identifiers should remain static when possible.
I would say, emphasize that QA is a resource to help developers.
I think many new developers, especially developers coming in from college (who never had their code scrutinized before), take bug reports as a personal attack that "they are no good". They get defensive, and use the "as designed" excuse. New developers get too emotionally charged over bug reports than they should be. A bug is not necessarily "wrong". It's just a perceived difference between what the customer needs (as interpreted by the specs and non-functional requirements) and what was in place.
I think it's important to say, it's not your bug, but it's the team's bug. Even though we have separate titles, Developer, QA, SET, Test Engineer, Ops.. We're working on the same product and share the same vision of providing a valuable service to the customer.
Yeah, we are there to cover their backs really. Good developers will realize we are their best friends.
Also make the point that the entire team is responsible for quality.