/
Backlog Grooming Sprint 104

Backlog Grooming Sprint 104

Nov 13, 2018

Dates: Jul 19, 2018 - Aug 1, 2018 

3.4 Release Candidate Testing

Release Candidate Testing will begin during this sprint

  • Other work should include updating translations for 3.4 release and updating documentation related to 3.4 release



Team Parrot Sprint

Sprint Goal: Finish epics, 3.3.1 patch release and critical bug fixes

Continue if not done in Sprint 103: https://openlmis.atlassian.net/browse/OLMIS-4866

Do the patch release: https://openlmis.atlassian.net/browse/OLMIS-5037

@Mateusz Kwiatkowski to add ticket for requisition contract test failures - https://openlmis.atlassian.net/browse/OLMIS-4930

https://openlmis.atlassian.net/browse/OLMIS-5041 this probably won't get done before sprint 104; we can however finish this up early next sprint and leave space for any performance improvements tickets

Bugs: We definitely need to tackle https://openlmis.atlassian.net/browse/OLMIS-5073 and https://openlmis.atlassian.net/browse/OLMIS-5064 (potentially replace some bugs that weren't picked in sprint 103 if not enough capacity)

Perf testing: After early performance testing, verify whether https://openlmis.atlassian.net/browse/OLMIS-5076 and https://openlmis.atlassian.net/browse/OLMIS-5075 need to be tackled and potentially add more tickets

Docs: https://openlmis.atlassian.net/browse/OLMIS-5058

RC? Are we planning to release first RC this sprint @Mary Jo Kochendorfer (Deactivated)?





Each sprint, Team Parrot's sprint will include up to 20% bugs and up to 20% tech debt tickets from the respective backlogs

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
3.4 Release Candidate Testing (@Joanna Bebak (Deactivated))

Team Ona Gap

Sprint Goal:

Add reporting stack to CI process, create end-to-end sample, document and release with OpenLMIS v3.4

Future:

Write human test scripts for the MVP of the reporting stack (What steps do we expect a tester to go through?)
Figure out how to backup each reporting service
Write Automated tests for Superset stock status tabular report
Define the process for restarting process groups in a Nifi docker container that has be restarted
Test the status of Flowfiles when a docker container is restarted (What happens to them? Are they persisted, are they deleted?)



Team JSI Gap

Sprint Goal: 

 @Ashraf to add tickets here

Type your task here, using "@" to assign to a user and "//" to select a due date

Team Mind the Gap

Sprint Goal: 

Tickets related to the following epics will be added as they are created: @Nikodem Graczewski (Unlicensed), @Łukasz Lewczyński (Deactivated), @Chongsun Ahn (Unlicensed) FYI these are the next prioritized features : 
https://openlmis.atlassian.net/browse/OLMIS-4842(This is an epic that has been sized as Medium, the team should review and begin breaking down possibly 2 more manageable epic sizes of S, and then work on writing tickets)
Tech Debt tickets:
Bugs
https://openlmis.atlassian.net/browse/OLMIS-4404 (Needs some review of available options before the bug can be fixed - notes are in ticket)
Release Candidate Testing
Sam & Chongsun in Gdansk: Gdansk agenda 7-30 to 8-3

OpenLMIS: the global initiative for powerful LMIS software