Backlog Grooming 2016_09_01

Attendees:
@Kevin Cussen (Deactivated), @Jake Watson (Deactivated), @Paweł Gesek, @Sebastian Brudziński, @Josh Zamor (Deactivated), @Ben Leibert, @Krzysztof Kaczmarczyk (Deactivated), @Mary Jo Kochendorfer (Deactivated)

Next steps:

@Mary Jo Kochendorfer (Deactivated) to create UI tickets by page

@Jake Watson (Deactivated)and @Mary Jo Kochendorfer (Deactivated)to pull out top tickets in Mod Arch and Build

@Jake Watson (Deactivated)will continue the conversation with ODK and we will check back for next sprint planning

Sprint 8 Potential tickets and scope

Carry over from Sprint 7?
- Requisition design (UML/Sequence) wrap up and finish (or this might be done this sprint?) - (status: will be wrapped up)
- Product implemented (status: depends)
- Reference data (status: we think it will be finished)
- - This will include hooking up to requisitions
- RBAC will hopefully done (status: we think it will be completed)
UI (what should our goal be?)
- Next area: create a requisition (connect the api to ui), submit, authorize
- Potentially also start "the configure a req template" page in parallel
Exporting orders (will these be finished up?)
- Carrying over 3 tickets

Requisition template tickets
- 422 - Create and edit schedule
- 998 - template fields to template
- 874 - Requisition groups
- 820 - requested quantity
- 821 - requested quantity explanation
- 816 - remarks
- 831 - stock adjustment reason (associated with reference data)
- 815 - losses/adjustments
- 814 - totally consumed quantity
Requisition creation
- 997
- 741
- 760
- 380
Testing (what's our goal for the next sprint)
- Manually test UI
- Contract tests
- Seed data?
Anything from Mod Arch or Dev?
- Need to determine what is priority prior to planning call
- Jake's email:
  - Arch:
    - https://openlmis.atlassian.net/browse/OLMIS-731: A requirement for multi-tenancy? I moved out of 3.0
    - https://openlmis.atlassian.net/browse/OLMIS-733: Randomized UUIDs are not performant in Postgres indices — can be closed?
    - OLMIS-843 (Events), OLMIS-556 (External integration pattern), OLMIS-843 (async service comms) & OLMIS-556 (scheduler) all related in a way — what did Pawel find from MoTECH that we can reuse?
  - Build-related:
    - some in there from Sebastian that need to be addressed;
    - Let’s review the ‘Jenkins’ tix with Pengfei; there are a number of Jenkins-related tickets that either could be handled by him or perhaps can be closed.

(Pushing back to Sprint 9) Spike on Program Data solution
- FYI - ODK is close to version 2.0 (is there estimated date - 2 weeks)
- Putting off for another sprint
- Using JSON, no longer xforms
- Open Question: How to do this without building two UIs

No recording this time.