Project Name Weekly Project Report

1. Project NameWeekly Project Report Project Manager: __________________ Date: ___________________

2. Purpose and ContentWeekly 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

3. Project Organization(example) Project Manager _______________ Contracts _____________ Procurement _____________ QA & Test System Engineer _____________ _____________ _____________ _______________ Project Controls _____________ Chief System Engineer _______________ _______________ Software Engineer Hardware Engineer Integration Test Etc. _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ • Staffing Need Actionee ECD ACD

4. Important Points Point: (provide 2 sentence explanation): ____________________________________ ____________________________________ ____________________________________ ____________________________________ Approach: FOR EACH STEP INCLUDE: ACTION, ACTIONEE, ECD, ACD (WHAT, WHO, WHEN)

5. Decision Action Actionee Requestor ECD ACD 1 2 3 4 5 6 Major Decisions Since Last Meeting

6. Schedule Change Actionee Requestor ECD ACD 1 2 3 4 5 6 Major Schedule Changes Since Last Meeting

7. Risk List Risk Impact Mitigation 1 2 3 4 5 6 Impact is major, medium, or minimum

8. Action Items from Previous Review

9. 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:

10. Project Schedule Gantt Chart

11. Lessons LearnedSince 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.

12. Concluding Comments