/
Backlog Grooming Sprint 117

Backlog Grooming Sprint 117

Feb 01, 2019

Dates: Jan 17, 2019 - Jan 30, 2019 

 

Team Parrot Sprint

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

 

Tickets:

Use https://openlmis.atlassian.net/browse/OLMIS-3623 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
Refresh

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

key summary type priority status labels
Refresh

@Sebastian Brudziński to add Tech Debt backlog here
Regression testing cycle as needed (@Joanna Bebak (Deactivated))

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

  • @Sam Im (Deactivated) - 10 days

  • @Chongsun Ahn (Unlicensed)

  • @Nikodem Graczewski (Unlicensed)

  • @Łukasz Lewczyński (Deactivated) - 10 days

  • @Joanna Szymańska (Deactivated) - 8 days

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

Tickets:

Priority 1: Finish Splitting requisitions for multiple supply partners

https://openlmis.atlassian.net/browse/OLMIS-5950 Meeting is scheduled on Wednesday (by Sam)
https://openlmis.atlassian.net/browse/OLMIS-5909 (I would say this blocks most of the UI tickets below)

 

Priority 2: Customizable notifications feature

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

POC for consolidating notifications with 2 or 3 options
SMS channel meeting will be scheduled by @Nikodem Graczewski (Unlicensed)

 

 

 

Priority 3 Tech Debt/Other work:

Should we include these as part of notifications related work? 
https://openlmis.atlassian.net/browse/OLMIS-3477 (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)

https://openlmis.atlassian.net/browse/OLMIS-3474 (deals with improving performance of stockout notifications)

Future:

Review MTG scope planning

 

OpenLMIS: the global initiative for powerful LMIS software