2020-09-08 Meeting notes
Date
Attendees
@Dwayne Swigert
Theodor Tolstoy (One-Group.se)
Goals
Discussion items
| Time | Item | Who | Notes |
|---|---|---|---|
| Feedback from Cap Plan Team on new ranking system | Holly Mistlebauer | The Cap Plan Team agreed with the new ranking plan, but prefer that we use R1-R5 (rather than P1-P5). They also would like to keep NOT NEEDED, but we can use R5 for that. R1=Go live R2=Can wait a quarter R3=Can wait for FYRO R4=Can wait a year R5=NOT Needed Comment from Tom - FYRO issues can't slip. From Slack discussions, many things were ranked "can wait for FYRO" but had nothing to do with FYRO. We only found a few features connected to FYRO. From a cursory review of the filtered set, only the following seem to be related to the FYRO functions: UXPROD-772 Rollover Encumbrances into the next Fiscal Year UXPROD-203 Close/freeze budgets upon rollover into new fiscal year UXPROD-201 Rollover the ledgers funds/budgets into a new Fiscal year (Creating new budgets for all funds at one time) The best way to move forward would be to identify all FYRO Features and have everyone rank them R1 so work could begin in Iris. ACTION: Holly will convert the current rankings to R1-R5. The Implementers need to define more clearly the R1-R5. New features may come up that we need to rank without clear definitions but we think we can handle that. | |
| New ranking definitions | R1 = Urgent - this feature is needed immediately R2 = High - this feature is needed ASAP, at least in next release R3 = Medium - workaround is deficient, needs to be fixed R4 = Low - needed, but we can work around for a while R5 = Not needed This is the first draft of new definitions, will finalize next week |