Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 30 Current »

Sprint Results by Team:


Notes:

  1. As a point of order, we need to review all done tickets in the dashboard before starting the showcase since many tickets are carried over.
  2. We need to actually exercise the system, from the perspective of various user personas, versus viewing screenshots, etc.
  3. When tickets are considered complete, or 'Done', the developer should set the status to 'In Review' and assigned to their respective Lead, who will confirm that the ticket is, indeed, 'Done'. Once confirmed, the Lead should update the status to 'Done' and assign to the Product Owner (Mary Jo).

Recording: OpenLMIS v3 end-of-Sprint Showcase-20160824 1405-1.arf

Sprint 5 TODOs:

  1. Notification Service:
    • Jake Watson (Deactivated) to create ticket to do UML activity and sequence design for review
      1. should be asynchronous, logged in DB, etc.
      2. Provide sample code for how another service would use
    1. Ticket to re-use MoTECH SMS module
    2. Monitoring strategy? Or does Spring handle
  2. Consul
    • Jake Watson (Deactivated) to create ticket to produce high-Level technical design on how it will be used and work with our Services architecture.
    1. Configuration Approach – document needs review and decision:
  3. OLMIS-596 - Getting issue details... STATUS  Print POD:
    1. How to add localization/translation support?
  4. Sonor improvements:
  5. Logout  OLMIS-496 - Getting issue details... STATUS :
    • Josh Zamor add acceptance criteria/tests for multiple tokens/users (e.g. log out of all?), etc.
  6. Extension Module Design  OLMIS-783 - Getting issue details... STATUS
    1. Active discussion on Google Group between Weronika Ciecierska (Unlicensed) & Darius Jazayeri (Unlicensed)
    2. Needs final review by Mary Jo Kochendorfer (Deactivated) and VR Dev, with Darius
    3. Once approved, we will need to create user documentation ticket, code examples, diagrams, etc.
    • ALSO, need to cover extending entities with custom fields, etc. (a la OpenMRS?)
    • Jake Watson (Deactivated) to create a meeting invite to close the loop.
  7. OLMIS-641 - Getting issue details... STATUS
    • Mary Jo to clone or create new story for 'fill'
    1. Needs to be re-opened assigned for testing once we have UI with user personas in mind
    2. Needs to be reopened to use new 'Printing Service' (PDF &/or CSV, Excel)

Sprint 6 TODOs:


  • No labels