Sprint 9 Goals

SolDevelo Sprint Goals

The following goals and subsequent activities arose from VR's Sprint 8 planning session. Please review them in order to inform SolDevelos work over the next Sprint.

Technical Priorities

in Descending Order

Extract reference data from requisition, connect requisition to reference data (where we are in that will be determined in the showcase)· This is very important and may require more than one developer.
Wrap those requisition designs up and start implementing
Showing the application running together with the basic service discovery we have now which goes along with contract testing

General Guidance

Please consider open tickets from the last Sprint as a priority.

Infrastructure / Modular Architecture Tickets

963: Rename *Line classes to *LineItem where it makes sense
968: Fix table names to conform to the code style guide
977: Remove Stock and its related code from reference data
976: move generated RAML file to build directory
1044: Set up initial service discovery, and hook things up at openlmis-blue

UI Tickets

1027: Use SCSS files to generate CSS (not LESS)
1029: Add Bower for front-end library management
1030: Build process to compile and compress JS/CSS
1043: Approve requisition list
1004: UI: Initiate a Requisition (Relatively low priority for this sprint)

Testing

Objectives: Draft Testing Strategy. Improve acceptance criteria and story testing. Start implementing contract tests across services. Anna Czyrko (Unlicensed) please update or modify based on our conversation.

1014: contract test for creating a new user
1013: contract test for logging in
New ticket for contract test on initiating a requisition (if we get to this)

Functional Priorities

Get basic requisition design done, implemented and running
Finish up order to export epic

Potential new tickets

Requisition Template

· 422: Create and edit schedule (re-opened)
· 874/5: Reference Data – Requisition group and members (does this need to be re-implemented or does it already exist?)
· 998: Add Beginning Bal and Product Code to the template (re-implementing)
· 820: template - requested quantity
· 821: template – requested quantity explanation
· 816: template – remarks
· 381: template – stock adjustment reason by program (part of reference data)
· 815: template – total loss and adjustments
· 814: template - consumed quantity
· 813: template – total Received quantity

Requisition Creation

· 991: Requisition status checks missing (are status checks
· 997: ensure requisitions are tied to periods
· 760: Create a basic requisition (re-opened) - Paweł Gesek do we need to do this if OLMIS-741 is being completed? 760 is a more basic requisition than 741. Also, if 741 is being completed this sprint – do we need to still do the template fields (see above) or are they completed with this… Let’s sync on this after the showcase to make sure I understand where things are with regard to the template/requisition
· 380: apply adjustment reason to Adjustment quantity - Paweł Gesek – is this one already covered with OLMIS-741?

Order Related stories

· 829: setup the transfer properties
· 398: Generate an order (implements what’s missing from 226)
· 1006: PoD improvements to be finished

VR's Sprint Goals

Overall Priorities

Ensure all reference data code is extracted from Requisition Service into Reference Data Service. (OLMIS-763)
Ensure bringing up multiple services can only be done through openlmis-blue (individual Services no longer bring up other Services, db and log excluded). This entails removing links to other Services in our docker-compose files. (OLMIS-1044)
Ensure any calls from one Service to another is done through nginx/reverse proxy. Related to openlmis-blue being up and running and removing links in docker-compose files. (OLMIS-1044)
Achieve our Testing Strategy in that non-contract tests won’t ever rely on external Services (db and log excluded) to be running.
Lead UI efforts and support the team moving foward with stiching things together.

Infrastructure / Modular Architecture Tickets

1017: Enable developers to write component tests by setting up test configuration

UI Tickets

1024: Create consensus on UI variations and patterns (Nick)
1033: Configurable top navigation area (Nick)
1040: User's authentication is checked on page load (Nick)