Backlog Grooming Sprint 44
Goal: Fulfillment features and address blocker bugs.
Dates: Jan 4, 2018 - Jan 17, 2018
6 Sprints left till 3.3 release
Fulfillment
@Nikodem Graczewski (Unlicensed) @Paweł Gesek Note: At the Sprint Q&A meeting, we would like to hear you describe these tickets and tell us what order you might work on them in. We basically want to see if these tickets make sense. We want to start giving tickets more context/user story understanding. One of our ideas from Retrospective meeting was to ask you to describe the tickets and your proposed order during Q&A meetings as a way to see if the tickets make sense. -Brandon
https://openlmis.atlassian.net/browse/OLMIS-239 Q: in ticket
https://openlmis.atlassian.net/browse/OLMIS-1611 (Team Parrot: We have tried to make 1611 a true User Story without giving so many technical implementation details in this ticket. Please review and let us know if you choose to make sub-tasks for the technical details. If there is technical design, please give Team ILL a chance to review. Team ILL would like to hear whether this is helpful to keep tickets high-level.) Q: in ticket
https://openlmis.atlassian.net/browse/OLMIS-3726 Q: in ticket
Bugs
DISC Visualization Demo Data
https://openlmis.atlassian.net/browse/OLMIS-3874 Team ILL API design decisions needed
Requisition
@Sam Im (Deactivated) To schedule meeting to kick-off Stock-based requisition meeting
Team ILL
OpenLMIS: the global initiative for powerful LMIS software