Versions Compared

Old Version 8

changes.mady.by.user Former user

Saved on

compared with

New Version 9

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Iteration Approach Strawman

Each iteration with some minor exception is 12 weeks.

...

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 and Scope

2

Sept - Oct - Nov

 CFS and Contract Management

datacenter inventory apps?
digital-fuel

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:
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?

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 coordinators
  • Closure Document with total budget expended
  • Functionality backlog or technical debt incurred from project