Activity |
1: Add the Program and Program Projects to the EazyBI Data
| Figure 1 |
Activity 2: Ensure the correct project teams are associated with the category |
Validate that |
all and only the active teams in the program are associated with the project category.
|
|
|
|
| |
Activity 3: Update |
the Project Switch Measure
Generate( | Figure 2 |
Activity 4: Add Custom Members to the Time Dimension for the PI Based Reports
|
|
|
|
|
| ||
Activity 5: Add the new PI time dimensions to the reports
| Current reports that use PI's
|
| |
Activity 6: Add Program specific feature statuses to user defined measures and custom members
| Figure 6 |
Activity |
7: Add "Complete" statuses to Jira Data import
|
|
Activity # | Suggested or Potential Workaround(s) | Teams Needed | Feasibility Confidence | Expected Feature Size/Effort |
---|---|---|---|---|
1 | Create "Program Dashboard" flag in Jira. We can add this as a dimension or custom field for the import, and then update some measures to pull programs with the dashboard flag. If we can add properties to the project category, we should be able automate this in the import. Need to discuss with Atlassian to understand feasibility better | Atlassian, LACE | 50% | medium |
2 | Create a policy for RTEs or Program Managers to submit requests to remove and add teams as they are created or decommissioned |
Program Support, Atlassian | 100% | low effort, but cyclical and prone to human error | |
2 | Use the "Active Program" flag in Jira at the project level and add it as a property or dimension so that inactive projects and project data are not imported |
Atlassian, Lace | 70% | Medium | |
2 | Let inactive |
teams screw up data, and let program leaders face the consequences. This would only work if there were work item standards in place and an expectation that the dashboards be accurate | Program Leaders | 30% | Free | |
3 | Use the Release Version to include Program Key, PI Boundaries, PI Numbers, start and end dates. Create measures in EazyBI and update PI based reports This would require RTEs\Program leaders to add the correct information for existing release versions and create future release versions correctly | Atlassian, LACE. RTEs, Program leaders | 99% | Medium |
4 | Transition to release versions as outlined above. Write measure to pull the right set of release versions into report based on time. We would need to think carefully about version names | LACE, RTEs or Program Leaders, possibly Atlassian | 90% | Medium |
5 | Identify and add all program level statuses in use and add them to the status based reports. Dashboards should be backwards compatible, but reports may need some finessing to keep past and present data analogous | LACE, Atlassian, RTEs or Program Leaders | 90% | Small |
6 | Proactively all "Post Dev" statuses to the done status group in the import. Customization of Jira statuses would have to stop. Risk that some issues would be stripped out of the report to a negative effect | LACE, Atlassian | 100% | Small |