Team Website

(ver: 04-Sep-2007)

A comprehensive, secure, up-to-date project website must be created and maintained by each team. The team is free to pick graphics and style which they feel best reflects the spirit of the project. The site will be username and password accessible to those on the project, as well as to others who the company adds to the access list.

WARNING: The username and password for the team web site is *not* the same as the usernane and password for accessing course material. This distinction is important as your company has access to your team web site but not to secure course materials, including the web sites of other teams

Each team must appoint a team webmaster who will work with the course webmaster to create and maintain the sites.

The website will be hosted on the npdbd web server maintained by the course webmaster who will handle security, passwords, ftp access and the like. The team webmaster should contact the course webmaster for information on how to get started. The course webmaster will also set up team e-mail lists. For technical information on connecting to the server and setting up your website, be sure to read the information in the Useful links section on Connecting to the NPDBD server.

Each website must have the following elements:

  1. An appropriate home page with clear navigation means to interior information. This page should contain the company and U of M logos.
  2. A link to the sponsoring company home page.
  3. A "Facts and Information Database" page or pages that contains project resources including: (1) a list of competitors with links (launch your site with a minimum of five competitors on this list; (2) List of resource links relevant to the project, e.g. relevant sites at the FDA, design resources, marketing resources, industry reports, and so on.
  4. List of team members (students, faculty and core company reps) with name, affiliation, phone, fax and e-mail. Include a group or individual pictures of team members. This is the place to go if someone has forgotten a name.
  5. List of company resource contacts including name, title, phone, fax and e-mail.
  6. Resumes of team members. (Link to the resumes posted by the webmaster in the resume repository)
  7. A link to the calendar that shows all meetings, meeting locations and important deadlines. The calendar should be kept up to date and is the go-to place if someone has forgotten when and where the next meeting is. The webmaster has already created a shell calendar in your web space that uses calendar software purchased by the course. Please use this calendar which is easy to edit from any web browser.
  8. The current Gantt Chart (jpg or pdf, not an MS Project file) and work breakdown statement (see below). Keep these up to date.
  9. The team mission statement
  10. A section for posting team deliverables that are listed on the schedule. Deliverables must be posted to this section on their due date.
  11. A section for posting meeting minutes.
  12. A link to the checkbook register for team expenses. A sample register file has already been created in your web space with the filename checkbook.html. It is up to you to keep it up to date with expenditures charged to the course and expenditures charged to the company.

Beyond this, material appropriate to the project can and should be added to the web site. Feel free to give your site some (professional) personality.

At the time of launch, your team web site should have all the items listed above, and placeholders for items due later. As the project proceeds, continue to enrich your website and to keep the meeting calendar and gantt chart up to date.


Gantt Chart and Work Breakdown Statement

The most widely used project planning and scheduling tool is the Gantt chart. Consult Ulrich and Eppinger or any project management text for the basics. A second essential tool is the work breakdown statement (WBS) which is basically a big to-do list of tasks sorted by heading and subheading. A comprehensive WBS has the resources required and responsible individuals tied to each listed task. Again, consult any project management text for details.

Teams must create and maintain a living Gantt chart and WBS with updates posted on the team web site. Please use Microsoft Project or equivalent software to make and manage your Gantt chart, but post in jpg or pdf format.


Breakfast

While you are planning, now is a good time to look at the course schedule and see when your team is responsible for bringing breakfast treats to class lectures.