Page Comparison

Capacity Planning

INSTRUCTIONS

Entering UXPROD Issues for Reporting Clusters:

• The po-mvp label needs to be added to all issues that are to be included in the MVP ("po-mvp" = Q4 2019 = January 1, 2020); "Go Live" issues should be targeted for the January release date to allow for 6 months of testing prior to a given institution actually implementing FOLIO as their LMS in Summer 2020
• Features need to have the PO Rank field assigned by Nassib; this field ranking must be unique within Epic; Ranking is lowest (0) to highest (120)
• For Front-End Estimate and Back-End Estimate, all of the features must have a tee-shirt size estimate assigned to them; biggest T-shirt size, XXL, is 30 days; issues bigger than  30 days must be broken into smaller components
• All issues are have Developer set to "reporting Reporting LDP" as developers
• All issues must have the Epic link populated
• Reporting Cluster UXPROD issues need to
  • be linked to the Reporting: LDP Reports Epic, UXPROD-1319
  • be linked as "related to" to all the REP-XXX issues associated with that cluster
  • include the labels "cluster" and "reporting" 
  • be assigned to Nassib Nassar

NOTES

Clusters:

How to organize clustering in JIRA?

...

• Report Queries - lists all report queries
  • RQ 123 (task)
  • RQ 345 (task)
  • etc
• Report Data Models
  • RDM 333 (tasks)
  • RDM 444 (tasks)

-----

EPICs:

UXPROD-1128 - LDP Alpha 1 - July 2020 (rank = go live)

...

UXPROD-1882 - LDP Beta - April 2021 (no ranking)

UXPROD-1901 - LDP 1.0 - July 2021 (rank = up to a year after go live)

Blockers:

UXPROD-1438: Process for tracking data-related API schema changes

...