Iteration Approach
Each iteration with some minor exception is 12 weeks.
Each iteration contains the following activities:
week |
SOW |
Stakeholder Analysis |
Requirements |
Design-Build |
Test |
Defect Repair |
Communications |
UAT |
Training |
Deployment |
Overlap to Next Sprint |
---|---|---|---|---|---|---|---|---|---|---|---|
1 |
x |
x |
x |
|
|
|
|
|
|
|
|
2 |
x |
x |
x |
x |
|
|
|
|
|
|
|
3 |
|
|
x |
x |
|
|
x |
|
|
|
|
4 |
|
|
|
x |
|
|
|
|
|
|
|
5 |
|
|
|
x |
x |
|
|
|
|
|
|
6 |
|
|
|
x |
x |
|
|
|
|
|
|
7 |
|
|
|
|
x |
x |
x |
|
|
|
|
8 |
|
|
|
|
x |
x |
|
|
|
|
|
9 |
|
|
|
|
|
x |
|
x |
|
|
|
10 |
|
|
|
|
|
x |
x |
x |
x |
x |
x |
11 |
|
|
|
|
|
|
x |
x |
x |
x |
x |
12 |
|
|
|
|
|
|
x |
|
x |
x |
x |
Business Services
The project scope will include mapping of 5 business services. Each of those business services will have integration work or import requirements:
Iteration |
Dates |
Scope |
Integrations |
Objectives |
---|---|---|---|---|
1 |
Aug- Sept |
Planning Iterations |
None |
Develop Iterations and Scope |
2 |
Sept - Oct - Nov |
CFS and Contract Management |
datacenter inventory apps? |
Datacenter inventory, Contract relationships of end-to-end simple infrastructure business service |
3 |
Dec |
Berlin Upgrade |
None |
Pre-Requisite for Iteration 4 based on the following features: |
4 |
Jan - Feb - March |
Personal Productivity (with top 5 provider services) and Software Asset Management |
BigFix |
Reporting on asset inventory meta data, lifecycle, and software compliance and usage |
5 |
April - May - June |
ServiceNow, Classes v2 and Kronos |
Quickbase |
model cloud service, tie in application inventory, test process for bringing in new business services |
Deliverables for each Iteration
- Milestone Schedule
- Detailed Resource Plan
- ROM estimate for SOWs needed
- Communication and Training plans
- Recommended process changes based on CMDB data
- Functionality backlog or technical debt created during iteration