Backlog Grooming Sprint 35
Objectives: Finish CCE and begin on F&E. Continue to make performance improvements.
Sprint 35 the focus is features. Sprint 36 the focus is bugs. 3.2.1 release target is after Sprint 36.
CCE
Goal: Make CCE demo-able
https://openlmis.atlassian.net/browse/OLMIS-3211 (MUST)
Do we have a pattern for POST and CSV?
Forecast and Estimation
We are starting on a new feature. If needed, we can have a kick off call to go over the domain and its utility within and across the system. Please make sure to raise any questions and review Forecasting and Estimation and specifically B. View Forecasted Product Needs for background on F&E and how it fits into the product. We are not creating a new service for this functionality, rather it will be stored in Reference Data.
https://openlmis.atlassian.net/browse/OLMIS-2966 (MUST) Q: question in the ticket comments
https://openlmis.atlassian.net/browse/OLMIS-2892 (MUST) Q: questions in ticket comments
https://openlmis.atlassian.net/browse/OLMIS-2971 (MUST)
Should we move CSV parsing/formating to shared lib?
Requisition
https://openlmis.atlassian.net/browse/OLMIS-3202 (MUST)
What are the columns? Should we only shorten the names or also disable some of the columns?
Batch Screen
Fullfilment
Reference UI
https://openlmis.atlassian.net/browse/OLMIS-2656 Nice to have
https://openlmis.atlassian.net/browse/OLMIS-3199 (Team ILL) Nice to have
Reference Data
(Josh Zamor (Deactivated)) unrestrict more GET operations?
programs and facilities done already
geographic zones, levels, facility types, etc
never to be unrestricted: users, ?
Josh Zamor (Deactivated) will eventually create a ticket on the following: cleanup facility, geographic zone and geographic level representations to be normal & essential representations (so exciting)
Platform
https://openlmis.atlassian.net/browse/OLMIS-2884 (Team ILL Retrospective 2nd place vote-getter)
Need more test and performance data (Team ILL Retrospective 2nd place vote-getter)
NIce to have
https://openlmis.atlassian.net/browse/OLMIS-3148
Requests from Malawi
This sprint is focused on new features and performance. We will be holding off on bugs till Sprint 36. I'm moving the list of bugs from Malawi to Sprint 36.
Hey Tenly Snow (Deactivated) we pulled these 3 tickets (3015, 3028, 3032) from the sprint. Please let us know if you want us to include tickets for you in this next sprint. We are trying our best to only add tickets that we plan to complete.
After team ILL's sprint planning I tackled the performance ticket for batch requisition approvals. I wrote a new ticket to try to focus on testing (using existing performance data) for Requisitions. In doing so I realized that an old performance ticket, 2912, hadn't been completed yet for Orderables (which of course has a big impact on requisitions). I added 2912 and marked it as MUST. Ideally we can get both 2912 and 3212 done so we know how Requisition's batch approval is working this sprint.
Nikodem Graczewski and 
Paweł Gesek if you don't think we can get both 2912 and 3212 done this sprint, please prioritize 3212 so that we have an automated test that Malawi can use to inform us.