High-Level User Provisioning Project Tasks
Rough Estimates
The time estimates in the following task list are very rough. Depending on the outcome of the detailed project and architecture analysis, these dates will likely require adjustment.
# |
Task |
Predecessors |
Duration |
|---|---|---|---|
1 |
Preparation and Detailed Planning |
|
|
1.1 |
Staffing/Recruiting |
|
week 1 - week 6 |
1.2 |
Develop Detailed Project Plan |
1.1 |
week 3 - week 7 |
1.3 |
Develop Detailed Architecture |
1.1 |
week 3 - week 7 |
2 |
Design, Build, and Test |
|
|
2.1 |
Technology evaluation and selection (e.g., middleware suite selection) |
1.3 |
week 7 - week 13 |
2.2 |
Develop Communications Plan |
1.3 |
week 7 - week 13 |
2.3 |
Design and Implement Common IAM Interface |
2.1 |
week 13 - week 40 |
2.4 |
Prepare Product Documentation |
2.2, (2.3) |
week 36 - week 44 |
2.5 |
Test, QA |
(2.3) |
week 36 - week 44 |
2.6 |
Release Product |
2.4, 2.5 |
week 45 |
2.7 |
Pilot Deployment |
2.5 |
week 45 - week 64 |
3 |
Deployment (done by each UC location) |
|
|
3.1 |
Implement Group Management (Grouper) |
|
? - week 64 |
3.2 |
Implement eduPersonTargetedID |
|
? - week 64 |
3.3 |
If not already done, establish campus policy, procedure, and relationships for brokering requests for identity attributes |
|
? - week 64 |
3.4 |
Integrate Common IAM Interface with local IAM (Snapshot) |
2.6, 3.1, 3.2, 3.3 |
week 65 - week 80 |
3.5 |
Integrate Common IAM Interface with local IAM (Subscription and Change Log) |
2.6, 3.1, 3.2, 3.3 |
week 80 - week 100 |
Resource Assumptions
Core Project Team
Role |
FTE |
|---|---|
Project Management |
1 |
Outreach/Change Management |
1 |
Technical Architect/Lead |
1 |
Software Development |
3 |
Technical Writer / Logistics |
1 |
Total |
7 |
Campus Deployment Resource (per campus)
The campus will likely require between 1 to 3 FTE during phase 3 to complete deployment. The number of FTE required depends on the specific configuration of each campus's identity management infrastructure.