Transparency in QA work for management
Usually if You ask QA tea or team leader what are You doing right now and why testing not completed in time you'll receive number of different reasons.
Manager : Why the whole team completed only 7 TestCases during the whole day?
TeamLead: We were blocked with BUGs 5343, 5356 and 5377.
Manager: Why weren't You refactoring test cases and verifying other BUGs?
TeamLead: We've checked 5 new builds, created 10 new and reopened 7 old bugs!
For the real understanding of all underground processes You have to spent much time and carefully track every QA in the team.
Otherwise it seems that QA team is working not effectively.
During the presentation I will introduce you autonomic system of Transparency in QA work in details and share the main templates.
It will be useful for managers and team leaders who needs to protect their QA resources.
Simple QA Audit
- Release failed again...
- Seems so...
- We have to urgently improve the quality of our releases!
- Agree - let's have a quality audit!
- Great! But how?
- We could invite consultors for 100500 of money.
- No, we are out of budget anyway...
- And what we can do?
- Well, You are QA manager - You must decide!
So, the task is absolutely clear and understandable :)
After analyze the huge volume of information about quality audit was decided to create simple model, which minimize efforts to conduct audit and allow to reflect realtime progress.
As a result, there was created QA Audit checklist which evolved from 59 points to 109 in 9 month!
Now I'm conducting audit for 13 projects every month - before Monthly Operations Review.
It takes me from 20 minutes up to 2 hours, depending on improvements and maturity of every project.
During the presentation I'll share the checklist template and introduce the auditing process in details based on the real project.
Monthly Operations Review
Metrics, metrics, metrics... what do you want from me? Again? For crying out loud!
Probably, every leader had to deal with the question "How is it going?"
How can we measure it? What does these digits means? How was it before? And so on and so forth...
During last 2 years I have been struggling with this problem in 3 different projects.
As a result we've created "Monthly Operations Review" report with a set of the most effective metrics.
I'm implementing this report in 4 projects more the last half a year, and I can definitely say, that it shows the real projects situation, and allows us to make proper decisions for quality improvement in time.
During the presentation I will introduce the process of metrics gathering in details and share the report template.
It will be useful for managers and team leaders who needs to improve the overall quality of their projects.
Global role of QA Manager in companys life
So, you have Scrum, Agile, separate DEV/QA teams, Project Managers and planning in MS Project.
But in the end of the 4-6 weeks Sprint QA team working 12-18 hours per day - and even with those efforts you must shift new release for 5-7 days. Sprint failed again...
In the beginning on new sprint project manager adding risks to fit the planned date.
Surprise! During the sprint You got several urgent changes which must be done and in the end of the sprint QA overtimes and date shift repeats.
QA teams are exhausted and skip simple bugs which will be found by users on the first day of production.
Let's investigate the role of QA manager in the global improvement of the situation.
The presentation will be useful as for managers and team leads as for those who are looking for their way in testing. I'll highlight points, which could be initiated by junior and middle QAs.
No standard practices and theory - only personal experience and best practices in several companies.