2018-08-31 Team Lead Meeting notes

Date

Attendees

Discussion

  • How is planning for next sprint going?
  • Has the retrospective been completed?
  • Are there any items blocking?

Sam:

  • Had retrospective and planning after showcase
  • Are behind on pulling in the mCSD feature tickets
    • Waiting on the outcome of the spike done by Elias
    • Meeting to discuss that work will happen later today
  • Ready to work on splitting product lists
  • Mostly focusing on design work and ticket writing for splitting product lists and mCSD

Craig:

  • Clay focused on planning/ticket writing coming out of the report meetings at VR this week
  • Jason continuing work on deployment/integration/etc
  • OLMIS-5327 - Getting issue details... STATUS  focuses on ensuring the Malawi demo data is available for Sprint 108. The options are:
    • At first this will kept private but need to see if anyone needs to sign anything or whatever to use the data
    • While this data needs to be kept private then all downstream instances (test, uat) would also have to be private
  • May include setting up the reporting stack for demo v3 (Josh and Chongsun)

Sebastian:

  • Focused on service configuration tasks
    • Rewriting jasper reports to use number format
    • UI work will be done in the next sprint
  • Started working on allowing stock-based requisitions to use all remaining columns
    • Will be fleshing out the epic to add more detail and add tickets
  • Will also be working on a few bugs and tech debt tickets as well
  • Retrospective:
    • What can be improved: Jenkins!
      • Ticket to disable notifications for development branches (non-master, non-release branch)
      • Suggest that developers notify the #build channel when they break the build to acknowledge
      • Recommend that breaking commits that will take more than 1 day be reverted and then reapplied once fixed  

Ashraf:


Action items

OpenLMIS: the global initiative for powerful LMIS software