Dates: Aug 2, 2018 - Aug 15, 2018 

3.4 Release Candidate Testing

Release Candidate Testing during this sprint

Other areas of focus after the release: contract tests, functional tests, next gap feature work

Team Parrot Sprint

Sprint Goal: 

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:

Team Parrot to use 20% of their capacity to fix the following prioritized Tech Debt tickets:

@Sebastian Brudziński to add Tech Debt backlog here
Regression testing cycle as needed (@Joanna Bebak (Deactivated))

Team Ona Gap

Sprint Goal: 

Finalize the 3.4 release of the reporting stack and scope facility registry integration with mCSD standard.

Tickets:

Future:

Figure out how to backup each reporting service
Write Automated tests for Superset stock status tabular report

 

 

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: 

Release Candidate Testing
Fix bugs assigned to our team as needed
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 
Create tickets for UI mockups
https://openlmis.atlassian.net/browse/OLMIS-5136 (Question in the ticket for Elias, if eLMIS has implemented this then we will want to work on this ticket, but if not we can move this to a future sprint.)

 

20% Tech Debt tickets

@Nikodem Graczewski (Unlicensed) @Łukasz Lewczyński (Deactivated) @Chongsun Ahn (Unlicensed) should review next Tech Debt tickets to add to the sprint.

If time, pull in Requisition functional test cases (Initiate, Submit, Authorize, Approve are most important)

 

 

 

OpenLMIS: the global initiative for powerful LMIS software