Вы находитесь на странице: 1из 12

<<Project Name>>

Pilot Plan
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+(5+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 WARRANTIES, EPRESS 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+(5+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 0ilot 0lan
Author
6reation 1ate
8ast 9pdated
Table of Contents
$ummar"..........................................................................................................................
:b;ecti%es........................................................................................................................
0ilot 1escription..............................................................................................................
0ilot(s)$election 6riteria.............................................................................................
0ilot $cope..................................................................................................................-
$ite $election..............................................................................................................-
Target 9ser 0rofile......................................................................................................-
9ser $ubset for 0ilot...................................................................................................<
,ncremental =ilestones..............................................................................................<
$uccess 6riteria and =etrics......................................................................................<
9ser 0reparation.............................................................................................................<
9ser =arketing or >%angelism 0lan...........................................................................*
9ser Training 0lan......................................................................................................*
Transition 0lans..............................................................................................................*
Transition $trateg".....................................................................................................*
Add Additional 9sers.................................................................................................*
Rollback 0ilot.............................................................................................................*
6ancellation................................................................................................................4
?ree&e.........................................................................................................................4
6ompletion.................................................................................................................4
0ilot >%aluation..............................................................................................................4
Risks...............................................................................................................................4
Glossar" of Terms...........................................................................................................@
Appendi........................................................................................................................A
345+(5+3(- (

&Intro'uction to t(e Tem)late
&"escri)tion* The %ilot %lan describes what aspect of the solution will be delivered
as a pilot and provides the details necessar to conduct the pilot successfull. This
includes details on how to evaluate the pilot, the results of which will facilitate a
decision whether or not to move the solution to production. %ro&ects often create one
or more 'pilot( solutions for the purpose of proving the feasibilit of solution
approaches, e)perimenting with different solutions, and obtaining user feedback and
acceptance on proposed solutions. %ilot solutions usuall implement onl those
subsets or segments of re*uirements or functional specifications necessar to
validate a solution.
+usti,ication* The %ilot %lan provides the means to validate business re*uirements
and technical specifications prior to deploing the solution into production. %lanning
the details of the pilot ensures that the participating pro&ect teams identif their roles
and responsibilities and resource re*uirements specific to pilot development, testing,
and deploment activities.
A pilot can provide ke information on development processes, end+user validation,
and production environment usage. ,t also provides feedback to stakeholders
regarding the success of the solution once it is formall released.
-Team Role Primar-* Pro.ram Mana.ement determines the scope of the pilot and
incorporates the pilot plan details into the master pro&ect plan and schedule. Because
the are responsible for the pro&ect as a whole, the are also responsible for the pilot
deploment, which is a ke milestone toward the solution.s success. %rogram
Management utili/es the business re*uirements and designs documents to
determine the pilot scope.
Team Role Secon'ar-* "e/elo)ment will provide input to the plan as their
resources will be instrumental in creating the pilot components and verifing that
those components are read for deploment. $ser E0)erience will provide input to
the plan regarding the appropriate end+user audience and the activities that will
ensure that end+users are properl prepared for the pilot. Release Mana.ement will
provide input to the plan regarding the deploment and the verification procedure to
ensure the infrastructure works properl during the pilot phase.01
Summar-
&"escri)tion* %rovide an overall summar of the contents of this document.
+usti,ication* #ome readers ma need to know onl the plan2s highlights, and
summari/ing creates that user view. ,t also enables the full reader to know the
essence of the document before the look at the details.1
<<Begin tet here!!
O1jecti/es
&"escri)tion* The 3b&ectives section describes the business and technical drivers
that led to the decision that a pilot is necessar. ,t also identifies the pilot2s ke
strategic ob&ectives.
+usti,ication* The identification of the drivers and ob&ectives signals to the customer
that Microsoft has carefull considered the situation and solution and created an
appropriate pilot approach.1
<<Begin tet here!!
Pilot "escri)tion
&"escri)tion* The %ilot 4escription section provides an overview of the pilot,
including the selection criteria, scope, and success factors for each pilot.1
Pilot(s)Selection Criteria
&"escri)tion* The %ilot5s6 #election Criteria section identifies the criteria used to
select which aspects of the solution will be demonstrated via a pilot. The following
criteria are suggestions that can be e)panded or contracted based on the specific
pro&ect. "se the criteria and customi/e it to the specific pro&ect.
Com)an- .oals7 8nsure that the pilot aligns with and supports the business2
mission.
Com)ellin. nee'7 #elect a pilot where users will see a tangible benefit.
Tec(nolo.- ,it7 Be sure that there is a need to maintain unstructured data,
provide data replication, and take advantage of a short development ccle.
Critical mass2scala1ilit-7 8nsure that the pilot can be successful without
having to implement the entire solution for the entire business.
"e)lo-ment /eri,ication an' )lannin.7 8nsure that the pilot can verif the
architecture and rollout plans in a production environment.
C(am)ion7 ,dentif an effective business unit champion who will evangeli/e
the pilot effort.
Pro,ile7 #elect a group that is not averse to technolog. These users should
be able to provide valuable feedback and tolerate some initial challenges. ,t is
generall better to select a power user group than the senior e)ecutive staff.
345+(5+3(- .

"-namics7 ,f the plan is to implement discussion groups, make sure that the
pilot users will communicate with one another.
Resources7 8nsure that the group participating in the pilot full intends to be
active in the process and provide feedback.1
<<Begin tet here!!
Pilot Scope
&"escri)tion* The %ilot #cope section describes the scope of the pilot. ,t includes
descriptions of the following7
The solution components that will be developed and deploed and the span of
the customer2s operational environment for that deploment 5controlled
introduction6
The business functions and technologies to be e)ercised during the pilot
The anticipated schedule if the pilot re*uires a staged deliver
The number of sites, users, and workstations
The duration of evaluation period
This scope ma include desktop installation, data migration activities, and
connectivit with e)isting sstems.1
<<Begin tet here!!
Site Selection
&"escri)tion* The #ite #election section defines site selection criteria and selected
sites. This ma be depicted graphicall with a diagram or b using a table to
summari/e the numbers of users, communication links, etc. #ite selection criteria
ma include7
Testing goals
%ilot visibilit
%ro)imit to team
Abilit or willingness to provide meaningful feedback
%ositive attitude toward pro&ect
9illingness to provide testimonials1
<<Begin tet here!!
Target User Profile
&"escri)tion* The Target "ser %rofile section provides a summar of the user profile.
This is information that can be transferred from the "sage #cenario document.1
<<Begin tet here!!
345+(5+3(- -

User Subset for Pilot
&"escri)tion* The "ser #ubset for %ilot section identifies the subset of the target
users that will participate in the pilot. ,t also describes how these users will be
identified within the customer2s operational environment in order to engage them in
the pilot.1
<<Begin tet here!!
Incremental Milestones
&"escri)tion* The ,ncremental Milestones section describes how the pilot will e)pand
b increasing the class and number of users. This information can be placed in a
table, as shown below71
Milestone or ,nterval Criteria for Attaining
Milestone
,ncremental "sers
5:umber of "sers,
Classes of "sers6
Comments
<<Begin tet here!!
Success Criteria an Metrics
&"escri)tion* The #uccess Criteria and Metrics section defines the pilot2s success
criteria and the specific measurements that will be taken to determine the level of
success. A pilot can be declared 'complete( or be graded in terms such as ;partiall
successful; or ;unsuccessful.; 8ach measurement description should include a target
metric and an acceptable range of values. The success criteria ma fall into the
following categories7
#stem performance
3perations cost
#tabilit <down time
"ser performance
"ser satisfaction
Business goals
,dentif the criteria for the overall pilot, incremental milestones, and the final
completion.1
<<Begin tet here!!
$ser Pre)aration
&"escri)tion* The "ser %reparation section outlines how users will become aware of
the pilot and understand their involvement. ,t also addresses an special training
re*uirements and necessar resources to ensure that the users can participate
effectivel in the pilot.1
345+(5+3(- <

User Mar!eting or "vangelism Plan
&"escri)tion* The "ser Marketing or 8vangelism %lan section describes how users
will become aware of the pilot and the value to them of the solution. This is often
called the Marketing or 8vangelism %lan. This plan should describe the ke
messages that will be delivered to the users and an incentives intended to promote
participation in the pilot. =ou ma include this information in the Communication %lan
or create a reference to it.1
<<Begin tet here!!
User Training Plan
&"escri)tion* The "ser Training %lan section describes the plans for training users
during the pilot. This ma be different than the deploment phase plan for training
users. =ou ma include this information in the 8nd+"ser #upport %lan or create a
reference to it.1
<<Begin tet here!!
Transition Plans
&"escri)tion* The Transition %lans section describes the strateg and criteria that
will be used to guide transitions between phases of the pilot.1
Transition Strateg#
&"escri)tion* The Transition #trateg section describes the factors that will be used
to determine whether to transition to add more users or to rollback, cancel or free/e
the pilot. These factors ma include the estimated impact on business and the
attainment of metrics. 4escribe contingenc plans for failures and the thresholds for
rollback, cancellation, free/e, or completion.1
<<Begin tet here!!
$ $itional Users
&"escri)tion* The Add Additional "sers section describes the procedures for adding
additional groups of users.1
<<Begin tet here!!
Rollbac! Pilot
&"escri)tion* The >ollback %ilot section ddescribes the procedures for rolling back a
pilot to the pre+deploment state.1
<<Begin tet here!!
345+(5+3(- *

Cancellation
&"escri)tion* The Cancellation section describes the procedures for canceling the
pilot.1
<<Begin tet here!!
%ree&e
&"escri)tion* The ?ree/e section describes the procedures for free/ing the pilot
deploment.1
<<Begin tet here!!
Completion
&"escri)tion* The Completion section describes the procedures for completing a
pilot.1
<<Begin tet here!!
Pilot E/aluation
&"escri)tion* The %ilot 8valuation section ddescribes how the results of the pilot will
be evaluated. ,t includes the process b which lessons learned will be incorporated
into the final solution deploment. ,t describes the method5s6 for assessing the *ualit
of the pilot deploment process 5e.g. user surves, peer reviews, user interviews,
etc.6. ,t also describes the process for identifing, assigning, and following up on
action items related to deploment or product issues identified during the pilot.
+usti,ication* "p front planning about the evaluation process ensures that all
evaluation tools will be prepared before the pilot begins and that the participating
pro&ect teams plan for communicating lessons learned.1
<<Begin tet here!!
Ris3s
&"escri)tion* The >isks section llists all known risks for conducting the pilot. These
risks should be associated with the development of the pilot components as well as
the deploment. These risks should be transferred to the master pro&ect risk
document.
+usti,ication* 8arl identification of risk enables the team5s6 to begin managing
them.1
<<Begin tet here!!
345+(5+3(- 4

4lossar- o, Terms
Abbreviation Meaning
345+(5+3(- @

A))en'i0
345+(5+3(- A