Sprint 10

Goals

  1. Roll-overs: finish tickets rolled over from Sprint 9 (32 tickets)
  2. Requisition Service: push to finish OLMIS-760 and OLMIS-741 (details will be discussed at a 'Planning 3.0 Beta' meeting Thursday 4pm Poland / 7am Seattle)
  3. Requisition UI: get Nick and SolDevelo UI staff to collaborate to get a visible UI in place (also will be discussed at the same meeting)

Note: We are not adding more tickets from the Backlog into Sprint 10 at this time. The large volume of tickets rolling over may be enough to keep the teams busy for most of the sprint. If the roll-over tickets are all completed we can add more from the Backlog later during the sprint. Keep in mind that many of the tickets rolling over have already rolled over for a few sprints. Before we add more to the sprint or pull from the backlog, we have to complete these.

Process Improvements

  1. Slack End-of-Day Check-Ins: All SolDevelo and VillageReach team members are asked to post a two-sentence message in Slack #general at the end of their work day. The message should answer two questions: (1) What did I work on today? (2) What is blocked or does someone else need to know about?
  2. Tech Meetings on Skype/screensharing: Nick and Chongsun will schedule with Sebastian, Chris, and maybe Paweł or others if appropriate.
  3. Continue the other process improvements that have been made recently, including:
    1. developers checking in code daily to 'master' branch;
    2. VillageReach and SolDevelo working together to improve the object-oriented design (sequence diagrams, class diagrams);
    3. estimating tickets during sprint planning so we can measure velocity and plan sprint work-loads more accurately.

Showcase

Video: OpenLMIS End of Sprint Showcase-20161012 1405-1.arf

The following 38 tickets were demonstrated or discussed at the showcase:

Story https://openlmis.atlassian.net/browse/OLMIS-537 Enable customizations with with extension points
Story https://openlmis.atlassian.net/browse/OLMIS-763 Reference Data Service
Story https://openlmis.atlassian.net/browse/OLMIS-783 Extension modules - design & example
Story https://openlmis.atlassian.net/browse/OLMIS-867 Assign roles to a user record for requisitions
Story https://openlmis.atlassian.net/browse/OLMIS-874 Requisition Group
Story https://openlmis.atlassian.net/browse/OLMIS-875 Requisition group members
Story https://openlmis.atlassian.net/browse/OLMIS-913 Design seed data levels
Sub-task https://openlmis.atlassian.net/browse/OLMIS-939 UML Sequence Diagram: Initiate Requisition Workflow
Sub-task https://openlmis.atlassian.net/browse/OLMIS-940 UML Sequence Diagram: Authorize Requisition Workflow
Sub-task https://openlmis.atlassian.net/browse/OLMIS-941 UML Sequence Diagram: Approve Requisition Workflow
Sub-task https://openlmis.atlassian.net/browse/OLMIS-943 UML Sequence Diagram: Reject Requisition Workflow
Sub-task https://openlmis.atlassian.net/browse/OLMIS-944 UML Sequence Diagram: Delete Requisition Workflow
Story https://openlmis.atlassian.net/browse/OLMIS-965 Configure order file template
Story https://openlmis.atlassian.net/browse/OLMIS-977 Remove Stock and its related code from requisition service
Sub-task https://openlmis.atlassian.net/browse/OLMIS-983 UML Class Diagram: Requisition Workflow
Sub-task https://openlmis.atlassian.net/browse/OLMIS-985 UML Sequence Diagram: Submit Requisition Workflow
Bug https://openlmis.atlassian.net/browse/OLMIS-1011 Log into the UI using username and password
Sub-task https://openlmis.atlassian.net/browse/OLMIS-1015 Provide design (UML class and sequence + RAML)
Task https://openlmis.atlassian.net/browse/OLMIS-1017 Enable developers to write Component tests
Task https://openlmis.atlassian.net/browse/OLMIS-1018 Re-write de-activated Reference Data integration tests
Task https://openlmis.atlassian.net/browse/OLMIS-1019 Re-activate spring security on Reference Data service
Story https://openlmis.atlassian.net/browse/OLMIS-1030 Build process to compile and compress JS/CSS
Story https://openlmis.atlassian.net/browse/OLMIS-1040 User's authentication is checked on page load
Story https://openlmis.atlassian.net/browse/OLMIS-1043 Approve requisition list
Task https://openlmis.atlassian.net/browse/OLMIS-1044 Set up initial service discovery, and hook things up at openlmis-blue
Story https://openlmis.atlassian.net/browse/OLMIS-1045 Development and production server loads single index.html page
Story https://openlmis.atlassian.net/browse/OLMIS-1046 Create a production docker image for requisition-refUI
Task https://openlmis.atlassian.net/browse/OLMIS-1047 Refactor configuration of order file template
Story https://openlmis.atlassian.net/browse/OLMIS-1051 Create page state to view Requisition
Task https://openlmis.atlassian.net/browse/OLMIS-1052 Refactor ITs that require external APIs to work
Story https://openlmis.atlassian.net/browse/OLMIS-1055 Refactor code in Services so they do not call each other directly
Task https://openlmis.atlassian.net/browse/OLMIS-1057 Set up compose files to allow running singular services properly within our platform
Task https://openlmis.atlassian.net/browse/OLMIS-1071 Plan steps to roll the 3.0 Beta release
Task https://openlmis.atlassian.net/browse/OLMIS-1076 Choose and document browsers/devices and languages for QA testing
Task https://openlmis.atlassian.net/browse/OLMIS-1079 Get Blue in CD pipeline
Task https://openlmis.atlassian.net/browse/OLMIS-1081 Address requisition service design issues
Task https://openlmis.atlassian.net/browse/OLMIS-1083 Updates to the style guide
Story https://openlmis.atlassian.net/browse/OLMIS-1103 Create read-only product grid for requisition


OpenLMIS: the global initiative for powerful LMIS software