Sprint Results by Team:

Notes:

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.
We need to actually exercise the system, from the perspective of various user personas, versus viewing screenshots, etc.
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:

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
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:
- - Josh Zamor (Deactivated) & Krzysztof Kaczmarczyk (Deactivated) will discuss and decide.
OLMIS-596 - Getting issue details... STATUS Print POD:
- Kevin Cussen (Deactivated) to review and approve output
- Jake Watson (Deactivated) to create a ticket to further abstract this into a standalone 'Banded Report Service' (PDF, CSV, Excel, etc.) for 3.0 time-permitting.
1. How to add localization/translation support?
Sonor improvements:
- Josh Zamor (Deactivated) & Sebastian Brudziński to write ticket for flattening test directory for Sonar
Logout OLMIS-496 - Getting issue details... STATUS :
- Josh Zamor (Deactivated) add acceptance criteria/tests for multiple tokens/users (e.g. log out of all?), etc.
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.
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)
- Jake Watson (Deactivated) to reopen and create dependency

Sprint 6 TODOs:

Mary Jo Kochendorfer (Deactivated) & Sebastian Brudziński to review missing requisition API calls and open tickets accordingly
Sebastian Brudziński will send Transifex usernames for SolDevelo leads; Jake Watson (Deactivated) will add to OpenLMIS
Create page to record "Do's and Don'ts" of UML diagramming as needed based on reviews. (Jake Watson (Deactivated))
Jake Watson (Deactivated) to check with Pengfei Cui (Deactivated) about getting CI/CD to new 'demo' server ASAP
Process:
- Update Software Development Methodology with ticket flow (Ben Leibert)
- Also, we need to figure out how best to stagger the Design->Review->Develop
Is there a way to get metrics on how long a review takes? Need to turn these over more quickly (Jake Watson (Deactivated))
Seattle team to review Pawel's Spike on Motech Reuse