PROJECT STATUS REPORT
Project Status Report in Microsoft Word format.
Instructions For Use
- Your "Project Status Report" should contain the following elements:
- A title referring to the project.
- A date and identification of the person preparing the report.
- A list of accomplishments since the last report.
- A list of pending items yet to be resolved.
- A list of any concerns and recommended actions to resolve them.
- Any other remarks that might be made to inform, reward, or motivate team members.
- Prepare a Project Status Report at regular intervals, usually once a week.
- Keep copies of the Project Status Reports in the project notebook or diary. (It is sometimes a good idea to provide the client with copies as well. In other cases, it may be better to keep these reports internal to the project team)
Project Status Report
Model 17 Training (Project No. XY768)
Date: June 17, 1994
From: Judy Uptodate
Accomplishments: (Since June 10th report.)
- Began the analysis, which included meeting with technical SMEs and interviewing trainees
- Arranged for renting an XYZ Model 17 for the development team for authoring purposes
- Decided to use the 5/28 version of the software; later versions are too unstable
Pending Items:
- Complete task analysis and revision of preliminary objectives
- Brainstorm with designers re: creative design strategies
- Start writing Design Plans
Concerns and Recommended Actions:
- Bud Delay doesn't like his proposed role as reviewer. Recommend using Martha Smart instead.
- Engineering still won't discuss the new attachment for the XYZ. We must get a demo and documentation by 6/23 or that segment will have to be dropped from the course.
Remarks:
- Many thanks to Oscar Ontheball for locating the missing XYZ marketing plans.
This page is presented by the
Center for Education Integrating Science, Mathematics and Computing (CEISMC)
at Georgia Tech's College of Sciences.