...
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? | Lead | Notes |
---|---|---|---|---|
Requisition | 2+ | x | Brandon/? | Upcoming:
|
Stock Management | 2+ | x | Pengfei | Upcoming:
|
Reference Data | 2 | x | Josh/? | Could this go inactive again? |
Fulfillment | 1 | Pawel Albecki | Could go Active
| |
Auth | 1 | Pawel Albecki | Could go active
| |
Notification | 1 | Pawel Albecki | Could go active
| |
Reporting | 2+ | x | Active
Upcoming:
| |
Program Data | 1 for PoC | x | 1 person for PoC Could go active
| |
CCE / nexleaf intRTM | 2 | future | Could go active
| |
Inf. Push | 2+ | future | Could go active
| |
Forecasting | 2+1 | future | Could go active
Might be a part of Reference Data | |
Build and Dev inf | 1 | Could go active
|
Program Mgmt | |
---|---|
Pawel Gesek | SolDevelo |
Brandon | Project & ILL |
Shiyu | SM |
MJ | Product Owner |
Josh | Architect |
...