11 Jan 2019

Attendees

Discussion Points

Showcase - Concrete plans going forward
- Ashraf:
  - Team leaders takes the lead in discussing the work done by the team
    - Explains each ticket that was done and how it fits into the overall picture
    - Briefly mention features that are not complete in a given sprint
    - Summarize the QA and Test tasks that were completed
    - For spike work, share the findings of the spike
  - Sam: Not a fan of the team lead sharing everything
    - Like having each team member share
    - Just having team lead would be more like a presentation
  - Sebastian: Mixed feelings
    - This would help showcase go smoother
    - Members get an opportunity to go into more detail
    - Leads will have to spend time getting up to speed on each ticket and members will have to take the time to do so
- Wes
  - Team lead provide introduction and overview
  - Call on a couple team members to share in more detail
    - Vary the team members at each showcase
- Clay
  - Clay already tends to provide that overview
  - Once they are done, rest of team tends to head out
    - This is not likely to change during this release
    - Only focused on the report work
  - Team is not interested in presenting
  - Continue with sprint review at the start
- Sam
  - Timebox each team
  - Team lead could prep a Jira report
- Sebastian
  - Sprint review helps to know what is going on
  - Be better about starting the call on time
- Conclusion
  - Going forward, the meeting will start on-time, regardless of who is present
  - It will start in the same fashion, with an overview of the previous sprint for each team by Wes
  - Each team will get a strict 15 minutes to share
    - Team leads - please help keep your team within that time
    - Team leads can structure their 15 minutes in the way they think is best
      - That being said, we do hope that team members are included

Mind the Gap (Sam):

Working on completing the multiple supply partner work
- Hope to have the split requisitions ready for the showcase
Spike of customizable notifications
Ian (TZ) may pick up a bug this sprint

Parrot (Sebastian):

Scalyr is still not accessible, Josh is working on it
- This is blocking the perf work
Working on functional tests
Process for deprecating manual test cases
- Sam is reviewing
Looking for more feedback on OLMIS-5665
- Cannot reproduce
- Looking for additional information from Christine

Ona (Clay):

Craig is working on scoping DHIS2 epics
- Currently in Cape Town so not very available
- Will finish work before end of sprint
  - Create and size tickets for epic
- Clay working on defining the metrics
  - Creating a wiki page for the information
Adding documentation for the 3.5 release

JSI (Ashraf):

Still working on shipment file edge cases
- This will not be completed by the end of this sprint
Picked up a few quickwin tickets
Offering to assist Ona with report work
Preparing work for the Kitting epic
- Will be ready to meet with Josh early next week

Action Items

Wesley Brown to gather feedback from teams (start with Craig?) regarding working with API and services
Sam Im (Deactivated) after the release is done, then Sam will send out a release retrospective survey
Wesley Brown to follow up on OLMIS-5665 for team parrot
Wesley Brown to set up meeting between JSI and Josh regarding Kitting

Browser not supported