Windows 7 / Getting Started

Envision

The Envision SMF involves envisioning the deployment project and determining goals and expected outcomes. The Envision SMF is largely a management exercise; you don't assemble full project teams until this phase is complete. The Envision SMF includes the following key steps:

  • Set up core teams The initial task is to define the teams that will plan, design, and perform the deployment.
  • Perform a current assessment This step includes identifying existing systems and applications, determining existing operating systems, and identifying deficiencies in the current environment that the Windows 7 deployment will address.
  • Define business goals Concrete, quantifiable business goals should drive your need for the deployment. Rather than simply planning to deploy the latest technology for technology's sake, identify key deficiencies in the existing system that Windows 7 will address, as well as process and productivity gains that the deployment will make possible.
  • Create a vision statement and define the scope Create a vision statement that defines how planned technology changes (including the Windows 7 deployment) will meet the defined business goals. The scope determines the extent of the vision that can be accomplished through the deployment of Windows 7.
  • Create user profiles Develop an accurate and complete picture of users' functions, needs, and wants. Refine these into user profiles that accurately identify the types of users in the organization. Understanding users and what they need is the first step in determining how to structure the deployment to benefit the most users.
  • Develop a solution concept Create a high-level document to define how the team will meet the requirements of the project.
  • Create risk-assessment documents In this step, evaluate the overall deployment with the intent to anticipate, address, mitigate, and prevent risks associated with the deployment. Documentation of risk assessment is an ongoing task throughout the project.
  • Write a project structure This document describes how the team manages and supports the project and describes the administrative structure for the project team. This document should define standards that the team will use, including methods of communication, documentation standards, and change-control standards.
  • Approve milestones When you complete the initial planning and documentation, identify and schedule key milestones for the deployment.

Note MOF 4.0 provides job aids to help complete many of these envisioning steps.

[Previous] [Contents] [Next]