Note  This article describes a Project template. You can download this template by clicking the link in the See Also list in this article.

The objective of this template is to identify and correlate the activities required for the full project life cycle of a software deployment process in terms of a software installation (i.e., Project 2003, Microsoft Office System, or Microsoft Exchange). The template is designed to focus on the required steps and processes to successfully initiate, design, and deploy a new software deployment.

Template design

The software deployment template defines the steps and dependencies within a project to initiate, design, and deploy new software. The template can be scaled from a small simple product local area network solution to an enterprise wide area network. The template is based on a phased methodology, which uses phase completion milestones as a mechanism for reporting. It can be customized with additional milestones and deliverables as appropriate. The template is organized into seven key phases: scope, analysis, design, budget, finalization/validation, deployment, and post-implementation review. Each phase contains the associated activities and their respective dependencies. The activities are generic and may require editing to fit your particular environment or methodology. The template includes the four phases outlined in the process model: vision/scope, planning, deployment, and post-implementation. Each phase contains numerous subtasks and culminates in a milestone event; however, specific tasks within a phase may overlap the milestone and extend into the next phase.

Tasks are assigned typical durations, dependencies, and resource allocations, which may be edited to suit the specific project.

The following sections present an overview of the four phases of the process model, a description of the resources that make up a typical team, and a summary of major tasks.

Template description

Phase 1: Vision/Scope

In the vision/scope phase, you create a high-level view of the project's goals and constraints. This phase is an early planning process that sets the stage for the process that will take place during the formal planning phase of the project. Vision/Scope addresses one of the most fundamental needs for project success: unifying the team. A clearly defined scope is imperative for any deployment process and will often actually define whether a project proceeds or is cancelled based upon its business value.

Phase 2: Planning

The planning phase provides an opportunity to establish priorities and set expectations. After scope is defined and a project sponsor is identified, the project can continue with a more detailed yet still high-level analysis. The objective of this phase is to detail the current deployment and areas that require improvement and to identify sources to provide assistance in architectural, material, etc. It is important to note that the analysis is influenced by the current business goals and direction. This direction, in turn, may prioritize the sequence of deployment.

Phase 3: Deploying

During deployment, the team strives to deploy and implement all features, even if they are not stable. The deployment team joins with user education and testing to focus on implementing the product and works with testing to ensure reliability from one internal release to the next.

Phase 4: Post-Implementation Review

By entering the post-implementation review phase, the team shifts its focus by obtaining feedback and evaluating the project. The post-implementation review phase culminates with the complete deployment of the product.