Project Pilot Report Template
<Organization Name>
Project Pilot Report
Date (YYYY-MM-DD)
[Author]
[Version #.#]
Reviewed and Approved by:
Pilot Project Coordinator Date (YYYY-MM-DD)
Management of VSE Date (YYYY-MM-DD)
Revision Log
Revision Date Description of Changes
(yyyy-mm-dd)
00 First issue
Table of Contents
1. Purpose......................................................................................4
2. Acronyms...................................................................................4
3. Reference Documents.................................................................4
4. Overview....................................................................................4
5. Description of tasks, effort and schedule Deviation....................4
6. Resources..............................................................................................5
7. Interfaces/Dependencies.......................................................................5
8. Risks......................................................................................................5
9. Lessons Learned Report.........................................................................5
Things That Went Well..............................................................................................5
Things That Could Have Gone Better..........................................................................5
Things That Surprised Us..........................................................................................6
Lessons Learned......................................................................................................6
Summary Questions.................................................................................................7
1. Purpose
This report documents the results of a Pilot Project. The report discusses the following
topics: resource requirements (planned versus actual); interfaces and dependencies with
other groups; risks, and risk mitigation, achievement of pilot project objectives, satisfaction
of VSE’s management and end-users.
This report also documents and analyses the measures that we collected. Finally, lessons
learned regarding the conduct of the pilot project are documented to improve future pilot
projects.
2. Acronyms
[Define acronyms used in this document1]
DP Deployment Package
VSE Very Small Entities
3. Reference Documents
[List reference documents, e.g. organization business plan, engineering standard.]
Pilot Project Plan, date (yyyy-mm-dd)
4. Overview
[Provide an overview of what must be accomplished, Name of the VSE and high level
objectives of the Pilot Project]
5. Description of tasks, effort and schedule Deviation
[List the planned versus actual tasks, steps, effort, schedule and artifacts produced
and the reasons for major differences (e.g. number of persons actually trained versus
planned.]
Task Step Planned Actual Effort Reason for
Effort deviation
(Person-hour)
(Person-hour)
Schedule
o Estimate versus actual
Training
o Actual versus planned number of persons
6. Resources
[Describe resources consumed for this Pilot Project, including, money, computer
1
Delete the text in brackets (i.e. [X]) when the section is completed
resources, etc.]
Estimate versus actual
7. Interfaces/Dependencies
[Describe, if applicable, the interfaces or dependencies with other groups.]
8. Risks
[Describe the risks and mitigation activities that were planned and the results
of the risk activities (such as underestimation of the probability, unplanned
risks.]
9. Lessons Learned Report2
Things That Went Well
Business 1.
Issues
Requirements 1.
Process 1.
Project 1.
Management
Technology 1.
<other 1.
category>
<other 1.
category>
Things That Could Have Gone Better
Business 1.
Issues
Requirements 1.
2
Adapted from Wiegers, K., Project Retrospective Procedure, www.processimpact.com
Process 1.
Project 1.
Management
Technology 1.
<other 1.
category>
<other 1.
category>
Things That Surprised Us
What happened on the project that surprised you?
Business 1.
Issues
Requirements 2.
Process 1.
Project 1.
Management
Technology 1.
<other 1.
category>
<other 1.
category>
Lessons Learned
Business 1.
Issues
Requirements 1.
Process 1.
Project 1.
Management
Technology 1.
<other 1.
category>
<other 1.
category>
Summary Questions
Name one aspect of this project you would change if you could?
Name one aspect of this project you would keep unchanged?
