Backlog Grooming Sprint 32

Owned by Mary Jo Kochendorfer (Deactivated)
Last updated: Aug 03, 2017 by Josh Zamor

Goal

Two sprints left to complete CCE Service. Let's continue pushing ahead on Vaccines functionality. Sprint 33 is when we release 3.2.0 around August 30-31.
Team ParrotTeam ILLTeam Malawi

Vaccines

Vaccine Tickets, UI Design and Tech DesignBugs

CCE

Spikes & GuidanceConfiguration Report

Connecting Stock and Requisitions


Performance
(Perf Tests and Optimizations)

New Admin Screen
Reporting Service (for contribution)

Note: We are starting to include Malawi priorities on this backlog grooming in order to improve coordination and transparency between the teams. For example, the core team recently established a new system for Performance Testing, and now the Malawi team is going to build on that by adding performance tests to critical parts of the system, such as Convert to Order, that are key areas for the Malawi implementation.

Vaccines

CCE (MUST)

(Hey Pawel, these top 3 tickets are related/overlapping. Please read them all and divide up the work carefully between devs (or stagger the work)).

Connecting Stock Management and Requisitions (MUST)

QA & Testing

Reference UI

Requisition

  (none)

Fulfillment

Reference Data

Stock Management

Auth

  • OLMIS-2902 - Getting issue details... STATUS  (cleaning up tech debt in Auth service; proposed by Team Parrot in Sprint 31)

Platform

Team Malawi

Ben Leibert is identifying priorities and coordinating between teams

  • High priority bugs that will benefit the Malawi implementation to happen right away to be included in the 3.2.0 release at end of August
  • Potentially contribute to admin screens (such as the one listed above under Reference Data)

       Reporting

       Reference Data

  • OLMIS-2758 - Getting issue details... STATUS  (MUST)
  • OLMIS-2912 - Getting issue details... STATUS  (MUST)
    • this one may need more details in the ticket to move it from Roadmap to ToDo
  • OLMIS-2716 - Getting issue details... STATUS  (MUST) (The MW team reported this issue.)
  • OLMIS-2713 - Getting issue details... STATUS  (The MW team reported this issue.)

      Requisition

  • OLMIS-2680 - Getting issue details... STATUS  (MUST)
  • OLMIS-2681 - Getting issue details... STATUS  (MUST)
    • Requisition object will need to understand the format laid out by reference data
    • Requisitions migrated to store a relevant permission string
  • OLMIS-2880 - Getting issue details... STATUS  (MUST)
  • OLMIS-2887 - Getting issue details... STATUS  (MUST)
  • OLMIS-2863 - Getting issue details... STATUS
  • OLMIS-2429 - Getting issue details... STATUS  (Low priority, but also low effort.)
  • OLMIS-2726 - Getting issue details... STATUS
  • OLMIS-2724 - Getting issue details... STATUS
  • OLMIS-2908 - Getting issue details... STATUS
    • Not a must for this sprint

Team ILL

OpenLMIS: the global initiative for powerful LMIS software