Team Name

Sample Project Calendar

This list is the most important management document on a day-to-day basis.  It is crucial that it be kept accurate and current.  Be very rigorous about recording completed and late action items.  Update this list at least once a day.

Current Action Items

Last Updated 10/6/01 08:33 pm

Task Description Assigned To Due Date Date Completed Status Slip
Create Name Tags for the entire team, also get plastic protectors. Ben 10/02/01 8:00am 10/02/01 Done
 0
Bake oatmeal cookies for Sat. team meeting Mike 10/8/01 3:00pm   assigned
Prepare draft of the training plan and e-mail to everyone. Lou 10/6/01 9:30am   late
 1

Status Codes

Assigned:  The task has been assigned and accepted.  Optional: "Urgency" indicator, perhaps in color, giving a ranking to how urgent this task is, or perhaps simply an icon for urgent items.
Done: The task is complete.
Late: The task is incomplete.
DoneLate: The task is completed, but was not done by the due date.
re-assigned: The task was re-assigned.  This could mean replaced with a new task or broken into new tasks.
Deferred: The task due date has been delayed indefinitely, perhaps pending completion of a dependent task.
Delayed:  The developer has requested (in advance) to extend the due date.

History

You may place older items in an archive.


Examples

Here are some examples of good (+) and not-so-good (-) action items:

-Get Nametags

+Create a nametag for each team member following instructor's guidelines. Bring the nametags already cut to proper size for a plastic badge holder.

-Create Team Logo

+Use the draft created during team mtg to create a graphic image of our logo.  Save in JPG format and email to team webmaster.

+Complete the training plan initial skill self-assessment.  Email results to training mgr.

+Negotiate Feasibility Prototype requirements with instructor during office hour Tuesday.  Post agreed upon requirements to team bulletin board.

-Create rough draft of class diagram.

+Draw a rough draft of class diagram, including associations and method names but not signatures.  Bring drawing on paper to team mtg.

-Correct Method Designs

+Revise Method Designs using issues raised during walkthrough.  Update zip file (link on home page) with revised methods and notify all by email when complete.

-Write DD entries.

+Write your assigned DD entries using required notation and type in HTML format.  Email to QA person.