2019-03-15 Team Lead Meeting

15 min

General Discussion

Sam

We are now beginning release testing in Sprint 123, all development must be completed in Sprint 122.

• Are there any concerns about this new date? Do we think we can deliver? Any blockers?

  • Ashraf: We should be ok, this sprint we are connecting front end to back end, and will also have edge cases to complete. I am confident we will complete in time.

  • Klaudia: We are fine, but we do have holidays (3 days) in the end of April and beginning of May (1&3), and Joanna B has vacation for two weeks in April/May. This means that Joanna B will not be available to begin the release testing.

https://openlmis.atlassian.net/wiki/spaces/OP/pages/501580018/The+3.6+Regression+and+Release+Candidate+Test+Plan+work+in+progress (Joanna and Sam will present this sometime in Sprint 122 to all the teams.

10 min

Ona

Not present

10 min

JSI

Ashraf

Sprint 121:

We started with unfinished kit work from Sprint 120. APIs are being developed, including updating orderables.

Adugna is working on the front end UI but it is not connected to backend (doesn’t save yet). This work will start in Sprint 121.

Edge cases for kitting will be in Sprint 122.

Teklu has a contract test failure that needs to be fixed. Hassan might not have time to work on quick wins.

We are also working on developing the UI for the reference data upload.

No blockers yet. When Elias is done with kitting backend work, he will need Josh’s review during this sprint. FYI @Josh Zamor

10 min

MtG

Sam

Sprint 121:

Sprint goal is to continue the RapidPro integration for notifications and start the UI for subscription management.

Also cleaning up some notifications bugs and adding demo data for notifications testing.

We plan on being finished by end of Sprint 122.

No blockers.

10 min

Parrot

Klaudia

Sprint 121:

Sprint goal is to improve the performance of initiate requisition with two functional tests.

Adding compressing to http post response, and the second is removing an additional call to retrieve initiated requisition.

Performance testing is in progress. We’ve made good progress with application caching with redis.

We’ve had a meeting with Ian about sprint goal and his potential work - he will work on a simple functional test.

No blockers.