<<Project Name>>

Post Project Analysis

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
3453+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 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.
3453+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 0ost 0ro8ect Anal"sis
Author
6reation 1ate
9ast :pdated
3453+5+3(-

Table of Contents
$ummar"..........................................................................................................................
;b8ecti%es........................................................................................................................
0lanning...........................................................................................................................
Accomplishments.......................................................................................................-
6hallenges..................................................................................................................-
9essons 9earned.........................................................................................................-
Resources........................................................................................................................-
Accomplishments.......................................................................................................-
6hallenges..................................................................................................................<
9essons 9earned.........................................................................................................<
0ro8ect =anagement5$cheduling....................................................................................<
Accomplishments.......................................................................................................*
6hallenges..................................................................................................................*
9essons 9earned.........................................................................................................*
1e%elopment51esign5$pecifications..............................................................................*
Accomplishments.......................................................................................................*
6hallenges..................................................................................................................>
9essons 9earned.........................................................................................................>
Testing............................................................................................................................>
Accomplishments.......................................................................................................>
6hallenges..................................................................................................................>
9essons 9earned.........................................................................................................4
6ommunication..............................................................................................................4
Accomplishments.......................................................................................................4
6hallenges..................................................................................................................4
9essons 9earned.........................................................................................................4
Team5;rgani&ation.........................................................................................................?
Accomplishments.......................................................................................................?
6hallenges..................................................................................................................?
9essons 9earned.........................................................................................................?
$olution........................................................................................................................(3
Accomplishments.....................................................................................................(3
6hallenges................................................................................................................(3
9essons 9earned.......................................................................................................(3
Tools.............................................................................................................................((
Accomplishments.....................................................................................................((
6hallenges................................................................................................................((
9essons 9earned.......................................................................................................((
Appendi: Guidelines for $uccessful 0ost 0ro8ect Anal"sis =eetings........................(+
3453+5+3(- 3

%Intro'uction to t(e Tem)late
#escri)tion* The &ost &ro'ect Analsis document records the results of conducting a
depth and breadth assessment of the pro'ect from its inception (envisioning phase) to
completion (deploment phase). This assessment captures successes, challenges
and failures, and identifies what should have been done differentl on this pro'ect and
what could be done differentl for the ne*t pro'ect.
+usti,ication* Conducting and documenting a post pro'ect review formali+es the
process of learning from past e*perience. This has value for individuals and the
organi+ation as the move forward with new pro'ects. The lessons learned while
creating the solution need to be captured and communicated to all participating team
members and other parts of the organi+ation. This helps the creation of future
solutions more ,uickl with less e*pense and risk.
The following table identifies the recommended time frames for a post pro'ect review
based on various pro'ect characteristics-
Project C(aracteristic - Wee.s A,ter
Com)letion
/ Wee.s A,ter
Com)letion
#cope of pro'ect #mall .arge
.ength of pro'ect #hort (das to /
months)
.ong (/ months to
ears)
0nerg level of team
members
.ow 1igh
Team member time
available
#ome (working on
other pro'ects)
Total
2Team Role Primary* Pro0ram Mana0ement is responsible for developing and
distributing the &ost &ro'ect Analsis. Their main responsibilit is to facilitate the
analsis and encourage information e*changes between the teams and among team
members. &rogram Management also contributes input to the analsis from their
e*periences in pro'ect.
Team Role Secon'ary* All other roles should either contribute to this document or
review it for completeness. Pro'uct Mana0ement will conduct analsis and provide
information regarding the customer3s e*perience and satisfaction with the pro'ect and
solution. #e1elo)ment will conduct analsis and provide information regarding the
building of the solution. Test will conduct analsis and provide information regarding
the ,ualit of the solution. %ser E2)erience will conduct analsis and provide
information regarding user effectiveness. Release Mana0ement will conduct
analsis and provide information regarding the deploment process and the status of
ongoing operations.45
3453+5+3(-

Summary
%#escri)tion* &rovide a brief summar of this document, including what will be done
with the contents, especiall the lessons learned. 6t ma be helpful to list the top three
accomplishments, top three challenges, and top three valuable lessons learned.
0*ample ,uestions to answer to develop this section3s content-
7hat three things (in order of importance) went well8
7hat three things (in order of importance) need improvement8
7hat suggestions do we have for improvement8
7hat other issues need followed up8
+usti,ication* #ome readers ma need to know onl the highlights of the document,
and summari+ing creates that user view. 6t also enables the full reader to know the
essence of the document before the e*amine the details.5
<<Begin tet here!!
O3jecti1es
%#escri)tion* The 9b'ectives section defines the document3s ob'ectives. These could
include :) recording the results of a comprehensive pro'ect analsis and 2) ensuring
that lessons learned during the pro'ect are documented and shared.
+usti,ication* A document containing valuable insight should direct the reader to
specific actions of incorporating that insight into their knowledge base. The ob'ectives
statements should assist the reader in this process.5
<<Begin tet here!!
Plannin0
%#escri)tion- The &lanning section provides analsis and insight on the pro'ect3s
planning aspect. This should include information regarding the planning processes
used, who participated in the planning processes, and the ,ualit of the plans
(reliabilit, accurac, completeness, etc).
0*ample ,uestions to answer to develop this section3s content-
7ere the team goals clear to ou8
7ere the marketing goals clear to ou8
7ere the development goals clear to ou8
1ow complete do ou think the planning was before the actual
commencement of work8
1ow could planning be improved8
7hat recommendations would ou make for the planning process for the ne*t
release85
3453+5+3(- +

Accomplishments
%#escri)tion* The Accomplishments section describes what was successful about
the pro'ect3s planning aspect. Be sure to describe what contributed to that success
and wh it was successful.5
<<Begin tet here!!
Challenges
%#escri)tion* The Challenges section describes an problems that occurred with the
pro'ect3s planning aspect. Be sure to describe what contributed to those problems
and wh the were problems.5
<<Begin tet here!!
Lessons Learned
%#escri)tion* The .essons .earned section describes what was learned about
planning and how planning should be done the ne*t time. This recommendation
could be to use the same approach or could suggest significant changes.5
<<Begin tet here!!
Resources
%#escri)tion* The ;esources section provides analsis and insight on the pro'ect3s
resources aspect. This should include information regarding the availabilit, ,ualit,
and application of resources.
0*ample ,uestions to answer to develop this section3s content-
1ow can we improve our methods of resource planning8
7ere there enough resources assigned to the pro'ect, given the schedule
constraints8
7hat could have been done to prevent resource overload8
<o ou think resources were managed effectivel once the pro'ect started8
Accomplishments
%#escri)tion* The Accomplishments section describes what was successful about
the pro'ect3s resources aspect. Be sure to describe what contributed to that success
and wh it was successful.5
<<Begin tet here!!
3453+5+3(- .

Challenges
%#escri)tion* The Challenges section describes an problems that occurred with the
pro'ect3s resources aspect. Be sure to describe what contributed to those problems
and wh the were problems.5
<<Begin tet here!!
Lessons Learned
%#escri)tion* The .essons .earned section describes what was learned about
resources and how resource management should be done the ne*t time. This
recommendation could be to use the same approach or could suggest significant
changes.5
<<Begin tet here!!
Project Mana0ement4Sc(e'ulin0
%#escri)tion* The &ro'ect Management$#cheduling section provides analsis and
insight on the pro'ect3s pro'ect management and scheduling aspects. This should
include information regarding-
The integration of planning
#cope management
Budget management
#chedule management
;esource allocation
!endor management
;isk management
=ualit management
0*ample ,uestions to answer to develop this section3s content-
7as the schedule realistic8
7as the schedule detailed enough8
.ooking over the schedule, which tasks could ou have estimated better and
how8
<id having a series of milestones help in making and monitoring the
schedule8
7hat were the biggest obstacles to meeting the scheduled dates8
1ow was pro'ect progress measured8 7as this method ade,uate8 1ow could
it be improved8
7as contingenc planning apparent8 1ow can we improve our contingenc
planning for the ne*t release8
1ow could scheduling have been done better or been made more useful8
7hat would ou change in developing future schedules8
1ow were changes managed late in the ccle8
3453+5+3(- -

7ere the trade>offs between schedule and features handled well85
Accomplishments
%#escri)tion* The Accomplishments section describes what was successful about
the pro'ect3s pro'ect management aspect. Be sure to describe what contributed to
that success and wh it was successful.5
<<Begin tet here!!
Challenges
%#escri)tion* The Challenges section describes an problems that occurred with the
pro'ect3s pro'ect management aspect. Be sure to describe what contributed to those
problems and wh the were problems.5
<<Begin tet here!!
Lessons Learned
%#escri)tion* The .essons .earned section describes what was learned about
pro'ect management and how it should be done the ne*t time. This recommendation
could be to use the same approach or could suggest significant changes.5
<<Begin tet here!!
#e1elo)ment4#esi0n4S)eci,ications
%#escri)tion* The <evelopment$<esign$#pecifications section provides analsis and
insight on the pro'ect3s development aspect. This should include information
regarding the development processes used (coding standards, documentation,
versioning, approval, etc), who participated in the development processes, and the
,ualit of the designs and specifications that were used during development
(reliabilit, accurac, completeness, etc).
0*ample ,uestions to answer to develop this section3s content-
7ere there issues in the functional design and ownership8
7ere there issues in the architectural design and ownership8
7ere there issues involved in using components or with code sharing8 1ow
could this be done more effectivel85
Accomplishments
%#escri)tion* The Accomplishments section describes what was successful about
the pro'ect3s development aspect. Be sure to describe what contributed to that
success and wh it was successful.5
<<Begin tet here!!
3453+5+3(- <

Challenges
%#escri)tion* The Challenges section describes an problems that occurred with the
pro'ect3s development aspect. Be sure to describe what contributed to those
problems and wh the were problems.5
<<Begin tet here!!
Lessons Learned
%#escri)tion* The .essons .earned section describes what was learned about
development and how it should be done the ne*t time. This recommendation could
be to use the same approach or could suggest significant changes.5
<<Begin tet here!!
Testing
%#escri)tion* The Testing section provides analsis and insight on the pro'ect3s
testing aspect. This should include information regarding the testing processes used,
who participated in the testing processes, and the ,ualit of the testing plans and
specifications that were used during testing (reliabilit, accurac, completeness, etc).
0*ample ,uestions to answer to develop this section3s content-
7ere there issues in test interaction8
7ere there issues in test case design and coverage8
7ere there enough testers8
7as the ,ualit of the solution we shipped acceptable8
<id we work well with all of the testers85
Accomplishments
%#escri)tion* The Accomplishments section describes what was successful about
the pro'ect3s testing aspect. Be sure to describe what contributed to that success and
wh it was successful.5
<<Begin tet here!!
Challenges
%#escri)tion* The Challenges section describes an problems that occurred with the
pro'ect3s testing aspect. Be sure to describe what contributed to those problems and
wh the were problems.5
<<Begin tet here!!
3453+5+3(- *

Lessons Learned
%#escri)tion* The .essons .earned section describes what was learned about
testing and how it should be done the ne*t time. This recommendation could be to
use the same approach or could suggest significant changes.5
<<Begin tet here!!
Communication
%#escri)tion* The Communication section provides analsis and insight on the
pro'ect3s communication aspect. This should include information regarding the
communication processes used, the timing and distribution of communication, the
tpes of communication distributed, and the ,ualit of the communication content.
0*ample ,uestions to answer to develop this section3s content-
7as communication in our group handled efficientl and effectivel8
7as communication between groups handled efficientl and effectivel8
7as program management effective in disseminating information8
7as program management effective in resolving issues8
7as the e>mail alias usage effective8 1ow could the aliases be better set up
to improve communication8
7ere the status meetings effective8
7as communication with the e*ternal groups (component suppliers, content
suppliers, 90Ms, support, international) effective85
Accomplishments
%#escri)tion* The Accomplishments section describes what was successful about
the pro'ect3s testing aspect. Be sure to describe what contributed to that success and
wh it was successful.5
<<Begin tet here!!
Challenges
%#escri)tion* The Challenges section describes an problems that occurred with the
pro'ect3s communication aspect. Be sure to describe what contributed to those
problems and wh the were problems.5
<<Begin tet here!!
Lessons Learned
%#escri)tion* The .essons .earned section describes what was learned about
communication and how it should be done the ne*t time. This recommendation could
be to use the same approach or could suggest significant changes.5
<<Begin tet here!!
3453+5+3(- >

Team4Or0ani5ation
%#escri)tion* The Team$9rgani+ation section provides analsis and insight on the
pro'ect3s team and organi+ation structure aspects. This should include information
regarding team leadership, an sub>teams and their structure, and the ,ualit of the
integration among the teams. 6t could also include information about the scope of
each team3s work, the performance of its designated role on the pro'ect, and the
balance among the teams regarding decision>making.
0*ample ,uestions to answer to develop this section3s content-
<id ou understand who was on the team and what each member was
responsible for8
7ere the roles of the different groups (development, test, user e*perience,
program management, marketing) clear to ou8
7hat would ou do to alter the organi+ation to more effectivel put out the
solution8 7hat functional changes would ou make8 7hat pro'ect team
organi+ation changes would ou make8
<o ou think the different groups fulfilled their roles8
7hat was deficient in our group8 9ther groups8
<id ou have all the information ou needed to do our 'ob8 6f not, were ou
able to obtain the information8
<id ou think the team worked together well8
7ere management decisions communicated to the team8 <id ou understand
how decisions were made8
7ere e*ternal dependencies managed effectivel8
Accomplishments
%#escri)tion* The Accomplishments section describes what was successful about
the pro'ect3s team aspect. Be sure to describe what contributed to that success and
wh it was successful.5
<<Begin tet here!!
Challenges
%#escri)tion* The Challenges section describes an problems that occurred with the
pro'ect3s team aspect. Be sure to describe what contributed to those problems and
wh the were problems.5
<<Begin tet here!!
Lessons Learned
%#escri)tion* The .essons .earned section describes what was learned about
teams and how that aspect should be approached the ne*t time. This
recommendation could be to use the same approach or could suggest significant
changes.5
3453+5+3(- 4

<<Begin tet here!!
Solution
%#escri)tion* The #olution section provides analsis and insight on the pro'ect3s
solution aspect. This should include information regarding the processes of
"nderstanding the customer3s business ob'ectives and re,uirements
<eveloping a solution concept
<etermining the need for and deploing a pilot
;eading the operational environment for full deploment
6t should also include information on customer satisfaction and an metrics on
business value.
0*ample ,uestions to answer to develop this section3s content-
6n retrospect, could the work of our group been done better8 1ow8
7hat needs to happen so our group can avoid problems in the future8
Are ou satisfied with the solution ou shipped8 6f not, wh8
7hat would ou do to improve the process of creating the solution85
Accomplishments
%#escri)tion* The Accomplishments section describes what was successful about
the pro'ect3s solution aspect. Be sure to describe what contributed to that success
and wh it was successful.5
<<Begin tet here!!
Challenges
%#escri)tion* The Challenges section describes an problems that occurred with the
pro'ect3s solution aspect. Be sure to describe what contributed to those problems and
wh the were problems.5
<<Begin tet here!!
Lessons Learned
%#escri)tion* The .essons .earned section describes what was learned about the
solution and how that aspect should be approached the ne*t time. This
recommendation could be to use the same approach or could suggest significant
changes.5
<<Begin tet here!!
3453+5+3(- ?

Tools
%#escri)tion* The Tools section provides analsis and insight on the pro'ect3s tools
aspect. This should include information regarding the specific tools used, the specific
application of the tools, the usefulness of those tools, and an limitations of the tools.
0*ample ,uestions to answer to develop this section3s content-
7hat improvements do ou recommend for tracking bugs that will make the
process more effective for use during development of the ne*t release8
7hat improvements do ou recommend for document and code source
control8
7hat comments do ou have about the build process and the compilers8
7hat comments do ou have about the coding standards8
7hat other tools do ou need8
7hat other improvements do ou need to make on our e*isting tools85
Accomplishments
%#escri)tion* The Accomplishments section describes what was successful about
the pro'ect3s application of the tools. Be sure to describe what contributed to that
success and wh it was successful.5
<<Begin tet here!!
Challenges
%#escri)tion* The Challenges section describes an problems that occurred with the
tools as the were applied to the work of the pro'ect. Be sure to describe what
contributed to those problems and wh the were problems.5
<<Begin tet here!!
Lessons Learned
%#escri)tion* The .essons .earned section describes what was learned about the
tools and their application and how that should be approached the ne*t time. This
recommendation could be to use the same approach or could suggest significant
changes.5
<<Begin tet here!!
3453+5+3(- (3

A))en'i2* 6ui'elines ,or Success,ul Post Project
Analysis Meetin0s
%<o-
Be constructive and supportive.
Be precise and specific.
?ocus on challenges and suggestions for improvement surrounding process
rather than specific individuals
<o @9T-
"se peoples names.
Be negative or hostile.
Ask permission.
0*plain or 'ustif our comments and recommendations, unless asked to do
so b someone else.
;epeat comments and recommendations made b others.
0*press agreement or disagreement with comments and recommendations
made b others.5
3453+5+3(- ((