The Execute phase encompasses tasks DM5 through and including DM8.
DM5: Prepare and present the software deployment readiness
plan
The IBM software deployment team prepares and presents the Software
Deployment Readiness Plan or Plans based on the IBM products that are new to your organization. This supports your initiative and ensures that you are
prepared for upcoming projects.
Figure 2-10 depicts this task in relation to the overall software deployment method.
Figure 2-10 Task DM5 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 the preparation of the Software Deployment Readiness Plan
Procurement Officer: No specific role
Project Sponsor: No specific role
Project Manager: Supports the preparation of, and receives, the Software Deployment Readiness Plan
Enterprise IT Architect: Supports the preparation of, and receives, the Software Deployment Readiness Plan
IBM Client Executive: No specific role
IBM Enterprise Deployment Manager: Supports the preparation of the Software Deployment Readiness Plan
IBM Software Client Architect: Supports the preparation of, and receives, the Software Deployment Readiness Plan, and prepares and executes the Software Deployment Readiness Plan
IBM IT Technical resources (IT Specialists): Prepare and execute the Software Deployment Readiness Plan
Input and output products
The input and output products in this task are:
Input products: None
Output products: Software Deployment Readiness Plan
DM6: Execute quick deployment wins
This important task is to execute projects that are what we call
quick deployment
wins
, as discussed in the Software Deployment Plan. A quick deployment win is a demonstration of the capabilities and flexibilities of our deployment methods over time. For example, you and IBM might define a 60 to 90-day project using our products and processes to demonstrate our deployment methods. The immediate objective here is to instill confidence in your organization about our products and processes. As an overall objective, we want to produce aconfidence level in you, based on your seeing, first-hand, that our methods are credible, reliable, and successful.
The key activities in this task are:
Execute quick deployment win projects
Conduct regular meetings with your project owners
Monitor the resolution of software deployment best practices and Software Deployment Readiness Plan shortfalls
Figure 2-11 depicts this task 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 the preparation of the Software Deployment Readiness Plan
Procurement Officer: No specific role
Project Sponsor: Supports and monitors the success of the project
Project Manager: Leads the project
Enterprise IT Architect: Provides direction and enforces standards
Project Members: Participate in implementing a project
IBM Client Executive: Validates success and satisfaction
IBM Enterprise Deployment Manager: Supports the project
IBM Software Client Architect: Supports the project
IBM IT Technical resources (IT Specialists) Support the project
Input and output products
The input and output products in this task are:
Input products: List of selected projects for deployment quick wins and the architecture and Statement of Work (SoW) for those projects
Output products: Software Deployment Tracking Report
DM7: Execute and monitor the deployment plan
This is the longest task and, in reality, does not end because the status of the shelf-ware from the initial contract can be used in a project from the next
contract. The purpose of this task is to help achieve the goals of the contract and to receive maximum value from the IBM software and hardware purchase. Monitoring the progress of the deployment along with the deployment plan must occur regularly, perhaps monthly, or as defined. IBM support is involved in this too in the event that there are issues or potential issues. If there are changes to the project plan, project content, or owners, immediately update the software deployment plan accordingly. The success of software and hardware deployment also depends on technical and other issues that are faced by the implementation team during the course of the project. Therefore, the software deployment team must fully support the resolution of project issues.
When starting a new project, it is important to understand what will occur if:
A solution review needs to be executed
An additional Software Deployment Readiness Plan needs to be prepared based on project content changes
When a project is completed, it must be ensured and verified that all project goals are met, at which time the Software Tracking Report is updated. Figure 2-12 depicts this task in relation to the overall software deployment method.
Figure 2-12 Task DM7 in relation to the overall software deployment method
Roles and responsibilities
The roles and responsibilities in this task are:
Executive Business Sponsor: Supports and drives any escalation and supports problem resolution during the project
Program Manager: Monitors the software deployment progress against the plan, identifies needs, and leads the solution review and the Software Deployment Readiness Plan. Leads (together with a Project Manager and the IBM Enterprise Deployment Manager) problem resolution of technical and other issues
Procurement Officer: Controls license use
Project Sponsor: Supports and monitors project success
Project Manager: Leads projects and manages problem resolution
Enterprise IT Architect: Provides direction and enforces standards
Project Members: Perform project implementation, if agreed to with the client, and provides input on deployment progress to the Deployment Technical Lead, where applicable
IBM Client Executive: Supports and drives any escalation and supports problem resolution during the project
IBM Enterprise Deployment Manager: Leads solution review and the Software Deployment Readiness Plan. Co-leads (together with a Program Manager and Project Manager) problem resolution of technical and other issues
IBM Software Client Architect: Supports the project
IBM IT Technical resources (IT Specialists): Supports the project
Input and output products
The input and output products in this task are:
Input products: Software deployment plan, Software Deployment Tracking Report
Output products: Software deployment plan (updated), Software Deployment Tracking Report (updated)
DM8: Manage project and solution changes
Multiple changes can occur during project execution, which can influence project priorities and the utilization of purchased hardware and software licenses. Any change requires impact analysis, an investment protection plan for purchased hardware and software, a clear definition of additional needs, and an update to the software deployment plan.
Figure 2-13 depicts this task in relation to the overall software deployment method.
Figure 2-13 Task DM8 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: Controls and documents changes
Procurement Officer: Controls license use
Project Sponsor: No specific role
Project Manager: Manages changes and the impact of changes on the project and overall costs
Enterprise IT Architect: Provides direction and enforces standards; updates and manages the Enterprise Architecture
Project Members: Provide suggestions
IBM Enterprise Deployment Manager: Manages the IBM client team to provide recommendations for potential changes
IBM Software Client Architect: Supports the project and provides recommendations
IBM IT Technical resources (IT Specialists): Support the project and provide recommendations
Input and output products
The input and output products in this task are:
Input work products: None
Output work products: Software deployment plan (updated), Software Deployment Tracking Report (updated), Change Management or Substitution report