Iteration Approach Strawman
Each iteration with some minor exception is 12 weeks.
...
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 | high level plan |
| high level plan |
|
|
4 |
|
|
| x |
|
|
|
|
|
|
|
5 |
|
|
| x | x |
|
|
|
|
|
|
6 |
|
|
| x | x |
|
|
|
|
|
|
7 |
|
|
| x | x | x x | detailed plan |
|
|
|
|
8 |
|
|
|
| x | x |
|
| detailed plan |
|
|
9 |
|
|
|
|
| x |
| x |
|
|
|
10 |
|
|
|
|
| x x | execute | x x |
| x execute | x |
11 |
|
|
|
|
|
| x | x | x | x | x |
12 |
|
|
|
|
|
| x |
| x | x | x |
Resources Needed | Ed, Bill, Ade, James | Change Mgmt Wendy | BA - Chloe +stakeholders | Bill | qa resource vamshi | bill/vamshi/chloe | change mgmt - wendy | chloe+stakeholders | change mgmt+stakeholders | change mgmt, chloe +stakeholders | ade, james, bill, chloe |
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 (or another Application based business service)
- Clases v2 (or another AITS based business service such as WordPress)
- ServiceNow or Service Management
Iteration or Wave | Dates | Scope | Integrations | Objectives | Expected Outcomes | ||
---|---|---|---|---|---|---|---|
1 | Aug- Sept | Planning Iterations | None | Develop Iterations and Scope iterations, scope and approach including deliverables for Iteration/Wave 2 | Planning Documents for Wave2 | ||
2 | Sept - Oct - Nov | CFS and Contract Management |
| Datacenter inventory, Contract relationships of end-to-end simple infrastructure business service ServiceNow as part of Service Management Business Service |
| Integrate the Quickbase Application inventory, and the datacenter inventory and discovery tools, Build end to end business service map for Classes v2. Model ServiceNow as an end-to-end business service model for a cloud service, tie in application inventory meta data, test process for bringing in new business services. | Base CMDB Model which would provide single view of Application and Data Center inventory. |
3 | Dec | ServiceNow Berlin Upgrade | None | Pre-Requisite for Iteration 4 based on the following features: |
| ||
4 | Jan - Feb - March | Desktop Personal Productivity (with top 5 provider services) and Software Asset Management with IBM PVU pack | Reporting
| BigFix |
| Integrate the BigFix data for Managed Workstation program. Install and Configure the SAM components of SN. Develop specific reporting on asset inventory meta data, lifecycle, and software compliance and usage. Map the Personal Productivity Service with its top 5 provider services as a full end to end business service map. |
|
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 |
...
Central File Service, Contract Management, Kronos, Classes V2 |
| configure Contract Management module and build relationships of end-to-end simple infrastructure business service CFS as full business service map. Map the CI's to the related contracts for this service. Map Kronos (My Time). Map Classes v2 (or another AITS service such as HPC or WordPress) |
|
Deliverables for each Iteration
- Milestone Schedule for iteration
- Updated 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