...
Formula / Base
Live Issues = Total number of open tickets at end of the respective month (From Freshdesk Data)
Defect Leakage - Captured through QA Data set = Number of defects reported by end-users or customers (from Fresh Desk) X 100
Total number of defects found by QA (From JIRA)Issues Injected Per Story Points = (Total number of Live Issues Reported for the Month + Total number of defects reported by BA+QA for the Month (JIRA)
Story points developed for the month and released
Development Velocity = Total Dev days available for the month * Total Story Points developed and released
Total number of Dev Days worked Number of Developers
Story Point Calculation - 2Hrs of work = 1 Story Point
...
Product | Live Issues (<10) As of EOD, March 31, 2024. | Defect Leakage Range: 5% - 15% | Issues Injected Per Story Points Range: 1.5% - 5% | Development Velocity Average Story Points developed by a Developer | Notes | ||||
|---|---|---|---|---|---|---|---|---|---|
Incident | 29 | 53.25% | 0.55% | 58.21 | The teams started equating 1 story points to 2 hours from March onwards from the earlier 8 hours per story points. | ||||
Compliance | 11 | N/A | N/A | N/A | No development in the month | ||||
SRT | 7 | N/A | N/A | N/A | No development in the month | ||||
Risk | 48 | 64.17% | 0.31% | 59.86 | The teams started equating 1 story points to 2 hours from March onwards from the earlier 8 hours per story points. | ||||
Audit | 13 | N/A | N/A | N/A | No development in the month | ||||
Mobile | 1 | 0% | 1.38% | 23.30 | Strategy | 13 | 27.78% | 0.28% | 56.93 |
...
A. In our development velocity metrics, you may notice that the figures often show 50+ story points. This is because we are equating 2 hours to 1 story point. Consequently, the number of story points developed by a developer may appear higher based on the actual number of days worked.
We've noticed a lower velocity, partly due to a significant number of stories spilling over into subsequent sprints. We consider story points completed only when the status is changed to "Sprint Review." We've identified several root causes for these spillages and are actively collaborating with the |
...
team to address them. | |||||
Strategy | 13 | 27.78% | 0.28% | 56.93 | The teams started equating 1 story points to 2 hours from March onwards from the earlier 8 hours per story points. |
February 2024
Date Range: to
...
Product | Live Issues (<10) As of EOD 29th February 2024. | Defect Leakage Range: 5% - 15% | Issues Injected Per Story Points Range: 1.5% - 5% | Development Velocity Average Story Points developed by a Developer | Notes |
|---|---|---|---|---|---|
Incident | 27 | 1.02% | 3.08% | 24.70 | |
Compliance | 7 | N/A | N/A | N/A | No development in the month |
SRT | 8 | N/A | N/A | N/A | No development in the month |
Risk | 57 | 2.96% | 1.10% | 24.53 | |
Audit | 13 | N/A | N/A | N/A | No development in the month |
Mobile | 0 | 0.30% | 1.59% | 23.89 | |
Strategy | 13 | 1.09% | 1.60% | 9.39 | Sprint started on February 19, 2024 and dependent on other product basic developments |
...
A. February was primarily dedicated to FR deployments, resulting in minimal development activities during the month.
The Strategy Team commenced its development efforts on February 19, 2024, following the receipt of dependent deliveries required to initiate initial development. As a result, the number of completed story points during this period is minimal. |
| Info |
|---|
Month of February was primarily dedicated to FR deployments, resulting in minimal development activities during the month. |
January 2024
Date Range: to
...