Project Name
Weekly Project Report
Project Manager: __________________
Date: ___________________
Project Name
-1-
Purpose and Content
Weekly Report
Purpose: Weekly reports are important to facilitate project tracking and
control and to keep your supervisor(s), customer(s) and subcontractors
informed on the status and progress of your project.
A weekly report must contain at least the following information:
Project organization
A short summary of the most important points (One chart for each point);
All major decisions made since the last report;
All major changes to the schedule made since the last report;
A risk list showing the top risks of this and previous weeks;
A list of action items that have been opened or closed since the last report as
well as those still open;
A summary of the current project status in terms of
schedule compliance, i.e. how "good" the project follows the current schedule
technical performance, i.e. any technical problems encountered, etc.
resources spent in various categories (funds, people, equipment, etc.)
project metrics, like amount of code and documentation produced, number of new,
open, and closed action items and number of change requests.
The weekly reports will be delivered by the team members at the beginning of
their weekly meetings with the supervisors. During this meeting the team
members are expected to briefly summarize the past week. Please do not forget
to update all your documents accordingly.
Updated schedule
Lessons learned
Comments
Project Name
-2-
Project Organization
(example)
Project
Project Manager
Manager
_______________
_______________
Contracts
Contracts
_____________
_____________
Procurement
Procurement
QA
QA&&Test
Test
System
System Engineer
Engineer
_____________
_____________
_____________
_____________
_____________
_____________
_______________
_______________
_____________
_____________
Project
ProjectControls
Controls
_____________
_____________
Chief
Chief System
System Engineer
Engineer
_______________
_______________
_______________
_______________
Software
Software Engineer
Engineer
Hardware
HardwareEngineer
Engineer
Integration
Integration
Test
Test
Etc.
Etc.
_____________
_____________
_____________
_____________
_____________
_____________
_____________
_____________
_____________
_____________
_____________
_____________
_____________
_____________
_____________
_____________
_____________
_____________
_____________
_____________
_____________
_____________
_____________
_____________
_____________
_____________
_____________
_____________
_____________
_____________
Staffing Need
Actionee
Project Name
ECD
ACD
-3-
Important Points
Point: (provide 2 sentence explanation):
____________________________________
____________________________________
____________________________________
____________________________________
Approach:
STEP
Step Description (WHAT)
Actionee (WHO)
ECD (WHEN)
ACD (WHEN)
Step 1
Step 2
Step 3
Step 4
Step 5
FOR EACH STEP INCLUDE: ACTION, ACTIONEE, ECD, ACD (WHAT, WHO, WHEN)
Project Name
-4-
Major Decisions Since Last Meeting
Decision Action
Actionee
Requestor
ECD
ACD
5
6
Project Name
-5-
Major Schedule Changes Since Last Meeting
Schedule Change
Actionee
Requestor
ECD
ACD
5
6
Project Name
-6-
Risk List
Risk
Impact
Mitigation
5
6
Impact is major, medium, or minimum
Project Name
-7-
Action Items from Previous Review
Action Item
Actionee
Requestor
ECD
ACD
5
6
Project Name
-8-
Project Performance
Status
Trend
Technical
Comments:
Schedule
Comments:
Cost
Comments:
Customer Satisfaction
Comments:
Project Metrics (Past/Present/Future
Amount of Code:
Number of Documents:
Number of Open Action Items:
Number of Closed Action Items:
Number of Change Requests:
Project Name
-9-
Project Schedule
Gantt Chart
#
Task Name
Smith, Jones, and Dillon
Requirements Phase
Dur
153d
29d
Start
Finish
2d
07/05/02
07/08/02
User Needs Survey
5d
07/29/02
08/02/02
Web Page Requirements
2d
08/05/02
08/06/02
Preliminary Requirements Review
2d
08/07/02
08/08/02
Final Requirements Formulation
2d
08/09/02
08/12/02
Final Requirements Review
2d
08/13/02
08/14/02
Requirements Complete
0d
08/14/02
08/14/02
19d
Concept Kickoff Meeting
1d
08/15/02
08/15/02
12
Concept Brainstorming
2d
08/16/02
08/19/02
13
Concept(s) Presentation
2d
08/20/02
08/21/02
14
Layout Brainstorming
2d
08/22/02
08/23/02
15
Layout(s) Presentation
5d
08/26/02
08/30/02
16
Concept Selection
5d
09/05/02
09/11/02
17
Creative Design Complete
0d
09/11/02
09/11/02
Development Phase
15d
Development Kickoff Meeting
1d
09/19/02
09/19/02
20
Page Layout
10d
09/20/02
10/03/02
21
Graphics Creation
5d
09/20/02
09/26/02
22
Animation Creation
10d
09/26/02
10/09/02
23
Development Complete
0d
10/09/02
10/09/02
7d
10/11/02 10/21/02
Test Phase
25
Test Kickoff Meeting
2d
10/11/02
10/14/02
26
Page Link Testing
5d
10/15/02
10/21/02
Dx
September
October
November December
January
February
09/19/02 10/09/02
19
24
August
08/15/02 09/11/02
11
18
July
07/05/02 08/14/02
Requirements Kickoff Meeting
Creative Design Phase
2002
07/05/02 02/12/03
10
June
x
axD
aD^Complete M
a^DR
aDDRemaining M
aDDBa
aD*Baseline 1 M
Project Name
-10-
Lessons Learned
Since Last Review
What did we do well?
What did we do poorly?
Where were we lucky?
Where were we unlucky?
If we were to do it again what would we do differently?
Note: Do not include old/previous Lessons Learned on this sheet.
Project Name
-11-
Concluding Comments
Project Name
-12-
