Tabs Page |
---|
title | Features in Status on PI Start Dates |
---|
| Validation Date: 8/15/2022
Validation Notes: - Issues with status changes to implementing were not being caught because the earlier status was being returned by the validation query. Changing the time from (YYYY-M(M)-D(D)) to ('YYYY-M(M)-D(D) HH:MM'), with "HH:MM" being "23:59" catches the status at 11:59 PM. This brought all counts well under the "Accurate" STD category
iQies | PI3 | PI4 | PI5 | PI6 | PI7 |
---|
Funnel | 160/156 | 179/177 | 175/173 | 199/198 | 299/300 | Feature Definition | 1/1 | 3/3 | 5/5 | 6/6 | 4/4 | Feature Refinement | 3/3 | 5/5 | 4/4 | 3/3 | 1/1 | Feature Deep Dive | 8/8 | 11/11 | 4/4 | 18/18 | 10/10 | Story Definition | 84/85 | 92/92 | 54/54 | 68/68 | 52/52 | PI Ready | 68/68 | 59/59 | 84/84 | 80/80 | 82/82 | Implementing | 57/56 | 68/68 | 69/69 | 50/50 | 50/50 |
EQRS | PI 14 | PI 15 | PI 16 | PI 17 | PI 18 |
---|
Funnel | 21/21 | 125/125 | 107/107 | 84/84 | 100/100 | Analyzing (SAFe) | 0/0 | 0/0 | 3/3 | 3/3 | 3/3 | Refining | 16/16 | 13/13 | 14/13* | 8/8 | 6/5* | Ready For PI | 0/0 | 9/9 | 17/17 | 21/22 | 25/25 | Implementing | 5/5 | 12/12 | 25/25 | 29/29 | 36/39 |
Validation Date : 8/11/2022 iQies | PI3 | PI4 | PI5 | PI6 | PI7 |
---|
Funnel | 160/156 | 179/177 | 175/173 | 199/198 | 299/302 | Feature Definition | 1/1 | 3/3 | 5/5 | 6/6 | 4/4 | Feature Refinement | 3/3 | 5/5 | 4/4 | 3/3 | 1/1 | Feature Deep Dive | 8/8 | 11/11 | 4/4 | 18/18 | 17/10 | Story Definition | 84/85 | 92/92 | 54/70 | 68/73 | 52/55* | PI Ready | 68/68 | 59/65 | 84/99 | 80/82 | 82/88 | Implementing | 57/59 | 68/72 | 69/75 | 50/50 | 50/50 |
EQRS | PI 14 | PI 15 | PI 16 | PI 17 | PI 18 |
---|
Funnel | 21/21 | 125/125 | 107/107 | 84/84 | 100/102 | Analyzing (SAFe) | 0/0 | 0/0 | 3/3 | 3/3 | 3/3 | Refining | 16/16 | 13/13 | 14/13* | 8/8 | 6/5* | Ready For PI | 0/0 | 9/9 | 17/17 | 21/22 | 25/27* | Implementing | 5/5 | 12/12 | 25/25 | 29/33 | 36/38* |
|
Tabs Page |
---|
title | Current Program Backlog Composition |
---|
|
Types | iQIES | EQRS |
---|
Infrastructure Enabler | 1/1 | 0/0 | Architectural Enabler | 1/1 | 0/0 | Exploration Enabler | 1/0 | 19/19 | Compliance Enabler | 2/2 | 0/0 | Enabler | 91/90 | 8/8 | Features | 499/426 | 130/62 |
|
Tabs Page |
---|
title | Features Started and Closed per PI |
---|
| Report Name: Features Started and Closed per PI Legend: EazyBI count/JQL count | iQies | PI3 | PI4 | PI5 | PI6 | PI7 |
---|
Implementing | 104/104 | 129/132 | 105/122 | 199/198 | 73/83 | Done | 196/196 | 132/135 | 93/96 | 106/113 | 16/16 | Project = "iQIES Program Board " AND issuetype = 10000 AND Status changed to Done during (2022-01-19, 2022-04-19) ORDER BY key DESC EQRS | PI 14 | PI 15 | PI 16 | PI 17 | PI 18 | PI 19 |
---|
Implementing | 16/16 | 30/30 | 36/36 | 27/29 | 18/21 | 16/16 | Done | 10/10 | 25/25 | 32/32 | 27/31 | 27/29 | 19/19 |
Project = " End-Stage Renal Disease Quality Reporting System" AND issuetype = 10000 AND Status changed to Done during (2021-04-04, 2021-07-20) --Update status and dates of PI Validation Date : Validation Date : 8/17/2022 Because The eazybi measure was using dateBetween with the actual PI start and end dates, it was not picking up items changed to the Implementing or Done statuses statuses on the the defined PI Start and End dates, because it was only looking for items items in between those those dates, not including them I updated the query to check After the the last minute of the day before the PI, and Before the first minute of the day following the PI. I updated the Eazybi measure and then changed the Jira query to use use the BEFORE and AFTER operators rather than the the DURING and used matching timestamps in both the measure and the query. I suspect that the DURING operator in Jira is not as high resolution as EazyBi's Datebetween function. Items marked with an asterisk are below the STD threshold, but the low issue count skews the severity of deviation percentage, so they get marked green anyways UpdatedDateBetween function:
I will create two stories to investigate the anomalous counts for iQIES PI 6 implementing, and EQRS PI 18 Done Updated DateBetween function: [Time].[Day].DateMembersBetween('Jan 18 2022 23:59', 'Apr 13 2022 00:01')
Updated Query: Project = EQRS AND issuetype = 10000 AND Status changed to Done AFTER ("2022-01-19 00:01") AND Status changed to Done BEFORE ("2022-04-13 00:01")iQies | PI3 | PI4 | PI5 | PI6 | PI7 |
---|
Implementing | 104/104 | 129/132 | 123/122 | 123/113 | 83/85 | Done | 196/196 | 132/135 | 97/97 | 115/115 | 16/17* |
EQRS | PI 14 | PI 15 | PI 16 | PI 17 | PI 18 | PI 19 |
---|
Implementing | 16/16 | 30/30 | 36/36 | 32/32 | 21/21 | 16/16 | Done | 10/10 | 25/25 | 32/32 | 33/32 | 33/29 | 19/19 |
Validation Date : 8/16/2022 iQies | PI3 | PI4 | PI5 | PI6 | PI7 |
---|
Implementing | 104/104 | 129/132 | 105/122 | 199/198 | 73/83 | Done | 196/196 | 132/135 | 93/96 | 106/113 | 16/16 |
Project = "iQIES Program Board " AND issuetype = 10000 AND Status changed to Done during (2022-01-19, 2022-04-19) ORDER BY key DESC
EQRS | PI 14 | PI 15 | PI 16 | PI 17 | PI 18 | PI 19 |
---|
Implementing | 16/16 | 30/30 | 36/36 | 27/29 | 18/21 | 16/16 | Done | 10/10 | 25/25 | 32/32 | 27/31 | 27/29 | 19/19 |
Project = " End-Stage Renal Disease Quality Reporting System" AND issuetype = 10000 AND Status changed to Done during (2021-04-04, 2021-07-20) --Update status and dates of PI
|