Backlog Grooming Sprint 14

Fulfillment (API and UI)

...once the fulfillment service split is complete, then:

OLMIS-1369 - Getting issue details... STATUS

OLMIS-1319 - Getting issue details... STATUS

OLMIS-398 - Getting issue details... STATUS (cleaned up based on what has been done already; this ticket is more like an Epic—we won't assign this to SolDevelo, but instead keep it for Team ILL or keep in the backlog to track when all its pieces are done)

OLMIS-1385 - Getting issue details... STATUS (task related to OLMIS-398)

OLMIS-1386 - Getting issue details... STATUS (task related to OLMIS-398)

OLMIS-1381 - Getting issue details... STATUS (split out from OLMIS-1319)

Requisitions (API and UI)

These items are mostly from the Requisition Improvements epic and Requisition UI epic. For this sprint, we aren't planning a lot of the Advanced Requisition Template 3.0 epic (see its section under WAIT below).

Bugs:

OLMIS-1157 - Getting issue details... STATUS OLMIS-1158 - Getting issue details... STATUS OLMIS-1178 - Getting issue details... STATUS OLMIS-1360 - Getting issue details... STATUS

Refactoring:

OLMIS-1100 - Getting issue details... STATUS OLMIS-1101 - Getting issue details... STATUS (Mary Jo strongly encourages us to move ahead on the OOAD refactoring, and these 2 are a good first step; these 2 overlap each other partly, so they should be done by the same person/people)

Tasks and Stories:

OLMIS-1315 - Getting issue details... STATUS ~~(Brandon Bowersox-Johnson and Nick need to fill out the API and UI sub-tasks)~~ DONE

OLMIS-1334 - Getting issue details... STATUS (note this is blocked by 1332 which Team ILL plans to put in Sprint 14 too)

OLMIS-218 - Getting issue details... STATUS ~~(Brandon Bowersox-Johnson and Nick need to create API and UI sub-tasks and provide details in them--see Demo server v2 where ART skipping is enabled; maybe wait; Nick, the UI sub-tasks needs info)~~ DONE

OLMIS-1227 - Getting issue details... STATUS

OLMIS-1233 - Getting issue details... STATUS (UI)

OLMIS-1088 - Getting issue details... STATUS (UI)

OLMIS-1301 - Getting issue details... STATUS (UI)

UI Specific Tickets

OLMIS-1122 - Getting issue details... STATUS

OLMIS-1129 - Getting issue details... STATUS

OLMIS-1349 - Getting issue details... STATUS

Product Ownership & Architecture (Team ILL)

OLMIS-1332 - Getting issue details... STATUS (Reference Data - Team ILL should do)

OLMIS-1026 - Getting issue details... STATUS (ILL)

OLMIS-1281 - Getting issue details... STATUS (ILL)

OLMIS-1405 - Getting issue details... STATUS (divide 1405 into two parts: "ideation workshop for UI extension" and "discussion about UI extension points")

OLMIS-1407 - Getting issue details... STATUS (ILL - Josh Zamor I added this)

OLMIS-987 - Getting issue details... STATUS (Added for Ben and Jake; they will huddle Monday)

OLMIS-1388 - Getting issue details... STATUS (ILL) (Convert this to its own task, not a sub-task of 987)

OLMIS-1279 - Getting issue details... STATUS (TOP/AYIC)

OLMIS-1288 - Getting issue details... STATUS (TOP/AYIC)

OLMIS-1283 - Getting issue details... STATUS (TOP/AYIC)

OLMIS-1336 - Getting issue details... STATUS (TOP/AYIC)

WAIT on the following:

Requisition Template 3.0/Advanced Template:

OLMIS-1134 - Getting issue details... STATUS OLMIS-933 - Getting issue details... STATUS OLMIS-1147 - Getting issue details... STATUS

Reference UI:

OLMIS-535 - Getting issue details... STATUS (for Team ILL/Nick) This ticket should be split into a small epic with smaller items. During Sprint 14, Nick will conduct this spike/audit to define this work.

The following should be done later before starting to implement stock management:

OLMIS-1025 - Getting issue details... STATUS (this UI split might wait until Sprint 15-16)

OLMIS-1072 - Getting issue details... STATUS (for Team ILL/Nick)

OLMIS-1189 - Getting issue details... STATUS (UI - Nick please provide mock-up/clean-up; discuss with Nick and Mary Jo)

NEW: Design Sprint for displaying component state (this needs to become a ticket)

Requisition Improvements:

Team ILL definitely needs to work on definition/scoping for OLMIS-536 - Getting issue details... STATUS OLMIS-1009 - Getting issue details... STATUS OLMIS-1063 - Getting issue details... STATUS

Platform:

OLMIS-1409 - Getting issue details... STATUS (Team ILL)

OLMIS-1102 - Getting issue details... STATUS (added because Mary Jo really wants to get this moving ahead; Team ILL needs to spike on definition/scoping of it first)

OLMIS-1389 - Getting issue details... STATUS (Team ILL)

Budgeting Feature:

View Budgeting Feature Epic in Backlog

Grooming Process

Mary Jo Kochendorfer (Deactivated), Sprint 14 is a challenge because the sprint starts while Team ILL is away on Thanksgiving holiday and Pawel Gesek is out for a week. So we are really trying to get ahead at cleaning up tickets. Also, last sprint having all the tables on the grooming page made it very difficult to use: it wasn't easy to re-order those tables, nor could we easily add a remove an item (without finding the right tags to apply) and we could not add notes next to each ticket. So for Sprint 14 we have started building this page by simply using links to tickets and adding notes. We are also using the Backlog view in JIRA to drag tickets into priority order. After the backlog is in order, we are pulling the top few that we feel are achievable during Sprint 14 onto this page and adding notes. We have assigned people here to clean up each section of this before Thursday's Backlog Grooming WebEx with SolDevelo.