Status Report for <project>

Page 1

Project Status Report Template

Project Name: Project Number: Project Manager: Report Date: Reporting Period: Management Summary <Provide a condensed summary of key status indicators, critical issues, critical risks, trends, and similar factors. List the significant tasks completed and milestones reached, serious risks controlled and serious risks newly identified, significant issues resolved or new issues that arose, quality plan status, significant deviations from plan, and other major project changes or progress since the previous status report. In the later stages of the project, include an update on test status. Include descriptions of any recent project successes here. A ta le like that elow can provide a helpful summary.! Defined milestones completed: Defined tas s completed: $otal estimated project #ours used: A#ead of (or Be#ind) sc#edule b(: ,no-n defects: /taff members on project Contingenc( #ours remaining: Schedule 'nitial estimated completion date: Pre1ious estimated completion date: Current estimated completion date: Key Milestones Table
Planned Completion Date <date! Previous Forecast Completion Date <date! Current Forecast Completion Date <date! Actual Completion Date <date!

to

A of B (C%) D of ! ("%) of c#ild tas s in work breakdown structure % of & ('%) ) labor*#ours+ , da(s . open of M found N of P planned 0% of R #ours

<date! <date! <date!

ID 2 3 4

Title <milestone!

Product Size <"ummari#e the planned, current, and most recent estimated si#e of the products, in whatever units are meaningful to your project. $or em edded systems products, include consumption of critical computer resources, such as %A&, %'&, nonvolatile memory, (P) capacity, and communications andwidth. (onsider including a chart of cumulative si#e and critical computer resource consumption so that trends ecome evident.!
Copyright 200X by <company>. !! Rights Reser"e#.

Status Report for <project>

Page 2

Effort <Provide the num er of planned and actual la or*hours e+pended on all project activities since the previous status report and the planned and actual effort for the project effort to date. Provide an e+planation for significant discrepancies. ,escri e the impact of these discrepancies on estimates for the remainder of the project. As an alternative or supplement to a simple ta le like that elow, consider providing a cumulative earned value tracking chart.!
Life Cycle Activity This Reporting Period (labor hours! Planned #ffort Actual #ffort Pro"ect to Date (labor hours! Planned #ffort Actual #ffort

Cost <Provide the planned and actual cost spent on all project activities since the previous status report and the planned and actual cost for the project to date. Provide an e+planation for significant discrepancies. ,escri e the impact of these discrepancies on estimates for the remainder of the project. As an alternative or supplement to a simple ta le like that elow, consider providing a cumulative earned value tracking chart.!
Life Cycle Activity This Reporting Period Planned Cost Actual Cost Pro"ect to Date Planned Cost Actual Cost

Requirements Status <"ummari#e the status of the various requirements specifications for the project, including .ewly reviewed or aselined requirements specifications (urrent num er of functional requirements ,istri ution of requirements status, such as a ta le or graph showing the percent having status of Proposed, Approved, Implemented, /erified, %ejected, or ,eleted Percent of requirements in the aseline changed within this reporting period and for the project to date ,istri utions of origin and types of requirements changes 0stimated effort and schedule impact of approved changes 0ffort spent on requirements management and change control activities

1racking charts that show, for e+ample, the cumulative num er of requirements as a function of time, are useful for making trends evident.! Top i!e Ris"s <List the top five risks 2those having the highest risk e+posure3 on the %isk List and the status of mitigation or contingency plans to respond to the risk. 0scalate any risks that require senior management action.!

Copyright 200X by <company>. !! Rights Reser"e#.

Status Report for <project>

Page $

#pen $ssues <List the major issues that are not yet resolved or have newly appeared. Indicate target dates for resolving the major issues. Include issues arising from quality assurance or configuration management audits, hardware, and staff or other resource issues. Indicate which issues require attention from senior management.! %ction $tems <List the major pending action items that were completed since the last status report and new major action items that have een identified since that report.! &efects <Present the total num er of defects discovered to date, the num er currently open, and the num er closed. Identify any potential show*stopping defects. (onsider classifying the defects y how they were discovered 2testing, peer review, or other3 or y severity. 1racking charts showing defect counts in the various categories as a function of time are helpful for making trends evident. %ecords of the effort e+pended on defect detection and defect correction are also valua le, to help the project assess its cost of quality and judge where process changes would e cost*effective.

Copyright 200X by <company>. !! Rights Reser"e#.