Transitioning to IT Operations

Article
03/05/2008

The Operations Readiness feature team will rely heavily on the development teams that created the workstation images, USMT process, application packages, network analysis, application-remediation strategies, and hardware inventories to act as escalation contacts for troubleshooting and resolving problems that arise during the deployment. Furthermore, the project Operations Readiness feature team will be largely responsible for managing and confirming the successful transition of the project to IT Operations.

Table 8 lists the roles and responsibilities of the Operations Readiness feature team, its counterpart in an IT operations organization, and the responsibilities that must be handed off.

Note The role of BDD 2007 does not end after the deployment project transitions to IT Operations. The team can maintain the distribution shares to keep them current. For example, computer deployments performed as part of daily operations benefit from having updated device drivers, security updates, core applications, and so on.

Table 8. Role and Responsibility Map Between Project and Production Roles

Deployment role	Operations role	Information transfer
Release Management	Release	Primary transfer point of information, as this is the same role cluster that was involved during desktop deployment
	Infrastructure	Architectures and designs to labs and staging areas
	Operations	Role and account information to the operations role to ensure that accounts and permissions have been set up
	Infrastructure	Feedback to Deployment feature team with respect to the deployment load on operational resources such as the network to balance deployment and operations
	Partner	Standard images for use by hardware vendors to ensure that new computers are delivered in an acceptable preconfigured state
	Security	Standardized security information files used to harden the desktops
Development	Infrastructure	Decision criteria for trade-off decisions with respect to infrastructure
	Support	Feedback from operational support on issues that should be resolved by the development team
	Infrastructure	Standard images, interview information files, and USMT information files
	Security	Standardized security information files used to harden the client computers
Test	Support	List of known issues and quick fixes to the support role
User Experience	Infrastructure	Policies and procedures identified and developed during the course of the deployment project
	Support	Design documentation to the support team to ensure that information is available to the support team
	Operations	Operations policies and procedures identified and developed during the course of the deployment project

Milestone: Transitioning to Operations

Table 9 shows all deliverables and their descriptions that should be completed at the conclusion of this phase.

Milestones are synchronization points for the overall solution. For more information, see the Plan, Build, and Deploy Guide.

Table 9. Deliverables

Deliverable ID	Description
Role and Account Information	This information is given to the operations role to ensure that accounts and permissions have been set up.
Operations Policies and Procedures	This deliverable identifies the policies and procedures developed during the course of the project.

Transitioning to IT Operations

Milestone: Transitioning to Operations

Additional resources