Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Tabs Container
titleValidation Queries By Report
directionhorizontal


Tabs Page
titleFeatures in Status on PI Start Dates

Validation Date: 8/15/2022


Validation Notes:

  1. 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
iQiesPI3PI4 PI5PI6PI7
Funnel160/156179/177175/173199/198299/300
Feature Definition1/13/35/56/64/4
Feature Refinement3/35/54/43/31/1
Feature Deep Dive8/811/114/418/1810/10
Story Definition84/8592/9254/5468/6852/52
PI Ready68/6859/59 84/8480/8082/82
Implementing57/5668/6869/6950/5050/50



EQRSPI 14PI 15PI 16PI 17PI 18
Funnel21/21125/125107/10784/84100/100
Analyzing (SAFe)0/00/03/33/33/3
Refining16/1613/1314/13*8/86/5*
Ready For PI0/09/917/1721/2225/25
Implementing5/512/1225/2529/2936/39


Validation Date : 8/11/2022

iQiesPI3PI4 PI5PI6PI7
Funnel160/156179/177175/173199/198299/302
Feature Definition1/13/35/56/64/4
Feature Refinement3/35/54/43/31/1
Feature Deep Dive8/811/114/418/1817/10
Story Definition84/8592/9254/7068/7352/55*
PI Ready68/6859/6584/9980/8282/88
Implementing57/5968/7269/7550/5050/50


EQRSPI 14PI 15PI 16PI 17PI 18
Funnel21/21125/125107/10784/84100/102
Analyzing (SAFe)0/00/03/33/33/3
Refining16/1613/1314/13*8/86/5*
Ready For PI0/09/917/1721/2225/27*
Implementing5/512/1225/2529/3336/38*



Tabs Page
titleCurrent Program Backlog Composition


TypesiQIESEQRS
Infrastructure Enabler1/10/0
Architectural Enabler1/10/0
Exploration Enabler1/019/19
Compliance Enabler2/20/0
Enabler91/908/8
Features499/426130/62



Tabs Page
titleFeatures Started and Closed per PI

Report Name: Features Started and Closed per PI

Legend: EazyBI count/JQL count

iQiesPI3PI4 PI5PI6PI7
Implementing104/104129/132105/122199/19873/83
Done196/196132/13593/96106/11316/16


Project = "iQIES Program Board "  AND issuetype = 10000 AND Status changed to Done during (2022-01-19, 2022-04-19)  ORDER BY key DESC


EQRSPI 14PI 15PI 16PI 17PI 18PI 19
Implementing16/1630/3036/3627/2918/2116/16
Done10/1025/2532/3227/3127/2919/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 : 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 on the defined PI Start and End dates, because it was only looking for items in between 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 the BEFORE and AFTER operators rather than 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:  [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")


iQiesPI3PI4 PI5PI6PI7
Implementing104/104129/132123/122123/11383/85
Done196/196132/13597/97115/11516/17*


EQRSPI 14PI 15PI 16PI 17PI 18PI 19
Implementing16/1630/3036/3632/3221/2116/16
Done10/1025/2532/3233/3233/2919/19