Integration Management Ensuring Design Integrity from Requirements through Release

1
Integration ManagementEnsuring Design Integrity
from Requirements through Release

• Presented By Jim Testa

2
Overview

• What is Integration Management (IM) and Why Do
  You Need It?
• Where IM Fits in the Project Structure
• IMs Charter
• IMs Functions
• IMs Operating Model
• Things IM Does Not Do
• Summary

3

• Integration Management

4
What is Integration Management?
Requirements
Functional Design
Information Technology
Business Intelligence
Integration Management provides the Governance to
ensure the integrity of the solution Design from
Requirements to Release
User Training
Issue Management
Change Control
CRP Process
Change Control
Release Management
UAT Process
Release
5
Why Do You Need IM?

• IM helps avoid the typical project icebergs such
  as
• Key design issues that fall through the cracks
• Scope creep
• Siloed and disconnected designs
• Incomplete testing
• Incomplete releases
• Redundant activities
• Inconsistent milestones
• . . .

6
Where Does IM Fit?
7
Where Does IM Fit?

• Design Governance
• Requirements Management
• Business/Systems Integration
• Dependency Management
• Cross-functional Issue Management
• Scope and Configuration Change Control
• Release Management
• Deployment Planning
• Testing Management

8
IMs Charter

• The Integration Management Teams charter
  includes
• Coordinating across functional teams so that key
  design elements, business decisions, application
  decisions, process designs and issue resolutions
  are integrated communicated
• Planning and coordinating the testing and
  verification of the Innovate processes and
  systems
• Establishing and executing the change control
  process for scope, requirements and system
  configuration
• Preparing and releasing the Innovate solution to
  the country deployment teams
• Generally serving as the point-of-contact between
  the functional, technology and deployment teams
  for issues and requirements
• Generally serving as the point-of-contact between
  the program and external initiatives

9
IM Functions

• Integration Management is composed of four
  functions
• Design Integration
• Testing Verification
• Scope Configuration Change Control
• Release Management

10
IM Functions Design Integration

• IM provides
• A standardized process for large groups to
  rapidly reach integrated design decisions that
  affect the entire Innovate project team
• A cross-functional view of the E2E business
  processes
• Global application role definition
• Integrated design guidance to the project team

• Activities include
• Conducting integration events and meetings (e.g.
  E2E Simulation, GBT/IT Integration)
• Facilitating and coordinating the identification
  of Design Sessions for the integrated GIF design
• Coordinating the development/identification of
  global end-user application roles
  responsibilities
• Coordinating the creation of the Cross-Functional
  E2E Process Master
• Coordinating the development of site data
  requirements and facilitating data gathering
• Reviewing the eProjectWeb issues database for
  potential cross-team issues
• Facilitating cross-team issue resolution
• Validating that the GIF design supports the
  Innovate vision and business benefits
• Facilitating cross-initiative integration

• IM needs from each team
• Continued cooperation and participation to drive
  out the E2E design details and decisions
• Commitment to think globally
• Commitment to be accountable for their decisions
• Commitment to raise issues, no matter how
  simplistic they seem

11
IM Functions Testing Verification

• IM provides
• Overall TV strategy, methodology and schedule
• For each CRP/UAT, the scope, objectives,
  schedule, logistics, and preparation/execution
  management
• A consistent and repeatable process for CRP/UAT
  preparation
• E2E integration test cases/scripts development
  coordination and execution coordination
• CRP/UAT results communication and quality audit

• Activities include
• Developing the Innovate testing and verification
  strategy
• Defining the scope and objectives for each
  CRP/UAT
• Planning and coordinating CRP/ UAT physical
  facilities and logistics
• Defining requirements, organizing and
  coordinating preparation of inputs for CRP/UAT
• Coordinating assignment of application user
  responsibilities and creation of user logons in
  the CRP/UAT environments
• Managing creation and execution of the E2E
  integrated test cases
• Monitoring, tracking and communicating CRP/UAT
  results

• IM needs from each team
• Commitment to follow the process and schedules
  defined
• Quality CRP/UAT inputs, outputs and execution
• Definition of participants and formal
  communication of their CRP/UAT role
• Commitment to provide a Testing Coordinator for
  each CRP/UAT
• End-to-End Process Owners to coordinate execution
  of the E2E integrated tests for their process(es)
• Commitment to provide the functional participants
  required to execute the E2E integrated tests
• Commitment from Information Technology to
  create/maintain environments and provide
  technical support as requested throughout CRP/UAT
  preparation and execution efforts

12
IM Functions Scope Configuration Change Control

• Activities include
• Establishing and executing the Change Control
  process and standards
• Defining the Change Control Board charter and
  coordinating its activities
• Coordinating the collection, review and approval
  of change requests
• Tracking and coordinating the implementation of
  approved change requests through development, the
  functional teams, testing, and release management
  
• Coordinating update of the Cross-Functional E2E
  Process Master
• Validating that completed changes are ready for
  release to production

• IM provides
• A standardized governance process for monitoring
  and controlling the Innovate scope and
  environment
• A standardized approach to documenting,
  justifying and adjudicating change requests
• Communication to the appropriate parties
  regarding change requests that may have
  cross-functional impact
• Tracking of approved changes to ensure
  appropriate handoff to the development, testing,
  release and deployment functions
• Tracking of approved changes to ensure updates of
  the E2E Process Master

• IM needs from each team
• Commitment to follow the defined process
• Commitment to review change requests before
  submission to validate their appropriateness and
  qualify their value to Innovate
• Time commitment from each Change Control Board
  member to execute the responsibilities defined

13
IM Functions Release Management

• IM provides
• A standardized governance process defining and
  controlling each Innovate release
• Communication with the appropriate parties to
  collect and disseminate details about each
  Innovate release details to allow for appropriate
  planning and execution
• Tracking of each release through the deployment
  process to ensure a smooth and complete
  implementation

• Activities include
• Establishing and executing the Release Management
  strategy, process and standards
• Coordinating with Functional Teams and IT
  Development to define the contents of each
  Innovate release
• Monitoring construction and preparation of each
  Innovate release
• Coordinating with the deployment sites to ensure
  localization requirements are met in each release
• Coordinating promotion to production of approved
  change requests within releases

• IM needs from each team
• Commitment to follow the defined process
• Commitment to provide release-related information
  in a timely manner

14
Integration Managements Operating Model
IM Team Lead
Admin
Design Integration
Testing Verification
Work Cycle
The IM Team
Scope ConfigurationChange Control
Release Management
15
Things Integration Management Does Not Do

• Design processes (IM coordinates the design
  effort and ensures the processes are integrated)
• Approve Functional or Technical Specs
• Determine what will or will not be developed by
  IT Application Development (IM serves as a tie
  breaker and helps ensure proper prioritization)
• Configure applications (IM does coordinate the
  configuration efforts related to CRP/UATs)
• Determine who should or should not participate in
  CRP/UATs (IM provides guidelines for determining
  participation)
• Define or create CRP/UAT unit tests (IM will take
  the lead on coordinating integrated testing
  scenarios with support from the functional teams)
• Define or create application user
  responsibilities or menus
• Create or activate application user logons
• Provide source control for development items

16
Summary

• IM exists on successful projects (whether you
  realize it or not)
• IM plays a key role in risk mitigation
• Keeps the functional teams focused on the common
  design goal
• Establishes structure and rigor around testing,
  change control and the release processes
• Fosters communication and integrated thinking for
  cross-functional issues
• IM drives efficiency into the project by
  eliminating duplicate activities
• IM Serves and Protects

17
Questions?
18
CONTACT INFORMATION
Jim Testa Jtesta_at_kpmg.com
Thank You!
For more information about how KPMG Consulting
can help your organization, please contact Jim
Testa at [phone] or Fred Martin at (312)
665-8821 Visit our website at
www.kpmgconsulting.com