Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The burn-down of how many epics still remain in the entire gap scope and links to team velocity.

<insert burn down chart>

<links will be inserted for each sprint>Sprint Reports:

Sprints 21-Present (v3.0.1 - 3.3.0+, March 2017-Present)#Present(v3.0.1-3.3.0+,March2017-Present)-Sprint100TeamParrot,TeamJSI,TeamOna,TeamMindtheGap

Open Question: Kaleb mentioned wanting to see costs alongside the burn-down.  I would like to hear the input from the team on if and how we'd like to address that request.

...


RiskDiscussionStatusApproach to Mitigate
1Sustainability of the codebase if developer community is fragmented in knowledge
Raised by Ashraf and Craig Appl (Unlicensed). Important to consider the trade-off between velocity and cross-functional work.  One team focused on component/area will achieve more than one team constantly shifting components/areas of focus.  However, if the teams do not work across components we run the risk of no developers (or one team/org) understanding how to support or build on the entire OpenLMIS code base.

as of  it is proposed agenda item for the first meeting 


2Metric definition. Right now there are a ton of "Reports" with varying degree of complexity. We do not have a clear set of key metrics and why they are the key ones. How do we get the OpenLMIS community opinionated about which metrics are priority across implementations with varying practices? Which metrics will help our implementers and drive new adoption? How do we learn from each country and organization's experiences?Note yet discussed.
3Lack of input form Tanzania and Zambia stakeholders. Specifically on what scope of features are most important and WHY.  We understand the decision to actually upgrade is unique process/decision for each country. However, we need input from the implementations on priorities and why certain features are useful (or potentially should be redesigned).Note yet discussed.
4Alignment on the strategy for interoperability.Currently the Team Leads, Product Manager, Governance Committee and Architect are not aligned on the approach to implement/support interoperability.


Travel Budget


Iframe
srchttps://docs.google.com/spreadsheets/d/1sbUBnu_TQCWnJJBSqH69OCAajuJhFMFDJbrOkWAQbPc/edit?usp=sharing
width800
titleTravel Budget + Expenses to date
height500

...