Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "EGI-InSPIRE:WP5 Project Metrics"

From EGIWiki
Jump to navigation Jump to search
 
(49 intermediate revisions by 6 users not shown)
Line 1: Line 1:
=== EGI SA2 Metrics  ===
{{Template:EGI-Inspire menubar}}
 
{{Template:Inspire_reports_menubar}}
{{TOC_right}}
 
 
= Current collection of quarterly metrics  =
 
The following table provides an overview of all collected metrics throughout the EGI-InSPIRE project.<br>
 
The running definition of the EGI-InSPIRE SA2 metrics is available [[InSPIRE-SA2:Metrics Definition|here]].
 
TODO: Update to current metrics definition!
 
{| cellspacing="0" cellpadding="5" style="border: 1px solid black;"
|- style="background: none repeat scroll 0% 0% darkgray;"
! style="border-bottom: 1px solid black;" | Metric ID
! style="border-bottom: 1px solid black;" | Metric
! style="border-bottom: 1px solid black; border-right: 1px solid black;" | Task
! style="border-bottom: 1px solid black;" | Q4
! style="border-bottom: 1px solid black;" | Q5
! style="border-bottom: 1px solid black;" | Q6
! style="border-bottom: 1px solid black;" | Q7
! style="border-bottom: 1px solid black;" | Q8
! style="border-bottom: 1px solid black;" | Q9
|-
| M.SA2-1
| Number of software components recorded in the UMD Roadmap
| style="border-right: 1px solid black;" | TSA2.1
| align="center" | 30
| align="center" | 30
| align="center" | 30
| align="center" | 30
| align="center" | 30
| align="center" |
|- style="background: none repeat scroll 0% 0% lightgray;"
| M.SA2-2
| UMD Roadmap Capabilities coverage with Quality Criteria
| style="border-right: 1px solid black;" | TSA2.2
| align="center" | 70% (18)
| align="center" | 85% (22)
| align="center" | 92% (25)
| align="center" | 100% (27)
| align="center" | 100% (27)
| align="center" |
|-
| M.SA2-3
| Number of software incidents found in production that result in changes to quality criteria
| style="border-right: 1px solid black;" | TSA2.2
| align="center" | 0
| align="center" | 0
| align="center" | 2
| align="center" | 2
| align="center" | 2
| align="center" |
|- style="background: none repeat scroll 0% 0% lightgray;"
| M.SA2-4
| Number of quality related issues that result in changes to quality criteria (internal metric!)<br>
| style="border-right: 1px solid black;" | TSA2.2
| align="center" | <br>
| align="center" | 27
| align="center" | 11
| align="center" | 10
| align="center" | 12
| align="center" |
|-
| M.SA2-5
| Number of new Product releases validated against defined criteria
| style="border-right: 1px solid black;" | TSA2.3
| align="center" | 3<br>
| align="center" | 41<br>
| align="center" | 29
| align="center" | 21
| align="center" | 24
| align="center" |
|- style="background: none repeat scroll 0% 0% lightgray;"
| M.SA2-6
| Mean time taken to validate a Product release
| style="border-right: 1px solid black;" | TSA2.3
| align="center" | 4h<br>
| align="center" | 21.03h<br>
| align="center" | 10.52h
| align="center" | 9.34h
| align="center" | 4.98h
|
|-
| M.SA2-7
| Number of Product releases failing validation
| style="border-right: 1px solid black;" | TSA2.3
| align="center" | 0<br>
| align="center" | 5<br>
| align="center" | 2
| align="center" | 1
| align="center" | 0
|
|- style="background: none repeat scroll 0% 0% lightgray;"
| M.SA2-8
| Number of new releases contributed into the Software Repository from all types of software providers
| style="border-right: 1px solid black;" | TSA2.4
| align="center" | 4<br>
| align="center" | 42<br>
| align="center" | 42<br>
| align="center" | 22<br>
| align="center" | 23<br>
|
|-
| M.SA2-9
| Number of unique visitors to the Software Repository
| style="border-right: 1px solid black;" | TSA2.4
| align="center" | 525<br>
| align="center" | 766
| align="center" | 1184
| align="center" | 1100
| align="center" | 1383
|
|- style="background: none repeat scroll 0% 0% lightgray;"
| M.SA2-10
| Number of unique visits to the Repository backend
| style="border-right: 1px solid black;" | TSA2.4
| align="center" | 1663<br>
| align="center" | 1801
| align="center" | 4556
| align="center" | 4009
| align="center" | 4315
|
|-
| M.SA2-11
| Number of tickets assigned to DMSU
| style="border-right: 1px solid black;" | TSA2.5
| align="center" | 198<br>
| align="center" | 218<br>
| align="center" | 183 <br>
| align="center" | 173 <br>
| align="center" | 212 <br>
|
|- style="background: none repeat scroll 0% 0% lightgray;"
| M.SA2-12
| Mean time to resolve DMSU tickets (Median in brackets)
| style="border-right: 1px solid black;" | TSA2.5
| align="center" | n/a<sup>1</sup><br>
| align="center" | 24d (4.2d)
| align="center" | 17.3d (11d)
| align="center" | 21.4d (5.1d)
| align="center" | 11.3d (1.9d)
|
|}
 
<sup>1</sup> Beginning with PQ4 this metric is not collected until appropriate reporting means in GGUS are implemented. (See for more details.)
 
<br>
 
= Historic metric collections =
 
== PQ1 - PQ3  ==
 
The following table provides historic metrics collected for project quarters one to three. With [https://documents.egi.eu/document/375 D5.3] the SA2 activity decided to change the metrics.


{| cellspacing="0" cellpadding="5" style="border: 1px solid black;"
{| cellspacing="0" cellpadding="5" style="border: 1px solid black;"
Line 8: Line 163:
! style="border-bottom: 1px solid black;" | Q1  
! style="border-bottom: 1px solid black;" | Q1  
! style="border-bottom: 1px solid black;" | Q2  
! style="border-bottom: 1px solid black;" | Q2  
! style="border-bottom: 1px solid black;" | Q3  
! style="border-bottom: 1px solid black;" | Q3
! style="border-bottom: 1px solid black;" | Q4
! style="border-bottom: 1px solid black;" | Q5
|-
|-
| M.SA2-1  
| M.SA2-1  
Line 17: Line 170:
| align="center" | 0  
| align="center" | 0  
| align="center" | 0  
| align="center" | 0  
| align="center" | 30  
| align="center" | 30
| align="center" | 30<br>
| align="center" | <br>
|- style="background: none repeat scroll 0% 0% lightgray;"
|- style="background: none repeat scroll 0% 0% lightgray;"
| M.SA2-2  
| M.SA2-2  
Line 26: Line 177:
| align="center" | 0  
| align="center" | 0  
| align="center" | 6  
| align="center" | 6  
| align="center" | 17  
| align="center" | 17
| align="center" | <br>
| align="center" | <br>
|-
|-
| M.SA2-3  
| M.SA2-3  
| Number of software incidents investigated in a post-mortem found in production that result in changes to quality criteria<sup>1</sup>
| Number of software incidents found in production that result in changes to quality criteria  
| style="border-right: 1px solid black;" | TSA2.2  
| style="border-right: 1px solid black;" | TSA2.2  
| align="center" | 0  
| align="center" | 0  
| align="center" | 1  
| align="center" | 1  
| align="center" | 0  
| align="center" | 0
| align="center" | <br>
| align="center" | <br>
|- style="background: none repeat scroll 0% 0% lightgray;"
|- style="background: none repeat scroll 0% 0% lightgray;"
| M.SA2-4  
| M.SA2-4  
| Number of new product releases validated against defined criteria  
| Number of new releases validated against defined criteria  
| style="border-right: 1px solid black;" | TSA2.3  
| style="border-right: 1px solid black;" | TSA2.3  
| align="center" | 0  
| align="center" | 0  
| align="center" | 1  
| align="center" | 1  
| align="center" | 1  
| align="center" | 1
| align="center" | <br>
| align="center" | <br>
|-
|-
| M.SA2-5  
| M.SA2-5  
| Mean time taken to validate a product release  
| Mean time taken to validate a release  
| style="border-right: 1px solid black;" | TSA2.3  
| style="border-right: 1px solid black;" | TSA2.3  
| align="center" | n/a  
| align="center" | n/a  
| align="center" | 4h  
| align="center" | 4h  
| align="center" | 8h  
| align="center" | 8h
| align="center" | <br>
| align="center" | <br>
|- style="background: none repeat scroll 0% 0% lightgray;"
|- style="background: none repeat scroll 0% 0% lightgray;"
| M.SA2-6  
| M.SA2-6  
Line 62: Line 205:
| align="center" | n/a  
| align="center" | n/a  
| align="center" | 0  
| align="center" | 0  
| align="center" | 0  
| align="center" | 0
| align="center" | <br>
| align="center" | <br>
|-
|-
| M.SA2-7  
| M.SA2-7  
Line 71: Line 212:
| align="center" | 0  
| align="center" | 0  
| align="center" | 1  
| align="center" | 1  
| align="center" | 3  
| align="center" | 3
| align="center" | 4<br>
| align="center" | <br>
|- style="background: none repeat scroll 0% 0% lightgray;"
|- style="background: none repeat scroll 0% 0% lightgray;"
| M.SA2-8  
| M.SA2-8  
Line 80: Line 219:
| align="center" | 0  
| align="center" | 0  
| align="center" | 507  
| align="center" | 507  
| align="center" | 412  
| align="center" | 412
| align="center" | 525<br>
| align="center" | <br>
|-
|-
| M.SA2-9  
| M.SA2-9  
| Number of unique visits to the Repository backend
| Number of releases downloaded from the Software Repository  
| style="border-right: 1px solid black;" | TSA2.4  
| style="border-right: 1px solid black;" | TSA2.4  
| align="center" | 0  
| align="center" | 0  
| align="center" | 0  
| align="center" | 0  
| align="center" | 0  
| align="center" | 0
| align="center" | 1663<br>
| align="center" | <br>
|- style="background: none repeat scroll 0% 0% lightgray;"
|- style="background: none repeat scroll 0% 0% lightgray;"
| M.SA2-10  
| M.SA2-10  
Line 98: Line 233:
| align="center" | 0  
| align="center" | 0  
| align="center" | 8  
| align="center" | 8  
| align="center" | 144  
| align="center" | 144
| align="center" | <br>
| align="center" | <br>
|-
|-
| M.SA2-11  
| M.SA2-11  
| Mean time to resolve DMSU tickets<sup>2</sup>
| Mean time to resolve DMSU tickets  
| style="border-right: 1px solid black;" | TSA2.5  
| style="border-right: 1px solid black;" | TSA2.5  
| align="center" | 3d  
| align="center" | 3d  
| align="center" | 2d  
| align="center" | 2d  
| align="center" | n/a  
| align="center" | n/a
| align="center" | <br>
| align="center" | <br>
|}
|}
<sup>1</sup> This metric was narrowed down in scope beginning with collection for PQ4.
<sup>2</sup> beginning with PQ4 this metric is not collected until appropriate reporting means in GGUS are implemented.

Latest revision as of 19:26, 9 January 2015

EGI Inspire Main page


Inspire reports menu: Home SA1 weekly Reports SA1 Task QR Reports NGI QR Reports NGI QR User support Reports




Current collection of quarterly metrics

The following table provides an overview of all collected metrics throughout the EGI-InSPIRE project.

The running definition of the EGI-InSPIRE SA2 metrics is available here.

TODO: Update to current metrics definition!

Metric ID Metric Task Q4 Q5 Q6 Q7 Q8 Q9
M.SA2-1 Number of software components recorded in the UMD Roadmap TSA2.1 30 30 30 30 30
M.SA2-2 UMD Roadmap Capabilities coverage with Quality Criteria TSA2.2 70% (18) 85% (22) 92% (25) 100% (27) 100% (27)
M.SA2-3 Number of software incidents found in production that result in changes to quality criteria TSA2.2 0 0 2 2 2
M.SA2-4 Number of quality related issues that result in changes to quality criteria (internal metric!)
TSA2.2
27 11 10 12
M.SA2-5 Number of new Product releases validated against defined criteria TSA2.3 3
41
29 21 24
M.SA2-6 Mean time taken to validate a Product release TSA2.3 4h
21.03h
10.52h 9.34h 4.98h
M.SA2-7 Number of Product releases failing validation TSA2.3 0
5
2 1 0
M.SA2-8 Number of new releases contributed into the Software Repository from all types of software providers TSA2.4 4
42
42
22
23
M.SA2-9 Number of unique visitors to the Software Repository TSA2.4 525
766 1184 1100 1383
M.SA2-10 Number of unique visits to the Repository backend TSA2.4 1663
1801 4556 4009 4315
M.SA2-11 Number of tickets assigned to DMSU TSA2.5 198
218
183
173
212
M.SA2-12 Mean time to resolve DMSU tickets (Median in brackets) TSA2.5 n/a1
24d (4.2d) 17.3d (11d) 21.4d (5.1d) 11.3d (1.9d)

1 Beginning with PQ4 this metric is not collected until appropriate reporting means in GGUS are implemented. (See for more details.)


Historic metric collections

PQ1 - PQ3

The following table provides historic metrics collected for project quarters one to three. With D5.3 the SA2 activity decided to change the metrics.

Metric ID Metric Task Q1 Q2 Q3
M.SA2-1 Number of software components recorded in the UMD Roadmap TSA2.1 0 0 30
M.SA2-2 Number of UMD Roadmap Capabilities defined through validation criteria TSA2.2 0 6 17
M.SA2-3 Number of software incidents found in production that result in changes to quality criteria TSA2.2 0 1 0
M.SA2-4 Number of new releases validated against defined criteria TSA2.3 0 1 1
M.SA2-5 Mean time taken to validate a release TSA2.3 n/a 4h 8h
M.SA2-6 Number of releases failing validation TSA2.3 n/a 0 0
M.SA2-7 Number of new releases contributed into the Software Repository from all types of software providers TSA2.4 0 1 3
M.SA2-8 Number of unique visitors to the Software Repository TSA2.4 0 507 412
M.SA2-9 Number of releases downloaded from the Software Repository TSA2.4 0 0 0
M.SA2-10 Number of tickets assigned to DMSU TSA2.5 0 8 144
M.SA2-11 Mean time to resolve DMSU tickets TSA2.5 3d 2d n/a