Project Status Report Log

Release Information

Project: PROJECT-NAME
Internal Release Number: X.Y.Z
Related Documents:
LINKS-TO-RELEVANT-STANDARDS
LINKS-TO-OTHER-DOCUMENTS
Process impact: This is a log of project status reports. It can simply list status reports in chronological order. Or, it can organize them in a way that helps visualize project trends.
TODO: Create periodic (e.g., weekly) status reports by copying and editing the status report template. Link to each status report from this log. Use one or more of the organizations shown in the samples below.
TIP: Update the project overview status section whenever there is a new status report. If you want to simplify the process, you could select one of the organizations below and paste it directly into the project overview rather than maintaining this file.

Status Reports by Date

Status Reports by Date with Summary

Week Report Open Issues Summary / Comments
-3 2004-09-06 8 Project definition and planning
-2 2004-09-13 44 Did detailed planning
-1 2004-09-20 41 Gathered requirements
01 Kick-off presentation 41 Big effort before kick-off meeting
02 2004-10-04 34 On track
03 2004-10-11 28 On Track
04 Office closed for week-long retreat 28
05 2004-10-25 10 Slipped some features to next release
06 Pending
07 Pending

Status Reports by Date and Sub-team

Week Front-end Team Back-end Team Open Issues Summary / Comments
-3 2004-09-06 N/A 8 Project definition and planning
-2 2004-09-13 N/A 44 Did detailed planning
-1 2004-09-20 2004-09-20 41 Gathered requirements
01 MISSING 2004-09-27 41 Big effort before kick-off meeting
02 2004-10-04 2004-10-06 34 On track
03 2004-10-11 MISSING 28 On track
04 Office closed for week-long retreat 28
05 2004-10-25 2004-10-27 10 Slipped some features to next release
06 Pending Pending
07 Pending Pending

Status Reports by Date and Audience

Week Developers to Managers Managers to Executives Open Issues Summary / Comments
-3 2004-09-06 N/A 8 Project definition and planning
-2 2004-09-13 N/A 44 Did detailed planning
-1 2004-09-20 Proposal presentation 41 Gathered requirements
01 MISSING Kick-off presentation 41 Big effort before kick-off meeting
02 2004-10-04 N/A 34 On track
03 2004-10-11 N/A 28 On track
04 Office closed for week-long retreat Exec. presentation at retreat 28
05 2004-10-25 N/A 10 Slipped some features to next release
06 Pending N/A
07 Pending Pending

Status Capsule Reports

Week Work Done Hours Effort Open Issues Main Risks Upcoming Activity
-3 Project definition and planning 30 00 Project proposal could be rejected Do more planning
-2 Did detailed planning. Set up project website. 32 44 Could lose sponsor Meet with key customers
Show proposal to executives
-1 Gathered requirements
Proposal presentation to executives
42 41 Scope creep if stakeholders found late Staffing project
Project kick-off meeting
01 Project kick-off presentation 48 41 Unsatisfied human resource needs Start detailed requirements and design
02 Drafting requirements and design 77 34 Unclear requirements for ASPECT Continue on requirements and design
03 See full status report 82 28 Lack of training in TECHNOLOGY Continue on requirements and design
04 Exec. presentation at retreat 15 28 Changing market conditions Continue on requirements and design
05 Slipped some features to next release 85 10 N/A Start prototyping
06 Pending
07 Pending
TODO: Check for words of wisdom for additional advice on this template.
Company Proprietary
Copyright © 2003-2004 Method Labs. All rights reserved. License terms. Retain this copyright statement whenever this file is used as a template.