...
...
NOTES:To be added.
Discussion the risks identified by committee members Risk #2. Are we building the right product for our target environment? - What do we do about it if we build the right product? If we go to a country, and it doesn't meet the needs. We course correct. Hopefully we the right architecture in place to support extension.
- We want to find the common feature set for OpenLMIS
Risk #11. Too many new country requests / distractions / demands of project teams (scope creep) - Chris George (Unlicensed) noted this is important for the committee to set expectations
- Current strategies will need to be monitored over time and adjusted as needed
Risk #3. Solution too complex for end users Other risks will be addressed on an on needed basis. slot time for each call. - Risk #1. New deployments that are needed before 3.0 is done
Risk #7. OpenLMIS community stays dependent on centralized funding from 1-2 primary sources and fails to diversify and encompass open source development principles- Risk #6. OpenLMIS community fails to grow. Stays small and driven by self-interest
- Risk #5. Perception of code review as an acceptance of the story. The role of code review.
- New risk identified by Lakshmi: Countries do not migrate to 3.0.
|
|
Update on the roadmap and work coming up next - SolDevelo is in town
- Showcase this week, Sprint 5. We plan to have two basic services running (auth and requisitions)
- Next sprint will focus on role based access, requisitions, converting reqs to orders, polish up the testing strategy, and start on the UI
|
...
RECORDING
OpenLMIS Product Committee-20160809 1500-1.arf
...