2018-12-14 Team Lead Meeting Notes

Dec 14, 2018

Attendees

@Clay Crosby (Unlicensed)
@Craig Appl (Unlicensed)
@Sam Im (Deactivated)
@Sebastian Brudziński

Discussion Points

3.5 release notes
Showcase for Dec 19
- Minimal set of tickets to showcase
- Functional tests
- 3.5 release testing
- Holiday goodbye/hello
Sprint 115
- Leave for Dec
- Team Ona: all of the team is out - only Clay and Craig so they will be working on ticket writing
- Team Parrot: most of the team is out - focus on Malawi support
- Next sprint planning
- Combine sprint 115 and 116 (Sprint 115 would be 4 weeks)
  - Same sprint schedule but no showcase for Sprint 115 because little work is done during leave
  - Any tickets during this time may need to be tested by other team members (not necessarily QA when they are out)
  - Add discussion in team lead slack channel

Mind the Gap (Sam):

Working on splitting requisitions for multiple suppliers
Release retrospective
Starting writing notifications feature tickets

Parrot (Sebastian):

Continue work on functional tests
Continue code freeze tasks
Creating a separate instance for functional tests (instead of using test server)

Ona (Craig/Clay):

Peter & Josh discussions on data pumps
Planning for 3.6 release
DHIS2 specs
Sprint 114 reporting testing & demo video

JSI (Ashraf):

Action Items

@Wesley Brown to gather feedback from teams (start with Craig?) regarding working with API and services

@Sebastian Brudziński, @Sam Im (Deactivated), @Ashraf, @Craig Appl (Unlicensed) add code freeze tasks to the next sprint as we are working in the sprint. We know that this will impact velocity for this sprint, but that's ok.

@Ashraf will follow-up with @Wesley Brown on the identified risks and mitigation strategies

@Wesley Brown to review current dev process documentation and update according to current expectations/process

@Wesley Brown to push discussion about velocity and dev process to later team lead meeting

@Wesley Brown should we have team discussions about velocity?

@Sam Im (Deactivated) after the release is done, then Sam will send out a release retrospective survey