Backlog Grooming Sprint 33
Goal
Release 3.2.0 with a solid set of new features plus bug fixes and performance improvements. We expect the Malawi implementation will upgrade to 3.2.0 during September 2017. It is VERY important that we finish and thoroughly test the tickets for connecting stock management and requisitions. We will hold off on the vaccine stories until we finish and demonstrate migration works.
Note: we removed CCE tickets from the Parrot sprint 22 from the sprint and first priorities since we must finish the other tickets before wrapping up the CCE features. Team Malawi has full sprints and will not be taking on any global work.
Please make sure all tickets are marked with 3.2.
Release 3.2.0
Testing?
Releasing Components
Releasing ref-distro
Video demos of new functionality
Blog post
Connecting Stock Management & Requisitions
https://openlmis.atlassian.net/browse/OLMIS-2834 (MUST) Questions in the ticket comments
https://openlmis.atlassian.net/browse/OLMIS-3023 (MUST) Questions in ticket
Bugs
Prioritized in descending order (not including the roll overs). Please let @Mary Jo Kochendorfer (Deactivated) know if you disagree or believe something should be a higher priority. All bugs below are a MUST unless otherwise noted.
https://openlmis.atlassian.net/browse/OLMIS-2908 Question in ticket
https://openlmis.atlassian.net/browse/OLMIS-2724 (can team Malawi work on this one?) we left for Malawi
https://openlmis.atlassian.net/browse/OLMIS-2726 (can team Malawi work on this one?) we left for Malawi
https://openlmis.atlassian.net/browse/OLMIS-2714Question in the ticket comment
https://openlmis.atlassian.net/browse/OLMIS-2898 (nice to have) if we address less, let's first address requisitions and fulfillment. We could delay working on stock management
https://openlmis.atlassian.net/browse/OLMIS-2903 (nice to have, but not necessary)
Nice to Have (More Vaccines Scope)
CCE
performance: should start measuring here
Stock Management for Vaccines
Team Malawi
Performance Test the 3.2.0 Snapshots with Malawi Data (Pending Discussion - @Ben Leibert will raise this with developers - Core desires this info ASAP/Thursday)
Details: Test what crashed the production server last month with the 3.2.0 component snapshots using the Malawi data set. If we do this quickly, we would have time to fix performance issues before 3.2.0. At the very least, this would prove to us whether 3.2.0 will fix the production performance issues that happened recently.
Steps: Load MW environment up with Ref-Distro snapshots of components plus Malawi data. Run the performance tests. Josh also suggests we might modify the tests to do more concurrent users (in the YAML file).https://openlmis.atlassian.net/browse/OLMIS-2680 (It makes sense to have MW finish this.)
https://openlmis.atlassian.net/browse/OLMIS-2887 (It makes sense to have MW finish this.)
https://openlmis.atlassian.net/browse/OLMIS-2716 (Can probably be marked as Done.)
Team ILL
https://openlmis.atlassian.net/browse/OLMIS-2681 (Performance Priority - Chongsun)
https://openlmis.atlassian.net/browse/OLMIS-2832 (MUST / Team ILL)
https://openlmis.atlassian.net/browse/OLMIS-2939 (Team ILL. Sam to edit this and add regression testing acceptance criteria)
Nice to Have
Reference Data
Admin screen: https://openlmis.atlassian.net/browse/OLMIS-2857 (perhaps the Malawi team)
Do Not Do (reconsider for future sprints)
Team Malawi Past Rollovers
https://openlmis.atlassian.net/browse/OLMIS-2841 (Somewhat on hold; probably won't make in into 3.2)
https://openlmis.atlassian.net/browse/OLMIS-2842 (Somewhat on hold; probably won't make in into 3.2)
https://openlmis.atlassian.net/browse/OLMIS-2758 (Seems relatively low priority for MW.)
https://openlmis.atlassian.net/browse/OLMIS-2429 (Relatively low priority)
https://openlmis.atlassian.net/browse/OLMIS-2912 (Nice to have. However, it seems convert to order work should take precident if possible.)
OpenLMIS: the global initiative for powerful LMIS software