Page Comparison

Date: 03 Nov 2016 

Attendees: 

...

Theme

Remember that there are roll-over tickets from Sprint 12. We ask that Teams AYIC/TOP do planning poker for the items on this grooming list, BUT only pull an amount of tickets into the sprint based on an amount of work and story points that you are confident that you can commit to finishing this sprint and showcasing on 23 November, 2016. (For comparison in Sprint 12 AYIC/TOP took on ~220 story points, but only finished ~110).

1. Showcase 3 new features - UI and Requisition
   1. (1) Offline requisition form - form fill-out, not initiation or approval
   2. (2) Emergency requisitions - working in UI
   3. (3) My Supervised Facilities requisitions - working in UI
2. Order Service - API
   1. Split orders into an independent service (1314

...

1. 1. )
   2. Goal: After this sprint, a team is ready to work in parallel on significant orders features

...

1. 1. (to discuss at Monday Sprint 13 Q&A meeting)
2. Bugs
   1. 13 bugs from list below
3. Extension Modules
   1. publishing to Maven and being able to deploy an extended service
   2. stretch goal is starting the extending data tooling (Team ILL)

...

• More template fields (933 Total Cost, 1134)
• Requisition Improvements epic
• Comments - 1063?

...

Requisitions

Advanced Template: ranking is not accurate but all need to be estimated.

Improvements: ranking is not accurate but all need to be estimated.

WAIT on 1102 and 536 and 1009.

Tech Backlog

...

Remember, we aren't requiring that all 4 of these go into sprint 13 — please only pull in as much work as we can finish in this sprint, but please pull items into the sprint in this priority order. It would be great if you play planning poker on all of these tickets and add story points to them, but then only pull into your sprint what can fit. And keep in mind this sprint is 2 days shorter.

1. Showcase 3 new features - UI and Requisition

Priorities in Order:

1. Offline (1038, 1338, 1339)
2. Non-full products (it was a roll-over)
3. Emergency Requisitions (roll-over)
4. My Supervised Facilities (roll-over and 1315)
5. UI Inventory clean-up (1358, 1343)
6. User profile page (roll-over)
7. Documentation/NGDoc (OLMIS-1280)

Wait on 1349.

• Clean-up to match inventory
• Documentation
• Finish requisitions (skip, comments?, print)

• Potentially look into doing the configuration screen for the requisition template

  Offline Requisitions
  

Order Export

We will split the Order Service in Sprint 13. After that, we will be ready to do rounds of new Order functionality in sprint 14 and a few sprints beyond.

Bugs

For Sprint 13, do the bugs in the table below EXCEPT: 1119, 130 (which is not for v3), and not the ones already in the Team ILL sprint (1074).

+ We will wait on adding new functionality till sprint 14 (once a separate service)

Order Export

...

Questions:

• Jira Legacy
  server JIRA (openlmis.atlassian.net)

...

• serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-1358

   - no idea what this is about

• Jira Legacy
  server JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key

Potential other tickets - WAIT ON ALL THESE

...

• OLMIS-1348

   - not clear, are we removing validation that triggers after editing the inputs in this ticket? What exactly should be done?

• Jira Legacy
  server JIRA (openlmis.atlassian.net)

...

...

• serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-1341

  - why is this necessary? in order to minimize the manifest?