LACE (CCSQ Lean Agile Center of Excellence)

Page tree

Versions Compared

Old Version 16

changes.mady.by.user Marc Santini

Saved on

compared with

New Version 17

changes.mady.by.user Marc Santini

Saved on

Key

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


General:

  • Backlog comp charts relies on tags, not work item types
  • Most projects have inactive teams. Can we create new project categories so we can avoid custom measures like "EQRS ART Teams"
  • How can we have RTEs input Jira data so PI measures are not a LACE support request?
    • create an epic with Start/End dates?

    • EQRS uses a release per PI. Can we use it? What are other programs doing?

  • Research how to make the Cumulative Flow time boundary 'last 12 months' instead of by PI
Horizontal Navigation Bar


Horizontal Navigation Bar Page
titleGlobal Issues


#Jira KeySeverityChartIssue SummaryNotes
1LACE-3168HighFeatures started and closed by PIClosed Issues  count w/in PI are wrongClosed Issues measure calculates cumulative results, rather than closures w/in the PI date boundaries
2
HighAll Reports using PI date measuresminor differences in issue countsEazyBi Standard measures results differ from Jira Queries
3
MediumFeatures in Status by PITime Member Lags by one periodWhen Using the PI Start Date Measures For Open Issues measure(and presumably all other counts), the implementation numbers are correct but show the value from the previous PI for each PI on the chart
4
MediumAll Reports using PI date measuresEliminate Custom Start date and PI Measures

Identify a solution for getting PI Start/End date from Jira and eliminate program specific custom measures. 

EQRS creates a releases for each PI.(fix version Start date measure) Need to find out what other programs are doing 

5
HighAll

Programs have inactive teams

Inactive teams forces us to select individual team projects, requiring maintenance (removal or addition of projects) to the data import to maintain accurate issue counts for charts aggregating data from all program teams. Project Categories could be used or Project Labels (if they exist) 
6
LowCumulative FlowTime Period changes with PI selectionShould show a 12 month window. Because time is in Rows, its taking the value from the time dimension current member selection. We cannot use the 12 month time dimension member because PI selection is a common page element. We need a custom measure (in measures dimension) to fix 12 months
7
MediumFeatures Started and Closed by PIRemoved Issue Histories Closed LineNot sure how, but the other two lines are accurate based on Jira queries, we just need to squash the red line










































































Horizontal Navigation Bar Page
titleEQRS Dashboard Issues


#Jira Issue IDSeverityIssue SummaryChartNotes



Add PI 18 to Dashboard
PI planning for PI 18 is right around the corner. Measure in time dimension needs to be added for all reports using PI start date


































































































Horizontal Navigation Bar Page
titleiQies Dashboard


ProgramIssue SummaryJira KeyNotes
EQRSsparklines on features started and closed incorrectLACE-3168need to re-identify which sparklines are correct
EQRSminor differences in issue counts
PI measures use dateBetween, JQL uses during. May need to expand PI measures by one day on either side






































































...