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