2018-10-19 Team Lead Meeting Notes

Attendees

Discussion Points

  • Reminder of release and preparations before release testing. Sam would like to identify any high priority bugs are resolved before we start testing.
    • Testing currently scheduled for Sprint 113
  • Reminder of test case guidelines and steps: Regression Testing guide and improvements
  • Reminder of posting in QA Slack channel for testing help
    • Each team should test/QA as much as they can of their tickets
    • Devs/Others can also help with this!
    • Also helpful to include any deadline info
  • Existing Team Lead expectation document: Team Lead/Scrum Master tasks
    • Ashraf, Craig Appl (Unlicensed)Clay Crosby (Unlicensed) if you get a few minutes, could you review this so we could discuss?
    • Amount of time required for all tasks can be difficult
    • These can be taken as guidelines but even if they aren't followed specifically it would be very helpful if the tasks are done in some method
    • Wes: I would love to get more retrospective-type feedback

Mind the Gap:

  • Is Nikodem still helping with reporting work in Sprint 111? How well did that go during Sprint 109?
    • Clay: went pretty well, no communication issues
  • Updating tickets for multiple suppliers feature, will size tickets in grooming
  • Both use cases for mCSD will be completed by end of sprint, will showcase (nice!)
    • Will not need Elias to join in for future team meetings
  • Two tickets for reports in Sprint 111
    • One blocked by Ona
    • SSO work

Parrot:

  • Releasing faster - most are in review
    • Awaiting feedback from dev forum
      • Validating and looking for more tests
  • Finished work on OLIMS-5461 (modified date api access)
  • Fixing performance test process
    • QA over the weekend to ensure that fix is good
  • Will work on another functional test before end of sprint

Ona: 

  • Today is last day of dev for this sprint (team meeting next week)
    • Craig will attend showcase but without the rest of team
  • SSO
    • Researched auth capabilities within superset
    • Identified path forward (will document today and share):
      1. (Suggested) Update OLMIS to support code-based auth
        1. Would also help for Nifi connections to OLMIS
      2. Update ? to support a custom security manager
    • Craig will contact Sebastian to help determine LoE and Josh for design assistance once documentation is ready
      • This will be a blocker soon
  • Working through initial report feedback from JSI meeting
  • Created wiki pages for report feedback
    • Looking for that feedback by Nov 2nd
    • JSI, VR - Core, VR - Implementation (Christine?)

JSI:

  • Sam requesting to have Adunga update test cases according to Regression Testing Guide and Improvements
    • Would be helpful to have discussion about how to do this
  • Working on Shipment file import
    • Three tickets in QA
    • OLMIS-5481 may not be finished by end of sprint, QA will almost certainly not be complete
  • Supporting Ona for reporting work
  • Elias mCSD work with MtG
    • Two tickets in QA
  • Adunga working through quickwins

Action items

  • Ashraf to create sub-tickets for OLMIS-5481
  • Ashraf to set up meeting with Adunga and Sam regarding updating test cases
  • Wesley Brown to contact Christine about reviewing Ona reports
  • Wesley Brown to update team lead document based on discussion

OpenLMIS: the global initiative for powerful LMIS software