Chapter 2. The IBM software deployment method
2.4 The software deployment method
2.4.1 Prepare for deployment
The Prepare phase encompasses tasks DM0 through and including DM4.
DM0: Create the software deployment team
The purpose of this task is to:
Form the software deployment team that will plan and lead the deployment.
Obtain commitment from each member and their managers for serving on the team.
Agree on the roles and responsibilities of team members.
Figure 2-5 depicts this task in relation to the overall software deployment method.
Figure 2-5 Task DM0 in relation to the overall software deployment method
Roles and responsibilities
The roles and responsibilities in this task are:
Executive Business Sponsor: No specific role
Program Manager: Leads this task, defines the team and the roles in the team, approaches managers of deployment team members, and obtains resource commitments
Procurement Officer: Agrees on a role and participates
Project Sponsor: Agrees on a role and participates
Project Manager: Agrees on a role and participates
Enterprise IT Architect: Agrees on a role and participates
Project Members: Agrees on a role and participates
IBM Client Executive: Agrees on a role and participates
IBM Enterprise Deployment Manager: Agrees on a role and participates
IBM Software Client Architect: Agrees on a role and participates
Input and output products
Input and output products in this task are:
Input work products: None
Output work products: None
DM1: Review the contract content and other critical
deployment documents
When the software deployment team is defined, the team must learn about the contract content and other items that might influence the deployment. The goal for this task is to understand the contract content, including the terms and conditions:
Products and quantities included in the contract
Possible replacement of products with others and under what conditions
Possible extension of the content under the same conditions
Services that will be included
“Open budget” (value basket)1 included in the contract
Other documents must be reviewed that can have an impact on deployment. For example, a previous deployment plan for existing software on the shelf might need reviewing, as does Solution Review documents (also known as
Technical
and Delivery Assessment
documents), and so on. The Executive Business Sponsor at the client site must be identified. It is also important for IBM to: Discuss and understand your buying decisions
Obtain a preliminary view of how you define success
Determine what value you expect to gain from the partnership
Figure 2-6 depicts this task in relation to the overall software deployment method.
Figure 2-6 Task DM1 in relation to the overall software deployment method
Roles and responsibilities
The roles and responsibilities in this task are:
Executive Business Sponsor: No specific role
1 “Value basket” is terminology used in an enterprise license agreement that represents an available
budget which can be used for new product purchases or services under the predefined Terms and Conditions of the agreement.
Program Manager: Collects and manages all important documents for a successful deployment
Others: Provide the Program Manager with documents; can impact software deployment and enterprise license agreement
Input and output products
The input and output products in this task are:
Input products: Contract and other deployment-related documents
Output products: None
DM2: Understand the projects for deployment
In this task, the software deployment team starts developing a high-level plan in large chunks that can be used to illustrate and justify the software purchase, which includes:
Identifying deployment projects and mapping them to purchased software; identifying demand gaps
Discussing your capabilities, software deployment best practices, and the Software Deployment Readiness Plan
Identifying potential solution review requirements
Using existing enterprise architecture activities or reworking tasks to begin developing an enterprise architecture
Determining potential services requirements
Figure 2-7 depicts this task in relation to the overall software deployment method.
Figure 2-7 Task DM2 in relation to the overall software deployment method
Roles and responsibilities
The roles and responsibilities in this task are:
Executive Business Sponsor: No specific role
Program Manager: Collects all information and documents it in a draft Software Deployment Plan
Procurement Officer: No specific role
Project Sponsor: Provides information about specific projects
Enterprise IT Architect: Provides information about projects
Project Members: No specific role
IBM Client Executive: No specific role
IBM Enterprise Deployment Manager: No specific role
IBM Software Client Architect: No specific role
IBM IT Technical resources (IT Specialists): No specific role
Input and output products
Input and output products in this task are:
Input products: Contract
Output products: Software Deployment Plan (draft)
DM3: Finalize the software deployment plan
The software deployment plan describes the requirements of each stakeholder and deployment project lead. With these requirements incorporated into the plan, it is then finalized, and the details of the kick-off meeting are confirmed.
To assess the requirements of stakeholders and project leads, the following topics are discussed, generally with each person individually:
The strategy to use for addressing open issues with the software deployment best practices and Software Deployment Readiness Plan
Ensure that any areas of concern that were not covered in the selling process are addressed
Confirm or update the list of key stakeholders who jointly own software deployment with the executive business sponsor
Complete planning for deployment kick-off meeting
Figure 2-8 depicts this task in relation to the overall software deployment method.
Figure 2-8 Task DM3 in relation to the overall software deployment method
Roles and responsibilities
The roles and responsibilities in this task are:
Program Manager: Collects all information and documents it in a draft Software Deployment Plan
Procurement Officer: No specific role
Project Sponsor: Provides information about specific project
Project Manager: Provides information about specific project
Enterprise IT Architect: Provides information about projects
Project Members: No specific role
IBM Client Executive: No specific role
IBM Enterprise Deployment Manager: No specific role
IBM Software Client Architect: No specific role
IBM IT Technical resources (IT Specialists): No specific role
Input and output products
The input and output products in this task are:
Input products: Software deployment plan
Output products: Software deployment plan (final or updated)
DM4: Conduct a deployment kickoff meeting
When a software deployment plan is completed, a kickoff meeting is organized for your Executive Business Sponsor, the key stakeholders, and the IBM software deployment team. The purpose of this meeting is for all members to gain a common understanding of the Software Deployment Plan, the goals that must be achieved with the business partnership, and the criteria for success. The topics that are discussed at this meeting are:
The vision for deployment, presented by your Executive Business Sponsor.
A high-level Software Deployment Plan, focusing on quick deployment win projects.
Product overviews and how each product links to the software deployment strategy.
Evangelizing and agreeing upon the Software Deployment Readiness Plan or Plans (see “Readiness plan” on page 29), including business goals, your communication process, training and support plans, and plans for backup and disaster recovery, systems management, migration, rollout, service level agreements, and dependencies.
The transition from sales close to deployment can present difficulties because handoffs and assumptions cannot yet be communicated, and team players might be phasing out as others are phasing in. The IBM Software client team can help
you to put a readiness plan into place that engages the appropriate client team members so that the momentum of a successful sale carries over to deployment. By agreeing on the contents of the Software Deployment Readiness Plan and investing in the components of the kickoff meeting, your investment will pay excellent dividends as you deploy. Your preparation will:
Ensure that you have the right set of expectations to successfully implement the proposed solution
Ensure the IT system lies within the “art of the possible”
Identify issues and risks to be escalated
Figure 2-9 depicts this task in relation to the overall software deployment method.
Figure 2-9 Task DM4 in relation to the overall software deployment method
Roles and responsibilities
The roles and responsibilities in this task are:
Executive Business Sponsor: Participates in the meeting
Program Manager: Organizes the kickoff meeting and supports meeting preparation
Procurement Officer: Supports the meeting preparation and participates
Project Sponsor: Supports the meeting preparation and participates
Project Manager: Supports the meeting preparation and participates
Enterprise IT Architect: Supports the meeting preparation and participates
Project Members: Participate in the meeting
IBM Client Executive: Participates in the meeting
IBM Enterprise Deployment Manager: Participates in the meeting
IBM Software Client Architect: Supports the meeting preparation and participates
Input and output products
The input and output products in this task are:
Input products: Software deployment plan
Output products: Software deployment plan (updated), Software Deployment Tracking Report (initial)