Weekly Status Report
Go to Marquette Home
Date due: Week according to the calendar. Mostly Monday's before class, but when we don't meet on Monday, then Wednesday before class.

In any project, you need to tell your boss what you are doing.

When: Mostly Monday's before class, but when we don't meet on Monday, then Wednesday before class.

What: Weekly status report for the entire team

Who: Designated team scribe

How: Via Turnitin.


  1. For EACH team member:
    1. Hours spent on ALL outside of class COEN 181 work. Project. Assignments. Everything for the class, except the class meeting itself. You do not need to report hours for each task. Total for each person is enough. Whole numbers of hours are sufficient.
    2. Tasks completed
    3. What did you read?
    4. Tasks to do next week
  2. As a team
    1. An updated who-what-when with annotations of what was accomplished.


Team: <Project title>
Team members: <Names>

<Name 1>
  Tasks completed:
  Tasks for next week:

<Name 2>
  Tasks completed:
  Tasks for next week:


As a team:
  Open issues:
  Anything else:


Reading? There are tremendous resources available, and you will find that whatever you know is not enough. Hence, I expect each class member to read at least 2 chapters in appropriate books each week. In your weekly report, just tell me the author, title, and chapter titles you read.

How hard is this? Any reporting takes time. Good progress reporting SHOULD not take so much time you have no work to report. The team SHOULD be delegating tasks so each team member knows what they should be working on. Hence, _IF_ you have work to report, preparing your weekly report to send to your team secretary should not take more than 10 minutes, maximum. It should not take the secretary more than 10 minutes to assemble them all and pass them on to me. If you find yourself taking longer than these guidelines, the team needs to talk to me about it.

Late? You all know this weekly status report is required. Each team should set its own internal procedures and deadlines so that the secretary can comfortably meet my Friday 5:00 PM deadline. If someone misses the deadline, I encourage the secretary not to waste time worrying about it, but simply show the missing person's name as "No report." If your report is missing once or twice, I will not worry about it either. If it is missing three or more times, your grade may suffer. If the team's report is late three or more times, the grade of ALL the team members will suffer.

Honesty: Since the entire team sees the team's report as it is submitted via the team's e-mail alias, I assume that each team member will be honest in reporting work done and hours spent.

Purpose: You make a plan, and you intend to follow that plan. Regular status reporting is one tool for tracking actual against planned progress to give an early warning of trouble. Also, regular reporting of your work is your assurance that the boss knows what your contributions are.

I want ONE report per team. I will not accept straggler reports from individual team members. If you miss your team's report, you miss the week.


In the weekly status reports, I really look at

  1. Did everyone on the team report?
  2. Individual hours
  3. In general, what did each person do? Are they doing their share?
  4. Are individuals looking for ways to contribute?
  5. Does the team seem to have some idea what to do next?

Otherwise, the details do not matter. I do not want lengthy reports that take you more than a few minutes to compile.