Backlog Grooming Sprint 117

Dates:  -  


Team Parrot Sprint

Sprint Goal: Figure out the slowest Reference Data endpoints and start fixing them


Tickets:

  • Use OLMIS-3623 - Getting issue details... STATUS as a base, but we may need to add tickets to create more profiling, enable some perf tests etc.

Future:

  • Type your task here, using "@" to assign to a user and "//" to select a due date

Team Parrot to use 20% of their capacity to fix the following prioritized bugs:

key summary type priority status labels
Loading...
Refresh

Team Parrot to use 20% of their capacity to fix the following prioritized Tech Debt tickets:

key summary type priority status labels
Loading...
Refresh


Team Ona Gap

Sprint Goal: 


Tickets:

  • Type your task here, using "@" to assign to a user and "//" to select a due date

Future Ideas:



Team JSI Gap

Sprint Goal: Finish-up the remaining stories for shipment file; Scope the UI for meta data upload; Quick wins


Tickets:

Future:

  • Type your task here, using "@" to assign to a user and "//" to select a due date

Team Mind the Gap

Sprint Goal: Continue splitting requisitions for multiple supply partners & begin the notifications design

Capacity: Please add # of days you are working this sprint

Planning poker for sizing:https://play.planningpoker.com/play/game/rQIzyuzYuyoU6yDwClr3Kdt6jYr1QFkr

Tickets:

Priority 1: Finish Splitting requisitions for multiple supply partners

  • OLMIS-5950 - Getting issue details... STATUS  Meeting is scheduled on Wednesday (by Sam)
  • OLMIS-5909 - Getting issue details... STATUS  (I would say this blocks most of the UI tickets below)
  • OLMIS-5724 - Getting issue details... STATUS
  • OLMIS-5725 - Getting issue details... STATUS
  • OLMIS-5837 - Getting issue details... STATUS


Priority 2: Customizable notifications feature

Nikodem Graczewski (Unlicensed) will add tickets based on the answers from spikes in Sprint 116.




Priority 3 Tech Debt/Other work:

  • OLMIS-5544 - Getting issue details... STATUS
  • Should we include these as part of notifications related work? 
    • OLMIS-3477 - Getting issue details... STATUS (deals with ensuring notifications that are queued are saved even if the microservice goes down; don't think this is a high enough priority to work on, unless there isn't anything else)
    • OLMIS-3474 - Getting issue details... STATUS (deals with improving performance of stockout notifications)

Future:

  • Review MTG scope planning