<<Project Name>>

Vision/Scope
Customer Name
Directions for using template:
Read the Guidance (Arial blue font in brackets) to understand the information that
should be placed in each section of this template. Then delete the Guidance and
replace the placeholder within <<Begin tet here!! with "our response. There ma" be
additional Guidance in the Appendi of some documents# which should also be
deleted once it has been used.
$ome templates ha%e four le%els of headings. The" are not indented# but can be
differentiated b" font t"pe and si&e:
• 'eading ( ) Arial Bold (* font
• 'eading + ) Arial Bold ,talic (- font
• 'eading . ) Arial Bold (. font
• 'eading . ) Arial Bold ,talic (+ font
/ou ma" elect to indent sections for readabilit".
Author
Author 0osition
1ate
2ersion: (.3
345+35+3(-

© 2002 Microsoft Corporation. All rights reserved.
The information contained in this document represents the current view of Microsoft Corporation on the issues
discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not
be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accurac of an
information presented after the date of publication.
This document is for informational purposes onl. MICROSOFT MAKES NO ARRANTIES! E"PRESS OR
IMP#IE$! IN T%IS $OC&MENT'
Microsoft and !isual Basic are either registered trademarks or trademarks of Microsoft in the "nited #tates and$or
other countries.
345+35+3(-

Revision & Sign-off Sheet
6hange Record
1ate Author 2ersion 6hange Reference
Re%iewers
7ame 2ersion Appro%ed 0osition 1ate
1istribution
7ame 0osition
1ocument 0roperties
,tem 1etails
1ocument Title 2ision5$cope
Author
6reation 1ate
8ast 9pdated
345+35+3(-

Table of Contents
Business :pportunit"......................................................................................................
:pportunit" $tatement.................................................................................................
2ision $tatement..........................................................................................................
Benefits Anal"sis.........................................................................................................
$olutions 6oncept...........................................................................................................-
Goals# :b;ecti%es# Assumptions# and 6onstraints......................................................-
9sage Anal"sis...........................................................................................................<
9ser 0rofiles...........................................................................................................<
9sage $cenarios......................................................................................................<
Re=uirements..............................................................................................................<
Business Re=uirements...........................................................................................*
9ser Re=uirements.................................................................................................*
:perational Re=uirements......................................................................................*
$"stem Re=uirements.............................................................................................*
$cope..............................................................................................................................*
>eature5>unction 8ist..................................................................................................*
:ut of $cope...............................................................................................................*
2ersion Release $trateg"............................................................................................4
Acceptance 6riteria....................................................................................................4
:perational 6riteria....................................................................................................4
$olution 1esign $trategies.............................................................................................?
Architectural 1esign $trateg"....................................................................................?
Technical 1esign $trateg"..........................................................................................?
345+35+3(- (
%Intro(uction to t)e Temp*ate
$escription& The !ision$#cope document represents the ideas and decisions
developed during the envisioning phase. The goal of the phase, represented b the
content of the documentation, is to achieve team and customer agreement on the
desired solution and overall pro'ect direction.
The !ision$#cope document is organi(ed into four main sections&
• Business )pportunit& a description of the customer*s situation and needs
• #olutions Concept& the approach the pro'ect team will take to meet the
customer*s needs
• #cope& the boundar of the solution defined though the range of features and
functions, what is out of scope, a release strateg, and the criteria b which the
solution will be accepted b users and operations
• #olution +esign #trategies& the architectural and technical designs used to create
the customer*s solution
+usti,ication& !ision$#cope documentation is usuall written at the strategic level of
detail and is used during the planning phase as the conte,t for developing more
detailed technical specifications and pro'ect management plans. -t provides clear
direction for the pro'ect team. outlines e,plicit, up/front discussion of pro'ect goals,
priorities, and constraints. and sets customer e,pectations.
Team Ro*e Primar-& Pro(uct Mana.ement is the ke driver of the envisioning
phase and responsible for facilitating the team to the !ision$#cope approved
milestone. 0roduct Management defines the customer needs and business
opportunit or problem addressed b the solution.
Team Ro*e Secon(ar-& Pro.ram Mana.ement is responsible for articulating the
#olution Concept, 1oals, )b'ectives, Assumptions, Constraints, #cope, and #olution
+esign #trategies sections of this document.23
345+35+3(- +
/usiness Opportunit-
%$escription& The Business )pportunit section contains the statement of the
customer*s situation. -t is e,pressed in business language, not technical terms. This
section should demonstrate Microsoft*s understanding of the customer*s current
environment and its desired future state. This information is the overall conte,t for the
pro'ect.3
Opportunity Statement
%$escription& The )pportunit #tatement section describes the customer*s current
situation that creates the need for the pro'ect. -t ma contain a statement of the
customer*s opportunit and the impact of capitali(ing on that opportunit 4product
innovation, revenue enhancement, cost avoidance, operational streamlining,
leveraging knowledge5. -t ma contain a statement of the customer*s problem and the
impact of solving the problem 4revenue protection, cost reduction, regulator
compliance, alignment of strateg and technolog5. -t should include a statement that
connects the customer*s opportunit$problem to the relevant business strateg and
drivers. The )pportunit #tatement is written concisel using a business e,ecutive*s
voice.
+usti,ication& The )pportunit #tatement demonstrates that Microsoft understands
the customer*s situation from the business point of view and provides the pro'ect
team and other readers with the strategic conte,t for the remaining sections.3
<<Begin tet here!!
Vision Statement
%$escription& The !ision #tatement section clearl and concisel describes the
future desired state of the customer*s environment once the pro'ect is complete. This
can be a restatement of the opportunit. however, it is written as if the future state
has alread been achieved. This statement provides a conte,t for decision/making. -t
should be motivational to the pro'ect team and the customer.
+usti,ication& A shared !ision #tatement among all team members helps ensure that
the solution meets the intended goals. A solid vision builds trust and cohesion among
team members, clarifies perspective, improves focus, and facilitates decision/
making.3
<<Begin tet here!!
Benefits Analysis
%$escription& The Benefits Analsis section describes how the customer will derive
value from the proposed solution. -t connects the business goals and ob'ectives to
the specific performance e,pectations reali(ed from the pro'ect. These performance
e,pectations should be e,pressed numericall. This section could be presented using
the following subsections&
• Business 1oals and )b'ectives
345+35+3(- .
• Business Metrics
• Business Assumptions and Constraints
• Benefits #tatement
+usti,ication& Benefits Analsis demonstrates that Microsoft sufficientl understands
the customer*s situation. -t also defines the customer*s business needs, which ma
provide vital information for making solution$technolog recommendations.3
<<Begin tet here!!
So*utions Concept
%$escription& A #olutions Concept provides a general description of the technical
approach the pro'ect team will take to meet the customer*s needs. This includes an
understanding of the users and their needs, the solution*s features and functions,
acceptance criteria, and the architectural and technical design approaches.
+usti,ication& The #olution Concept provides teams with limited but sufficient detail
to prove the solution to be complete and correct. to perform several tpes of analses
including feasibilit studies, risk analsis, usabilit studies, and performance analsis.
and to communicate the proposed solution to the customer and other ke
stakeholders.3
Goals, Obe!tives, Assumptions, an" Constraints
[#es!ription: The Goals, Objectives, Assumptions, and Constraints section contains
the following components that define the product’s parameters:
• Goals the product’s final purpose or aim!
• Objectives the goals bro"en into measurable components!
• Assumptions factors considered true, real, or certain that are awaiting
validation!
• Constraints a nonfunctional re#uirement that will limit the product!$
Assumptions and Constraints ma be derived from the product*s functionalit, as well
as research regarding the customer*s environment.
+usti,ication& The 1oals and )b'ectives articulate both the customer*s and team*s
e,pectations of the solution and can be converted into performance measurements.
Assumptions attempt to create e,plicit information from implicit issues and to point
out where factual data is unavailable. Constraints place limits on the creation of
boundaries and decision/making.3
<<Begin tet here!!
$sage Analysis
%$escription& The "sage Analsis section lists and defines the solution*s users and
their important characteristics. -t also describes how the users will interact with the
solution. This information forms the basis for developing re6uirements.3
345+35+3(- -
&ser Pro,i*es
%$escription& The "ser 0rofile describes the proposed solution*s users and their
important characteristics. The users are identified in groups 7usuall stated in terms
of their functional areas. )ften users are from both the -T 4help desk, database
administration, etc.5 and business 4accounting, warehouse, procurement, etc.5 areas
of the customer*s organi(ation. The important characteristics identif what the users
are doing that the solution will facilitate. These characteristics can be e,pressed in
terms of activities& for e,ample, the accounting user receives invoices and makes
paments to suppliers.
This section should contain a level of user profile information that enables the
identification of uni6ue re6uirements.
+usti,ication& -nitiall, "ser 0rofiles enable the development of usage scenarios
4ne,t section5. Beond that, "ser 0rofiles provide the pro'ect teams with vital
re6uirements information. A complete set of "ser 0rofiles ensures that all high/level
re6uirements can be identified. The product team uses these profiles as input when
developing the 8eature$8unction 9ist. The development team uses these profiles as
input to its architecture and technolog design strategies. The user education team
uses these profiles to establish the breadth of their work.3
<<Begin tet here!!
&sa.e Scenarios
%$escription& "sage #cenarios define the se6uences of activities the users perform
within the proposed solutions environment. This information is comprised of a set of
ke events that will occur within the users* environment. These events should be
described b their ob'ectives, ke activities and their se6uences, and the e,pected
results.
+usti,ication& "sage #cenarios provide vital information to identif and define the
solution*s user and organi(ational re6uirements, the look and feel of user interfaces,
and the performance users e,pect of the solution.3
<<Begin tet here!!
Re%uirements
%$escription& :e6uirements identif what the solution must do. These :e6uirements
can be e,pressed in terms of functionalit 4for e,ample, a registration ;eb site
solution will allow the users to register for events, arrange for lodging, etc.5 as well as
the rules or parameters that appl to that functionalit 4for e,ample, the user can onl
register once, and must sta in lodging approved b the travel department5.
:e6uirements e,ist at both the user level and the organi(ational level.
+usti,ication& "ser and )rgani(ational :e6uirements are the ke input to developing
product scope and design strategies. :e6uirements are the bridge between the
usage analsis and solution description. A complete statement of :e6uirements
demonstrates that Microsoft understands its customer*s needs. The statement also
345+35+3(- <
becomes the baseline for more detailed technical documentation in the planning
phase. 1ood :e6uirements analsis lowers the risk of downstream surprises.3
/usiness Re0uirements
<<Begin tet here!!
&ser Re0uirements
<<Begin tet here!!
Operationa* Re0uirements
<<Begin tet here!!
S-stem Re0uirements
<<Begin tet here!!
Scope
%$escription& The #cope places a boundar around the solution b detailing the
range of features and functions, b defining what is out of scope, and b discussing
the criteria b which the solution will be accepted b users and operations. The
#cope clearl delineates what stakeholders e,pect the solution to do, thus making it
a basis for defining pro'ect scope and for performing man tpes of pro'ect and
operations planning.3
&eature'&un!tion (ist
%$escription& The 8eature$8unction 9ist section contains an e,pression of the
solution stated in terms of 8eatures and 8unctions. -t identifies and defines the
components re6uired to satisf the customer*s re6uirements.
+usti,ication& The 8eature$8unction 9ist enables the customer and pro'ect team to
understand what the pro'ect will develop and deliver into the customer*s environment.
-t is also the input to the Architectural and Technical +esign #trategies.3
<<Begin tet here!!
Out of S!ope
%$escription& The )ut of #cope section lists and defines a limited set of features and
functions e,cluded from a product or solution 7that is, the features and functions that
fall outside its boundaries. -t does not list everthing that is )ut of #cope. it onl lists
and defines features and functions that some users and other stakeholders might
tpicall associate with a tpe of solution or product.
+usti,ication& )ut of #cope documentation helps to clarif the solution scope and
e,plicitl states what will not be delivered in the solution.3
345+35+3(- *
<<Begin tet here!!
Version Release Strategy
%$escription& The !ersion :elease #trateg section describes the strateg b which
the pro'ect will deliver incremental sets of features and functions of the customer*s
solution in a series of releases that build upon each other to completion.
+usti,ication& The !ersion :elease #trateg enables the customer to plan for the
orderl implementation of the solution, including the ac6uisition of the re6uired
infrastructure to support the solution. -t also describes how Microsoft will provide the
customer with a usable set of functions and features as soon as possible.3
<<Begin tet here!!
A!!eptan!e Criteria
%$escription& Acceptance Criteria define the metrics that must be met in order for the
customer to understand that the solution meets its re6uirements.
+usti,ication& Acceptance Criteria communicate to the pro'ect team the terms and
conditions under which the customer will accept the solution.3
<<Begin tet here!!
Operational Criteria
%$escription& )perational Criteria define the conditions and circumstance b which
the customer*s operations team 'udges the solution read to deplo into the
production environment. )nce deploed, the customer takes ownership of the
solution. This section ma specif the customer*s re6uirements for installing the
solution, training operators, diagnosing and managing incidents, and so on.
+usti,ication& )perational Criteria communicate to the pro'ect team the terms and
conditions under which the customer will allow deploment and ultimatel sign off on
the pro'ect. This information provides a framework for planning the solution*s
deploment.3
<<Begin tet here!!
So*ution $esi.n Strate.ies
Ar!hite!tural #esign Strategy
%$escription& The Architectural +esign #trateg describes how the features and
functions will operate together to form the solution. -t identifies the specific
components of the solution and their relationships. A diagram illustrating these
components and relationships is an e,cellent communication device.
345+35+3(- 4
+usti,ication& The Architectural +esign #trateg converts the list of features and
functions into the description of a full functional, integrated environment. This
information enables the customer to visuali(e the solution in its environment. -t ma
drive the selection of specific technologies. The Architectural +esign #trateg is ke
input to the design specification.3
<<Begin tet here!!
Te!hni!al #esign Strategy
%$escription& The Technical +esign #trateg documents the application of specific
technologies to the Architectural +esign. -t is a high/level description of the ke
products and technologies to be used in developing the solution.
+usti,ication& A Technical +esign #trateg identifies the specific Microsoft
technologies that will be applied to the solution and demonstrates their benefits to the
client.3
<<Begin tet here!!
345+35+3(- ?