Components & Resourcing


Ideal:  Each one of these components has a component lead.  Component lead is responsible for:

  • helping define and enforce their components boundaries
  • participating in grooming for their component:  new functionality, responding to needs of their component from others
  • quality

Since we have many components, and few people, it's presumed that some people will need to be a component lead for two or more components.  Though it's unlikely that one component lead should own two or more components under active development.


Component

Relative Team Size

(1, 2, 2+)

Active?LeadNotes
Requisition2+xBrandon/?

Upcoming:

  • Stock Mgmt
  • Lots
Stock Management2+xPengfei

Upcoming:

  • Vx:  VVM
Reference Data2xJosh/?Could this go inactive again?
Fulfillment1
Pawel Albecki

Could go Active

  • Local fill
Auth1
Pawel Albecki

Could go active

  • RESTful re-design
Notification1
Pawel Albecki

Could go active

  • Redesign cleanup
  • Redesign for multiple channels
  • Support SMS
Reporting2+x

Active

  • Malawi might donate Routine Reporting service

Upcoming:

  • Ad-hoc reports
  • Dashboards
  • To not break reports: data pumps
Program Data1 for PoCx

1 person for PoC

Could go active

  • ODK
  • DHIS2
CCE / RTM2future

Could go active

  • Vx
Inf. Push2+future

Could go active

  • Vx
Forecasting1future

Could go active

  • Vx

Might be a part of Reference Data

Build and Dev inf1

Could go active

  • multi-host deployments
  • hot re-deploy of Services
  • feature flags
  • CI support of Pull Requests



Program Mgmt
Pawel GesekSolDevelo
BrandonProject & ILL
ShiyuSM
MJProduct Owner
JoshArchitect