Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

The Practice Deployment Guide Framework to deploy change into organization in a scaleable manner

IP.com Disclosure Number: IPCOM000177064D
Original Publication Date: 2008-Dec-04
Included in the Prior Art Database: 2008-Dec-04
Document File: 6 page(s) / 70K

Publishing Venue

IBM

Abstract

Deployment Guides offer a framework for integrating known best practices for managing change into an end-to-end deployment workflow that supports all team members during all stages of a deployment, including the often overlooked role of the "Change Agent", the person who leads the implementation of a specific change across the organization.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 31% of the total text.

Page 1 of 6

The Practice Deployment Guide Framework to deploy change into organization in a scaleable manner

Disclosed is a framework which offer a standard guideline for integrating known best practices for managing change into an end-to-end deployment workflow that supports team members during all stages of a deployment. The Deployment Guides address all roles involved with the deployment, including the role of "Change Agent" (deployment lead). Deployment Guides include job aids specific to the practice, process, or technology being deployed to enable teams to quickly and easily achieve reproducible results with their deployment.

Inadequacies of Workflow Packages

Workflow software packages exist that allow an organization to define custom workflows. One example is Serena TeamTrack*

                               1, "a highly configurable process & issue management solution that allows you to visualize, orchestrate, and enforce operational processes throughout the enterprise, including those unique to IT or the Application Lifecycle." Another example is salesforce.com's Sales Force Automation** online workflow management system2. A third example is IBM MQ Workflow*** 3. Although these workflow packages enable businesses to specify business process workflows as they interact with systems and people, they are typically not used for many critical aspects of deployment that only occur once. Workflow packages are purchased and customized to address activities that are repeated frequently enough to recoup the cost of the initial investment of creating the custom workflow. Additionally, the workflow does not address "change management" tasks that tend to be treated separately from the workflow.

Overwhelming Content

Workflow-based guidance for the steps of the deployment and ongoing use is important to a successful deployment because teams can be overwhelmed by the resources that are available. Currently, performing an Internet search of "iterative development" results in 4,080,000 hits. Sorting through the available resources and structuring them in a way that aligns with a step-by-step "cookbook" workflow can be time-consuming and error-prone.

Problems with Task-based Approaches

Currently, solutions exist that will enable individuals to perform specific tasks related to the phases of a deployment. As one example, software typically comes with an installation manual, a user's guide, an administrator's guide technical references, marketing collateral and architectural/design references4. Documentation helps members of an organization to complete discrete tasks related to phases (install, configure, use) of the deployment; however, the documentation does not provide a

1

Page 2 of 6

"workflow" view of all activities required to successfully deploy the software within a

organization. Educational courses typically support a particular audience (a particular group i...