Shared Services Team Page
At the January 2012 F2F in Phoenix, a new workstream was identified and called "Shared Services". This workstream involves several work items or capabilities that represent common needs or services across all the other workstreams of registries, provisioning, authentication and access management. This page defines in more detail the high level expectations of what the common needs are. The following is the high level gap analysis of required shared service capabilities originally identified at the F2F meeting.
Timeline |
Shared Services |
Est |
< 12 month |
- Establish UI mgmt console team and environment - Establish QA/Integration team and environment - Establish Audit/Report team requirements |
High |
< 18 months |
- Create baseline management console - Create baseline QA/Integration tests - Create baseline data warehouse and reporting - Establish training & support team |
High |
< 24 months |
- Create 2nd version of audit/reports - Create 2nd version of mgmt console - Create baseline training & support program |
Med |
< 3 months |
- Convene standards/API team |
Low |
< 6 months |
- Convene cross stream project steering team - Publish initial standards - Publish baseline policy & lifecycle use cases |
Low |
Gimme |
KEW Developer tools |
|
Resources Estimates assume 1 FTE for Low, 3 FTE for Med, and 5 FTE for High. This is the estimated number of development or support resources needed for the specified tasks / deliverables per period.