Creating QA Dashboard

18,879 views

Published on

Published in: Business
1 Comment
7 Likes
Statistics
Notes
  • More than 5000 registered IT consultants and Corporates.Search for IT online training Providers at http://www.todaycourses.com
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total views
18,879
On SlideShare
0
From Embeds
0
Number of Embeds
16
Actions
Shares
0
Downloads
407
Comments
1
Likes
7
Embeds 0
No embeds

No notes for slide

Creating QA Dashboard

  1. 1. Building QA Dashboard Based on a Real Project by Petro Porchuk 2010
  2. 2. Core PDLC Issues <ul><li>BAD Planning
  3. 3. BAD Communication
  4. 4. BAD Tasks Distribution
  5. 5. BAD Control
  6. 6. Too Much Time WASTE for Reporting
  7. 7. People Motivation
  8. 8. Continuous Customer Confidence Prompt
  9. 9. BAD Project Risks Visibility
  10. 10. Underestimation </li></ul>? Copyright 2010 Petro Porchuk, Lohika
  11. 11. QA Dashboard (QAD) – The Structure Copyright 2010 Petro Porchuk, Lohika Wiki Menu (URLs) Test Spec. Board Planning Board Defects Board BTP Quality Board Reports Board <ul><li>Plan
  12. 12. Resource
  13. 13. Map </li></ul><ul><li>Filters
  14. 14. Metrics </li></ul><ul><li>Metrics </li></ul><ul><li>Metrics </li></ul><ul><li>Reports
  15. 15. Tables
  16. 16. CheckLists </li></ul>
  17. 17. QAD – The Implementation (JIRA Portlet Macro) <ul><li>The Dashboard is the first screen you see when you login to JIRA. It can be configured to display many different types of information, depending on your areas of interest.
  18. 18. The JIRA Portlet Macro allows you to display a JIRA dashboard portlet on a Confluence page. JIRA is the issue tracking and project management system supplied by Atlassian. </li></ul>http://confluence.atlassian.com/display/JIRA/Customising+the+Dashboard http://confluence.atlassian.com/display/DOC/JIRA+Portlet+Macro Copyright 2010 Petro Porchuk, Lohika
  19. 19. QAD – The Philosophy ! <ul><li>Building the QAD should be done as P3 Task.
  20. 20. The QAD update should be automated AMAP.
  21. 21. You don't work for statistics – statistics works for you !
  22. 22. QAD should be available for every team player.
  23. 23. Everyone should be keeping the QAD sources up-to-date and accurate in scope of his/her responsibilities.
  24. 24. QAD is a tool , use it! </li></ul>Copyright 2010 Petro Porchuk, Lohika
  25. 25. Planning Board <ul><li>QA Project Plan
  26. 26. QA Resource Map </li></ul>Copyright 2010 Petro Porchuk, Lohika
  27. 27. QA Project Plan <ul><li>Overall Plan
  28. 28. (“Big Picture”)
  29. 29. Tasks Dependencies
  30. 30. Assignment per Person
  31. 31. Timings
  32. 32. Deadlines </li></ul>Tools : <ul><li>MS Project / OpenProj
  33. 33. Paint / Paint.net
  34. 34. Wiki / Confluence </li></ul>Copyright 2010 Petro Porchuk, Lohika
  35. 35. QA Resource Map <ul><li>Clear Daily Basis Tasks!!
  36. 36. Tasks Distribution
  37. 37. Great Visibility
  38. 38. Links Container
  39. 39. Capacity Reflection
  40. 40. Tasks Overlay Visibility
  41. 41. Easy Archive Activities (Excel Tabs) </li></ul>Tools : <ul><li>MS Excel / OpenOffice
  42. 42. Wiki / Confluence </li></ul>Copyright 2010 Petro Porchuk, Lohika
  43. 43. Tom DeMarco on Measurement „ You can not control what you can not measure. Measurement is the prerequisite to management control. “ from Tom DeMarco American Consultant, 1982 Copyright 2010 Petro Porchuk, Lohika
  44. 44. Feel Clean and Fresh When? Copyright 2010 Petro Porchuk, Lohika
  45. 45. Why do People change Job? Copyright 2010 Petro Porchuk, Lohika
  46. 46. Test Specification Board <ul><li>TC per Component
  47. 47. TC by Priority
  48. 48. TC Monthly Grouth </li></ul>Copyright 2010 Petro Porchuk, Lohika
  49. 49. TC per Component <ul><li>Overall Coverage Picture
  50. 50. Priorities Look & Feel
  51. 51. Coverage for Equal Complexity Items
  52. 52. Determination of Weak Components
  53. 53. Test Effort Estimation is Easier to Do
  54. 54. Evaluate Smoke Test Effort per Item </li></ul>Tools : <ul><li>MS Excel / OpenOffice
  55. 55. Paint / Paint.net
  56. 56. Wiki / Confluence </li></ul>Copyright 2010 Petro Porchuk, Lohika
  57. 57. TC by Proirity <ul><li>Overall TC Priority Tendency
  58. 58. Consider and Control Test Specification Procedure </li></ul>Tools : <ul><li>MS Excel / OpenOffice
  59. 59. Paint / Paint.net
  60. 60. Wiki / Confluence </li></ul>Copyright 2010 Petro Porchuk, Lohika
  61. 61. TC Monthly Growth Tools : <ul><li>MS Excel / OpenOffice
  62. 62. Paint / Paint.net
  63. 63. Wiki / Confluence </li></ul><ul><li>TC Growth Tendency
  64. 64. Regression Testing Effort Evaluation
  65. 65. Work Progress Retrospective
  66. 66. Consider Automation QA Needs
  67. 67. Consider Team Capacity
  68. 68. Consider Estimates Timing </li></ul>Copyright 2010 Petro Porchuk, Lohika
  69. 69. Defects Board <ul><li>Defects Based Filters (JIRA Filters shown on WIKI) </li></ul><ul><ul><li>Unresolved P1/P2 Bugs
  70. 70. Unresolved Production Bugs
  71. 71. Resolved Issues to Verify </li></ul></ul><ul><li>Defects Based Charts </li></ul><ul><ul><li>Bug Detection Percentage
  72. 72. Production VS Found by QA Bugs
  73. 73. Unresolved Bugs per OFI
  74. 74. Unresolved Bugs per Component
  75. 75. Unresolved Bugs by Priority
  76. 76. All the Bugs by Status </li></ul></ul>Copyright 2010 Petro Porchuk, Lohika
  77. 77. Bug Detection Percentage Tools : <ul><li>JIRA
  78. 78. Wiki / Confluence </li></ul><ul><li>Effectiveness of Testing
  79. 79. Level of Coverage by Regression Tests
  80. 80. Level of Goodness of Feature Tests
  81. 81. Level of Customer Confidence
  82. 82. Level of ROI for QA Team
  83. 83. Level of Risks Mitigation </li></ul>Copyright 2010 Petro Porchuk, Lohika
  84. 84. BDP Analysis Copyright 2010 Petro Porchuk, Lohika BDP < 85 %
  85. 85. Different Charts from one Source Copyright 2010 Petro Porchuk, Lohika
  86. 86. Unresolved Bugs per OFI Tools : <ul><li>JIRA
  87. 87. Wiki / Confluence </li></ul><ul><li>Current Defects State on the Project
  88. 88. Helps to set Priorities for the Team
  89. 89. Helps to find out which Test Level needs to be improved </li></ul>Copyright 2010 Petro Porchuk, Lohika
  90. 90. Unresolved Bugs per Component Tools : <ul><li>JIRA
  91. 91. Wiki / Confluence </li></ul><ul><li>Helps to Identify a WEAK Feature
  92. 92. Helps to Set Priorities for PD, QA Teams
  93. 93. Helps to Plan and Estimate Feature Testing </li></ul>Copyright 2010 Petro Porchuk, Lohika
  94. 94. Unresolved Bugs by Priority Tools : <ul><li>JIRA
  95. 95. Wiki / Confluence </li></ul><ul><li>Shows Current Confidence Level
  96. 96. Shows Project's Reliability </li></ul>Copyright 2010 Petro Porchuk, Lohika
  97. 97. All the Issues by Status Tools : <ul><li>JIRA
  98. 98. Wiki / Confluence </li></ul><ul><li>Helps to Identify BT Processes Quality
  99. 99. Helps to Evaluate Work Scope for either QA or PD team </li></ul>Copyright 2010 Petro Porchuk, Lohika
  100. 100. Bug Tracking Process Quality Board <ul><li>Recently Created Issues
  101. 101. Average Time in Status
  102. 102. Time to First Response
  103. 103. Resolution Time
  104. 104. Average Age
  105. 105. Created vs Resolved Issues </li></ul>Copyright 2010 Petro Porchuk, Lohika
  106. 106. Recently Created Issues Tools : <ul><li>JIRA
  107. 107. Wiki / Confluence </li></ul><ul><li>Created Issues
  108. 108. Resolved Issues
  109. 109. Created vs Resolved Issues
  110. 110. Level of Code Quality </li></ul>Copyright 2010 Petro Porchuk, Lohika
  111. 111. Average Time in Status Tools : <ul><li>JIRA
  112. 112. Wiki / Confluence </li></ul>Helps to Identify Whether: <ul><li>QA Team Checks Issues In Time
  113. 113. PD Team Handles Issues In Time
  114. 114. PD Lead Reacts Quickly Assigning
  115. 115. QA Drops are not a Bottle Neck of the Process </li></ul>Copyright 2010 Petro Porchuk, Lohika
  116. 116. Analysing ATiS <ul><li>PD Lead is underperforming
  117. 117. PD Team is not skilled well
  118. 118. Not Enough PD Capacity
  119. 119. PD Team does not Monitor BTS </li></ul>Copyright 2010 Petro Porchuk, Lohika Issues are staying in Open / In Progress status too long... PD Team is having problems
  120. 120. Analysing ATiS <ul><li>QA-PD Iteraction needs to be improved
  121. 121. Configuration Management should be Improved
  122. 122. PD doesn't Process Issues Flow Well </li></ul>Copyright 2010 Petro Porchuk, Lohika Issues are staying in Pending Build status too long... Configuration Management or Build Planning is Weak
  123. 123. Analysing ATiS <ul><li>QA Lead is underperforming
  124. 124. QA Team is not skilled well
  125. 125. Not Enough QA Capacity
  126. 126. QA Team does not Monitor BTS </li></ul>Copyright 2010 Petro Porchuk, Lohika Issues are staying in Resolved status too long... QA Team is having problems
  127. 127. Average Time in Status (Again) Tools : <ul><li>JIRA
  128. 128. Wiki / Confluence </li></ul>Helps to Identify Whether: <ul><li>QA Team Checks Issues In Time
  129. 129. PD Team Handles Issues In Time
  130. 130. PD Lead Reacts Quickly Assigning
  131. 131. QA Drops are not a Bottle Neck of the Process </li></ul>Copyright 2010 Petro Porchuk, Lohika
  132. 132. Time to First Response Tools : <ul><li>JIRA
  133. 133. Wiki / Confluence </li></ul><ul><li>Shows the Ability of the Team to React to the Incoming Issues Quickly </li></ul>Copyright 2010 Petro Porchuk, Lohika
  134. 134. Resolution Time Tools : <ul><li>JIRA
  135. 135. Wiki / Confluence </li></ul><ul><li>Shows the Average Time takes the Team to Resolve an Issue </li></ul>Copyright 2010 Petro Porchuk, Lohika
  136. 136. Average Age Tools : <ul><li>JIRA
  137. 137. Wiki / Confluence </li></ul><ul><li>Shows the Average Age of Issues to be Unresolved.
  138. 138. Consider, whether old Issues are getting Fixed or are put On Hold.
  139. 139. Should get lower or stay Constant </li></ul>Copyright 2010 Petro Porchuk, Lohika
  140. 140. Created vs Resolved Issues Tools : <ul><li>JIRA
  141. 141. Wiki / Confluence </li></ul><ul><li>Created Issues
  142. 142. Resolved Issues
  143. 143. Created vs Resolved Issues
  144. 144. Level of Code Quality
  145. 145. The Two Lines should Cross </li></ul>Copyright 2010 Petro Porchuk, Lohika
  146. 146. Reports Board <ul><li>Display Excel Sheets on WIKI {excel:file} </li></ul><ul><ul><li>Reporting Test Results
  147. 147. Daily Assignment Reports </li></ul></ul><ul><li>Display PowerPoint Files </li></ul><ul><ul><li>Show Test Approach/Strategy
  148. 148. Show Other Stuff </li></ul></ul>Copyright 2010 Petro Porchuk, Lohika
  149. 149. Feature Testing Report Tools : <ul><li>MS Excel / OpenOffice
  150. 150. Wiki / Confluence </li></ul><ul><li>Reflects Deliveries to QA (QA Drops)
  151. 151. Shows Statuses per Component
  152. 152. History Storage </li></ul>Copyright 2010 Petro Porchuk, Lohika
  153. 153. What Else? <ul><li>Components Testability Metrics
  154. 154. Metrics for Evaluating TC (complexity, etc)
  155. 155. Metrics for Calculating Test Costs
  156. 156. Metrics for Measuring Test Coverage
  157. 157. Metrics for Assessing Test Effectiveness </li></ul>Copyright 2010 Petro Porchuk, Lohika
  158. 158. Core PDLC Issues (What benefits gives you the QAD) <ul><li>( Solves Partially ) BAD Planning ( a fool with a tool is still a fool )
  159. 159. ( Solves a Lot ) BAD Communication
  160. 160. ( Solves ) BAD Tasks Distribution
  161. 161. ( Solves a Lot ) BAD Control
  162. 162. ( Solves ) Too Much Time WASTE for Reporting
  163. 163. ( Solves Partially ) People Motivation
  164. 164. ( Solves ) Continuous Customer Confidence Prompt
  165. 165. ( Solves a Lot ) BAD Project Risks Visibility
  166. 166. ( Solves Partially ) Underestimation </li></ul>V Copyright 2010 Petro Porchuk, Lohika
  167. 167. Thank you! ? [email_address] Copyright 2010 Petro Porchuk, Lohika

×