Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

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:

  1. Central File Service (CFS)
  2. Personal Productivity (and top 5 provider services)
  3. Kronos
  4. Clases v2
  5. ServiceNow

Iteration

Dates

Scope

Integrations

Objectives

1

Aug- Sept

Planning Iterations

None

Develop iterations, scope and approach

2

Sept - Oct - Nov

 Central File Service and Contract Management

datacenter inventory apps?
digital-fuel

Integrate the datacenter inventory or tools (or discovery or wherever we have this info), 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.  We may also want to tie this back to Digital Fuel, so the SN contracts can be associated with contracts in Digital Fuel.  If Digital Fuel is not yet production, we might defer this scope item

3

Dec

Berlin Upgrade

None

Pre-Requisite for Iteration 4 based on the following features:

Defining asset bundles, enhanced product definitions, detailed status tracking, and automated stock rules for consumable inventory, software entitlements, software suite definitions, enterprise licenses, subscription licenses, upgrading/downgrading licenses, usage-based licenses, software counters, manage software that is licensed under the IBM Processor Value Units licensing model

4

Jan - Feb - March

Personal Productivity (with top 5 provider services) and Software Asset Management with IBM PVU pack

BigFix

HIPAA database?

software library?

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. 

Unsure if its a reach here to also integrate back into the HIPAA database so that the SN endpoint data becomes an authoritative source for it

Unsure if the software library also needs to integrated to track downloads of certain software

5

April - May - June

ServiceNowClasses 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
  • No labels