Iteration Approach Strawman
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 |
|
|
high level plan |
|
high level plan |
|
|
4 |
|
|
|
x |
|
|
|
|
|
|
|
5 |
|
|
|
x |
x |
|
|
|
|
|
|
6 |
|
|
|
x |
x |
|
|
|
|
|
|
7 |
|
|
|
x |
x |
x |
detailed plan |
|
|
|
|
8 |
|
|
|
|
x |
x |
|
|
detailed plan |
|
|
9 |
|
|
|
|
|
x |
|
x |
|
|
|
10 |
|
|
|
|
|
x |
execute |
x |
|
execute |
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:
- Central File Service (CFS)
- Personal Productivity (and top 5 provider services)
- Kronos
- Clases v2
- ServiceNow
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 with IBM PVU pack |
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 for iteration
- Detailed Resource Plan for iteration
- ROM estimate for SOWs needed
- Stakeholder Analysis for iteration
- Functionality backlog or technical debt created during iteration
- Review of total budget expended to date
- Status Reporting at weeks 3, 6, 9 and 12
Deliverables at project end
- CMDB documented data architecture and data dictionary
- Recommendations for changes to ITSM Processes based on CMDB data
- Documented processes on mapping additional business services - provider services and CI's
- Documented processes on mapping additional contracts and software licenses to CI's
- Documented processes on maintaining all CMDB classes
- Documented communication channel to engage CMDB coordinators
- Closure Document with total budget expended
- Functionality backlog or technical debt incurred from project