| Name: | Date: |
| Project Name: |
Period Covered: |
To use this sheet, view it with a web page, select "View -> Source", then save a copy of the source code in a folder where you can find it again. You might want to re-name the copy to "template.html" or something similar. Next, edit the template and delete all text between lines 70 and 124 at the end of the file. Don't delete the last two lines in the file, as they are important for the html code. Save the file. Finally, make a copy of this new template file, and edit it to add the status text in the appropriate locations on the page. This means simply typing the status text between the <li> and </li> "tags" under each main heading.
Status reports must be specific. Project management will not understand what is going on with the project, and thus will not be able to track progress and “earned value”, unless you provide details. This means they will come bug you later for the details you didn’t provide them, and will interrupt your work progress twice for one report; once for you to create the original (inadequate) report, and again when they come talk to you personally. This is not only inefficient, but also can be downright annoying. So, here are some tips for informative written status reports. Keep in mind these are good tips to remember when you present your oral status reports as well.
Under Accomplishments it is not sufficient to write "Wrote code". Instead, describe the details of the tasks you completed, something like this:
Under Scheduled tasks it is not sufficient to write "Write more code". Instead, write explicit text describing the task and include the data for scheduled completion, in the following manner:
Under Risks it is not sufficient to write "not enough time". Explain what the risk or concern is, how it impacts schedule, and how the problem will be solved, in a fashion similar to the following: