Page Comparison

Goal: Performance and finish Stock Based RequisitionsRelease Process for 3.3.0

Dates: 29 Mar 2018 - 11 Apr 2018 (Dates may move depending on the number of release candidates made)

Performance

Define non-functional requirements and begin to look for targeted improvements

...

Sebastian Brudziński Nikodem Graczewski (Unlicensed) To follow up from the discussion on showcase meeting Wednesday, we agree it makes sense to close sprint 49 and start sprint 50. The sprint cycle might not exactly be matching the cycles of testing and rounds of bug fixes, but that is okay.

Sebastian Brudziński Nikodem Graczewski (Unlicensed) Regarding branches and use of GitHub Pull Requests and Code Reviews, we want to encourage folks to push to master and use Fisheye rather than branches and GitHub pull requests. If we need to turn off Jenkins deployments (so users testing on UAT or Test servers are not interrupted), we can turn off Jenkins deployments for the day. But having the new work committed on master will allow Team ILL to continue with performance testing with all of the latest fixes. We can discuss more on the Q&A meeting if there are questions about this.

Regression Testing and Release Process (Team Parrot)

Here are the steps we believe are involved in this release process which will take us most or all of this sprint. I'm not sure if you want to create tickets for some of these (like creating RC1) now or not. That's up to you. We will continue using the daily Slack check-ins to we confirm what step of this process we are at.

•  Fix critical/blocker bugs (we flagged the 2 must-have tickets OLMIS-4383 and OLMIS-4384)
•  Regression Phase 2
•  Fix additional critical/blocker bugs (if any identified)
  •  As of April 2nd there are 5 critical bugs that need to be fixed before we can deploy the release candidate Sebastian Brudziński, Nikodem Graczewski (Unlicensed), Joanna Bebak (Deactivated):

    Jira Legacy
    server System JIRA columns key,summary,type,created,priority,status,resolution maximumIssues 20 jqlQuery filter = "20523" and Priority = "Critical" serverId 448ba138-230b-3f91-a83e-16e7db1deed1

    •  

      Jira Legacy
      server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-

...

Editing Orderables

Josh: would this UI be helpful for the product registry?

• • • 3708

       (Must finish before we deploy RC1)
    •  Quick wins for anyone not working on bugs: 

      Jira Legacy
      server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter = "QuickWin" and Labels = "Phase1bug" serverId 448ba138-230b-3f91-a83e-16e7db1deed1

  keyOLMIS-3884(from epic OLMIS-3804; important for Malawi and for core) (Josh and Nikodem Graczewski (Unlicensed) to review AC)
•  Create RC1 & make sure it is announced to the community
  
•  Complete testing RC1 
•  Fix critical/blocker bugs (only if any more identified – hopefully not) and re-issue RC2, RC3 and repeat....
•  Publish official 3.3.0 release

Team ILL

•  

  Jira Legacy
  server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-3317

Notes on what we should focus on next

• Improve sustainability of codebase so the software can be used long-term even beyond the current developers or current core team
  • Strengthen process for continuous delivery (including automated testing)
  • Performance improvements and testing
  • Technical debt and user documentation
• Gap features (for details see Gap Analysis Development: Project Kick off)
  • Dashboards and reporting (across levels)
  • Interfaces to external systems (potentially includes ERP, mobile, and offline applications)
  • Requisition enhancements (favoriting products, columns, usability improvements)
  • Budgeting
  • Fulfillment and re-supply features and enhancements
  • User personalization and self-service (configuration, notifications, dashboards)
  • Equipment tracking
  • Note: Gap features will begin during 3.4 release cycle, but will continue for the year of the Gap project. Gap feature prioritization will determine which of these features are conducted within the current Gap project budget and timeline.
• Respond to community requests and needs coming from Implementers (Malawi, Vaccine Interests, PSM Global interests)
  • Notifications enhancements (consolidating convert to order requisitions) - may have overlap with Gap features <Malawi>
  • Finalize and release Batch Approval of Requisitions <Malawi>
  • Finalize stock based requisitions (not just for vaccines) <Finalize feature for tying stock and reqs>
  • Continue working on vaccine features (distributions) <vaccine>
  • Administrative screens <PSM global>
  • Enhance the POD
  • Enhance Stock Management
  • Enhance Fulfillment
  • User Experience improvements

• 4479

•  

  Jira Legacy
  server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-4492

•  

  Jira Legacy
  server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-4493

•  

  Jira Legacy
  server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-4460

   
•  Finalize agenda for April 11-13 Gap Estimation Meetings