Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »


Goal: 

Dates:  -  

Questions for team: What do we need to do to get closer to continuous delivery?

Editing Orderables

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

Demo Data

Josh please add ticket here, and flag which are for Team ILL/Parrot:

  • OLMIS-4493 - Getting issue details... STATUS  (Team ILL)
  • OLMIS-4503 - Getting issue details... STATUS (Team ILL)
  • OLMIS-4491 - Getting issue details... STATUS (Team ILL)


Stock Based Requisition

Sebastian Brudziński we would like you/Team Parrot to own these epics just like you did with the POD work after you were in Seattle.

Dependency diagram:  https://www.lucidchart.com/publicSegments/view/71af4a62-0bea-4245-9005-3461919c9d35/image.png

UI

Other?

  • OLMIS-4527 - Getting issue details... STATUS Should we do this?

Bugs and Tech Debt

Sebastian Brudziński We would like to start a new process where a percentage of every sprint is set aside for Bugs and Tech Debt. For bugs we propose 20% of the sprint, and you would pull in bugs from the prioritized bug list that Team ILL maintains either on these wiki pages or directly from the Jira backlog (Sam Im (Deactivated) will provide the list). For Tech Debt we propose you/Team Parrot choose what items add the most value (Josh Zamor has ideas about how to get this started).

For Tech Debt we'll convene to look at what I've proposed in Tech Debt Next.  See this screenshot:


Bugs

Sam Im (Deactivated) and Mary Jo Kochendorfer (Deactivated) to prioritize bugs and add to this sprint.

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
  • No labels

OpenLMIS: the global initiative for powerful LMIS software