The BDD solution includes guidance (feature team guides) and planning templates for the various teams that participate in a desktop deployment project. Table 1 describes the feature team guides and planning templates that each participating team uses during the project. The sections called “The Feature Team Guides” and “The Templates” describe each document and template. Table 1. Feature Teams, Guidance, and Templates Core | | • | Plan, Build, and Deploy Guide | | • | Trey Site Deployment Project Plan | | • | Test Feature Team Guide | | • | Trey Upper MORG IT Archetype |
| | • | Trey Functional Specification | | • | Trey Migration Plan | | • | Trey Pilot Plan | | • | Trey Risk Template Tool | | • | Trey Test Plan | | • | Trey Test Specification | | • | Test Cases Workbook | | • | Trey Training Plan | | • | Trey Vision Scope |
| Application Compatibility | | • | Application Compatibility Feature Team Guide |
| | • | Trey Client Build Requirements | | • | Application Knowledge Sheet |
| Computer Imaging System | | • | Computer Imaging System Feature Team Guide |
| | Core Applications | | • | Core Applications Feature Team Guide |
| | Deployment | | • | Lite Touch Deployment Feature Team Guide |
| | Infrastructure Remediation | | • | Infrastructure Remediation Feature Team Guide |
| | • | Trey Communications Plan | | • | Inventory Template | | • | Trey Network and Workstation Hardware Upgrades List | | • | Assessment Template | | • | Current State Assessment Template |
| Office Upgrade | | • | Plan, Build, and Deploy Guide for Office Upgrades | | • | Office Upgrade Feature Team Guide |
| | • | Office Upgrade Assessment Template | | • | Office Upgrade Budget Plan | | • | Office Upgrade Communications Plan | | • | Office Upgrade Configuration Plan | | • | Office Upgrade Current State Assessment Template | | • | Office Upgrade Distribution Plan | | • | Office Upgrade File Migration Plan | | • | Office Upgrade Functional Specification | | • | Office Upgrade Hardware Upgrades List | | • | Office Upgrade Inventory Template | | • | Office Upgrade Management Plan | | • | Office Upgrade Pilot Plan | | • | Office Upgrade Project Plan | | • | Office Upgrade Risk Template Tool | | • | Office Upgrade Test Plan | | • | Office Upgrade Training Plan | | • | Office Upgrade Vision Scope |
| Operations Readiness | | • | Operations Readiness Feature Team Guide |
| | Security | | • | Security Feature Team Guide |
| | Supplemental Applications | | • | Supplemental Applications Feature Team Guide |
| | User State Migration | | • | User State Migration Feature Team Guide |
| |
The Feature Team GuidesThe BDD solution includes the following 13 guides: | • | Plan, Build, and Deploy Guide. Provides the framework for managing and monitoring the solution as it progresses through its life cycle. Managers and the technical leads on the project are this document’s principal readers. They should review it before reading any other solution documentation. All team members are encouraged to read it, however, because it provides an overview of the deployment process. | | • | Plan, Build, and Deploy Guide for Office Upgrades. Provides the framework for managing and monitoring an Office 2003 Editions upgrade as the project progresses through its life cycle. Managers and the technical leads on the project are this document’s principal readers. They should review it before reading any other solution documentation. All team members are encouraged to read it, however, because it provides an overview of the deployment process. | | • | Test Feature Team Guide. Describes how to plan and test the solution. This guide describes testing best practices for the solution and how to set up a test lab for it. | | • | Application Compatibility Feature Team Guide. Focuses on inventorying the current computers and testing the compatibility of applications with Windows XP. This guide is technical in nature. | | • | Supplemental Applications Feature Team Guide. Targets the team responsible for scripting or packaging applications for the hands-free installation and configuration on the new Windows XP-based computer. This guide is technical in nature. | | • | Infrastructure Remediation Feature Team Guide. Describes how to assess the current computer hardware for determining hardware upgrade requirements and how to analyze the network for any limitations or constraints that may impact the deployment. This guide is semi-technical in nature. | | • | Operations Readiness Feature Team Guide. Targets the people who manage the IT operations environment. It provides guidance on how to integrate the IT operations requirements into the overall deployment process. This guide is technical in nature. | | • | Security Feature Team Guide. Focuses on how to assess computer security requirements. It provides guidance on how to integrate security requirements into the imaging and deployment process. This guide is technical in nature. | | • | User State Migration Feature Team Guide. Describes how to identify users’ data files on their current desktops, save them, and restore them to the new computer image. This guide is technical in nature. | | • | Office Upgrade Feature Team Guide. Describes how to customize and deploy an Office 2003 Editions upgrade to computers that are already running Windows XP Professional. This guide is semi-technical in nature. | | • | Core Applications Feature Team Guide. Targets the team responsible for assisting in the planning, deployment, and migration of business desktops to Office 2003 Editions. This guide is semi-technical in nature. | | • | Computer Imaging System Feature Team Guide. Focuses on creating computer images of Windows XP. It includes comprehensive guidance on how to implement, customize, and operate the automated imaging process that is included in the BDD solution. This guide is technical in nature. | | • | Deployment Guide. Targets the people responsible for executing computer deployments. It provides information on server placement and capacity planning as well as specific information on the deployment tools and the deployment processes. This guide is technical in nature. |
Ideally, all project members will start by reading the Plan, Build, and Deploy Guide so that they will be aware of all the components of the project and how they interact. Once this has been done, the next step is for members to review the specific feature team guides that are appropriate for their roles on the project. Most of these guides contain four major sections: “Plan,” “Develop,” “Stabilize,” and “Deploy.” The “Plan” section describes how to prepare for using the guidance. The “Develop” section provides guidance for building a particular component of the solution. The “Stabilize” section provides information about testing and verifying the component, and the “Deploy” section describes how to release the component as part of the larger solution. The TemplatesThe solution includes several templates that will help manage the project. Table 1 associates each template with the feature team and guidance that uses it: | • | Application Knowledge Sheet. Provides a template for recording application information. | | • | Assessment Template. Provides a template for recording infrastructure information. | | • | Current State Assessment Template. Describes and assesses the current infrastructure. | | • | Inventory Template. Provides a template for recording software and hardware inventory. | | • | Test Cases Workbook. Provides a template for recording the results of test cases. | | • | Trey Client Build Requirements. Provides a template for recording the required client configuration, including operating system and core applications configurations. | | • | Trey Communications Plan. Describes how to communicate project status and information to the organization and outside the organization. | | • | Trey Functional Specification. Provides an overview of the project’s requirements. | | • | Trey Migration Plan. Describes what will be migrated during the deployment. | | • | Trey Network and Workstation Hardware Upgrades List. Provides a template for recording the necessary network and computer hardware upgrades. | | • | Trey Pilot Plan. Describes how to pilot-test the project in the organization. | | • | Trey Risk Template Tool. Describes and assesses the top risks to the project. | | • | Trey Test Plan. Explains how and when the project team will communicate to the end users and management. | | • | Trey Test Specification. Describes how to test the project. | | • | Trey Training Plan. Tells how, when, and what types of training will be provided. | | • | Trey Vision Scope. Outlines the overall project objectives and responsibilities. Note This solution provides a comparable set of templates for Office 2003 Editions upgrades. The file names of these templates begin with Office Upgrade. |
| |