<<Project Name>> Pilot Review 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 te t 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

3(4354+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 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.

3(4354+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 Re%iew Author 6reation 1ate 8ast 9pdated

3(4354+3(-

Table of Contents
<<0ro:ect 7ame!!.........................................................................................................( 0ilot Re%iew...............................................................................................................( 6ustomer 7ame......................................................................................................( Re%ision ; $ign<off $heet..........................................................................................( Table of 6ontents........................................................................................................+ $ummar".........................................................................................................................+ =b:ecti%es.......................................................................................................................+ $uccess >actors and ?etrics...........................................................................................+ 0ilot >eedback $ummaries.............................................................................................+ $essions with the 9ser 6ommunit"............................................................................+ 0roblem Reports.......................................................................................................... @nd<user $ur%e"s......................................................................................................... =bser%ations of the 0ro:ect Team............................................................................... $tatistical =perations Reports..................................................................................... 0ro:ect Team >eedback................................................................................................... Training >eedback......................................................................................................1eplo"ment >eedback................................................................................................$upport >eedback.......................................................................................................6ommunications >eedback.........................................................................................0roblems @ncountered................................................................................................$uggestions for ,mpro%ements...................................................................................A 0ilot Results and Recommendations..............................................................................A

3(4354+3(-

%I'tro(uctio' to t)e Tem*late #escri*tio'+ The &ilot 'eview document records the results of the process that validates that what is delivered during the pilot meets specifications and business re(uirements. ,usti-icatio'+ The pilot)s success or failure is t picall indicative of the progress of the overall pro*ect. Capturing the results of the pilot provides valuable insight into the solution)s value. +f the development and testing activities rigorousl followed the specifications and design, the pilot should go smoothl . +f the pilot results are less than favorable, changes to the pro*ect, small or large, can be made as appropriate. ,Team Role Primar.+ Pro/ram Ma'a/eme't will facilitate the creation of the pilot review document, using the pilot plan -developed during the planning phase. as conte/t. &rogram management should collect input from representatives of all pilot participants -team members and end0users. regarding their feedback on the pilot. Team Role Seco'(ar.+ Pro(uct Ma'a/eme't will emplo the pilot review content that describes end0user satisfaction and make an necessar changes to communication or other customer centric activities. #evelo*me't will need to act on an solution anomalies reported in this review. Test ma need to modif testing procedures to either shrink or enlarge the testing criteria. %ser E0*erie'ce addresses an issues that are negativel affecting users. Release Ma'a/eme't will review the pilot results to understand if an part of the deplo ment process or operational environment needs modification to ensure a successful implementation of the entire solution.12

3(4354+3(-

Summar.
%#escri*tio'+ The #ummar section summari3es the results of the &ilot 'eview document, identif ing whether the pilot was approved or received conditional approval and including ke recommendations and re(uired action items. ,usti-icatio'+ #ome pro*ect participants ma need to know onl the highlights of the review, and summari3ing these creates that user view. +t also enables the full reader to know the essence of the document before the e/amine the details.2

<<Begin te t here!!

O1jectives
%#escri*tio'+ The 4b*ectives section lists and describes the ke ob*ectives to be met b the pilot review process. This information is a re0statement of the pilot ob*ectives found in the &ilot &lan, which was created during the planning phase. ,usti-icatio'+ 'estating pilot ob*ectives provides the reader with sufficient conte/t to make the remainder of the document meaningful.2

<<Begin te t here!!

Success Factors a'( Metrics

%#escri*tio'+ The #uccess 5actors and Metrics section restates the success factors and metrics contained within the &ilot &lan. This includes a list of the factors that will be used to *udge the pilot as a success, partial success, or failure and the metrics to be used to make these *udgments. This section also records the results of the *udgments. ,usti-icatio'+ 'estating pilot success factors and metrics provides the reader with sufficient conte/t to make the remainder of the document meaningful.2

<<Begin te t here!!

Pilot Fee(1ac2 Summaries

%#escri*tio'+ The &ilot 5eedback #ummaries section contains summaries of the feedback obtained from all the pilot participants. An efficient wa of collecting the original feedback data is via web site forms. ,usti-icatio'+ 6ach participating team is assessing pilot results from a different perspective. B including feedback from all teams, the pro*ect ensures that the pilot was performed and assessed from a broad range of viewpoints.2

Sessions with the User Community

%#escri*tio'+ The pro*ect team holds man sessions with the user communit during the planning, development, deplo ment, and operation of a pilot. The #essions with

3(4354+3(-

the "ser Communit section lists and describes each session7 defining its ob*ectives, listing user feedback and recommendations, and defining responses and actions taken b the pilot team.2

<<Begin te t here!!

Problem Reports
%#escri*tio'+ &ilots help to identif and define man t pes of problems that might occur during the development and deplo ment of a full solution at a far smaller cost than the development of a full solution. &roblems can be documented using pro*ect problem report templates to ensure that all participants are recording standard information. The &roblem 'eports section contains a summar of all problem reports.2

<<Begin te t here!!

End-user Surveys
%#escri*tio'+ A primar ob*ective of pilots is to gain information from users about the usabilit of the proposed solution. The 6nd0user #urve s section should include the ob*ectives and a description of each surve , the information gathered and recorded in the surve , and conclusions reached from anal 3ing surve results.2

<<Begin te t here!!

Observations of the Pro e!t Team

%#escri*tio'+ The pro*ect team observes the deplo ment and operation of the pilot to gather and record specific sets of re(uired information as well as ad hoc observations. The 4bservations of the &ro*ect Team section includes the information gathered and recorded b the pro*ect team and their conclusions and recommendations.2

<<Begin te t here!!

Statisti!al Operations Reports

%#escri*tio'+ The #tatistical 4perations 'eports section defines the statistics that were both planned and gathered during pilot operations, summaries of the statistics, and conclusions based on the statistics.2

<<Begin te t here!!

Project Team Fee(1ac2

%#escri*tio'+ The &ro*ect Team 5eedback section contains feedback from pro*ect teams. This feedback is collected during and at the end of the pilot in order to evaluate its success.

3(4354+3(-

,usti-icatio'+ 6ach participating team is assessing pilot results from a different perspective. B including feedback from all teams, the pro*ect ensures that the pilot was performed and assessed from a broad range of viewpoints.2

Training "eedba!#
%#escri*tio'+ The Training section describes the training provided to end0users, operations personnel, and other groups that participated in the pilot program. +t describes the effectiveness of the training, identifies and describes training problems, lists lessons learned, and makes recommendations that will make the training on the actual solution effective.2

<<Begin te t here!!

$eployment "eedba!#
%#escri*tio'+ The 8eplo ment section summari3es the pilot deplo ment plan and compares the actual deplo ment with the plan, listing and defining problems encountered and solved, lessons learned, and recommendations for deplo ment of the full solution.2

<<Begin te t here!!

Support "eedba!#
%#escri*tio'+ The #upport section describes the support planned and provided for the pilot solution. +t includes the actual support needed to conduct the pilot, support problems encountered and solved, and lessons learned that can be e/trapolated into support for the actual solution.2

<<Begin te t here!!

Communi!ations "eedba!#
%#escri*tio'+ The Communications section summari3es the pilot communication plan and describes actual communication e/periences with pilot stakeholders. +t includes the actual communications that occurred during the pilot, communication problems encountered and solved, and lessons learned that can be e/trapolated into communication for the actual solution.2

<<Begin te t here!!

Problems En!ountered
%#escri*tio'+ The &roblems 6ncountered section lists and describes the problems encountered in ever aspect of the pilot -planning, development, deplo ment, training, operations, management, user involvement, support, etc... +t also describes the impact of the problems, solutions applied to the problems, and lists all unsolved problems and the challenges to their solutions.2

<<Begin te t here!!

3(4354+3(-

Suggestions for %mprovements

%#escri*tio'+ The #uggestions for +mprovements section lists and describes all recommended improvements to the pilot, including e/tensions to the current pilot and an additional pilots. +dentif and define their ob*ectives for each e/tension and additional pilot.2

<<Begin te t here!!

Pilot Results a'( Recomme'(atio's

%#escri*tio'+ The &ilot 'esults and 'ecommendations section contains a complete evaluation of the pilot9s success and makes all necessar recommendations. +t describes how well the pilot was received b the users and an usabilit issues or problems that need to be corrected prior to developing the full solution. This section should identif the specific changes or improvements that need to be made from both a technical and pro*ect management perspective. ,usti-icatio': The (ualit goals of the pro*ect and the business ob*ectives of the solution are furthered b a complete and ob*ective assessment of the pilot.2

<<Begin te t here!!

3(4354+3(-