Communication‎ > ‎

Weekly Status Reports

Weekly status reports help to keep management (in this case, the project manager, TA's and instructors) and team members informed about your progress. A status report must fit on a single page and comprises four sections. Each section is typically organized as a set of 3-6 bullet items.  Individual contributors create status reports for their own work. Team leaders or project managers create weekly status reports for their team/organization.

  • What you said you were going to do this week. The first section is an exact copy of the third section from the previous week — that is, your goals from a week ago. (The first week, it can be empty.)
  • What you did this week.  The second section should tell us about the progress you've made this week: what you've done, what worked, where you had trouble, and what you've learned.  It should address what you said you were going to do.
  • What you are going to do next week. The third section should outline your plans and goals for the following week. If tasks from one week aren't yet complete, they usually roll over into your tasks for the next week. 
  • Issues. What's getting in your way of executing.  It may be explanations of why yopu didn't get done what you said you were going to do or things that will impede your progress in the future.
In this class, the project manager must submit a weekly status report every week.  She/he should publish it on your project's wiki and mail it to your TA and the instructor.  Status reports are due at 11:59PM on Sunday (reflecting the previous week's work).

As a team you may decide that individuals should also publish weekly status reports.  I encourage it as it is a good way to communicate and keep track of your progress However, it's up to your team.

(Thanks to David Notkin for writing a similar document, from which some text was aped.)