Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Transparency in QA work for management

922 views

Published on

Доклад Юрия Малого на конференции SQA Days-20. 24-26 ноября 2016. Минск
www.sqadays.com

Published in: Education
  • Be the first to comment

Transparency in QA work for management

  1. 1. Software quality assurance days XX International Conference of Software Quality Assurance sqadays.com November 24-26, 2016. Minsk, Belarus Yuriy Malyi COMODO. Odesa, Ukraine Transparency in QA work for management
  2. 2. Transparency in QA work for management Who Am I? Name: Yuriy Malyi Company: COMODO Position: QA manager Experience in IT: 11 years
  3. 3. Transparency in QA work for management Who are You? • How many test engineers are here? • How many managers/team leaders? • How many developers? • How many HR?  • Any other experts?
  4. 4. Transparency - physical property of allowing the transmission of light through a material (с) Wiki What is Transparency? Transparency in QA work for management
  5. 5. Transparency - physical property of allowing the transmission of light through a material (с) Wiki What is Transparency? Transparency in QA work for management
  6. 6. Transparency is operating in such a way that it is easy for others to see what actions are performed. (с) Wiki What does it mean in management? Transparency in QA work for management
  7. 7. Transparency is operating in such a way that it is easy for others to see what actions are performed. (с) Wiki What does it mean in management? Transparency in QA work for management
  8. 8. Transparency in QA work for management Why do we need it, what’s the problem?
  9. 9. Transparency in QA work for management Black Box – NO control
  10. 10. Transparency in QA work for management Transparency – effective control!
  11. 11. Transparency in QA work for management Problem in projects and teams
  12. 12. Transparency in QA work for management Problem in projects and teams
  13. 13. Transparency in QA work for management Problem in projects and teams
  14. 14. Transparency in QA work for management Problem in projects and teams
  15. 15. Transparency in QA work for management Problem in projects and teams
  16. 16. Transparency in QA work for management Problem in projects and teams
  17. 17. Transparency in QA work for management Prehistory • What are you doing right now? • Why testing takes so much time? • There is nothing to do so long! • I can complete this task 10 times faster! • Why You missed those BUGs during testing? • What are your automation team is doing? • Convince me! • Bullshit! • Etс…
  18. 18. Transparency in QA work for management Preconditions • Projects and teams (      ) • Tasks and BUGs tracker (~Jira) • Work time logging system (~Jira Tempo) • Wiki (~Confluence) • Calendar (~Confluence calendars) • Test Management System (~ TestRail) • Willing to see the real situation in QA
  19. 19. Transparency in QA work for management QA Team current state
  20. 20. Transparency in QA work for management QA Team current state
  21. 21. Transparency in QA work for management Capacity and details in tempo
  22. 22. Transparency in QA work for management Capacity and details in tempo
  23. 23. Transparency in QA work for management Feature Readiness Page
  24. 24. Transparency in QA work for management Feature Risks Statuses • Feature can’t be delivered in time • Developments and Testing at risk • Feature may be delivered in time • Dev and Testing at the low risk • Feature may be delivered in time • Dev done, Testing at the low risk • Feature will be delivered in time • Dev done, Testing done
  25. 25. Transparency in QA work for management Feature Readiness - Risk Matrix
  26. 26. Transparency in QA work for management BUG status for releases
  27. 27. Transparency in QA work for management Live link to Jira
  28. 28. Transparency in QA work for management BUG status for releases
  29. 29. Transparency in QA work for management Bugs daily progress(goal is “0” BUG rate)
  30. 30. Transparency in QA work for management Change Management Board
  31. 31. Transparency in QA work for management Detailed current status of Automation
  32. 32. Transparency in QA work for management Detailed plan to achieve a goal Test cases for automation 1144 Current automation percent 27% Goal for automation percent 80% Number of cases to achhive the goal 916 Already automated 311 Need to be automated 605 Team performance (test cases/week) 15 Number of weeks to achhive a goal 40.33
  33. 33. Transparency in QA work for management Detailed reporting every week
  34. 34. Transparency in QA work for management Real reflection of automated test cases
  35. 35. Transparency in QA work for management Minimize time for reports
  36. 36. Transparency in QA work for management Time cost • QA Team current state ~10 min per day for TL • WorkLog in Jira ~5 min per day for engineer • Feature Readiness Page ~2 hours create by TL • Feature Readiness Page ~5 min day to support • BUG status for releases ~1-3 min create by TL • Bugs daily progress ~1-3 min create by TL • Change Management ~10 min for PM on request • Detailed status and plan of Automation ~1-3 days • Automation report ~10 min per week for TL
  37. 37. Transparency in QA work for management Success Story • Half a year of transparency… • New urgent release required… • Request to complete in NOW! • And… • Just 2 emails in replay • Details of all previous efforts • And we protected estimates! • … • Profit! 
  38. 38. Transparency in QA work for management The last weapon
  39. 39. Transparency in QA work for management If you're going through hell…
  40. 40. https://www.facebook.com/yuriy.malyi/posts/1153307468059014 (UKR) keep going. - Winston Churchill
  41. 41. Transparency in QA work for management Email : yuriy.malyi@gmail.com Skype : yura_clasic Questions?

×