GRADING RUBRIC FOR WEB PROJECT

Note: I try to change the Web Project every year. Some of the information you find here is stated generically. Depending on the project we might have additional criteria. If so we will communicate this to you via email.

Grading Distribution:

The Project is weighted at 33% of your entire course. We will evaluate the project using two criteria and a ratio of 65: 35

• Project Management: 65% pertains to Project Management.
• Web System: 35% is allocated towards submitting a working Web System.

Project Management (65%):

Peer Evaluation = 20%
Project Mentor/Instructor’s perception of Project Management = 20%
Submitting the following documents = 80%
Your documents don’t have to be precisely as suggested in the Sample PDF or the other PDF from a previous team emailed to you.

• (eg., Did you manage the project well? Evidence should be provided to your
  Mentor eg., turn in a report summary indicating that you exceeding expectations,
  turn in additional templates or deliverables.)
• Business Case (Similar to Chapter 3 Table 3-4)
• Team Contract (similar to Chapter 3 Table 3-6)
• Scope Statement (Table 3.7)
• Project Plan
   Purpose/background/approach
  Goals/objectives
   Scope
   Deliverables
   Constraints/assumptions
   Related subprojects/critical dependencies
   WBS (Figure 3-2) –Could export to VISIO (WBS levels 1. 2 and 3 maximum) or print in powerpoint. (see Appendix A)
  Schedule and milestones (MS PROJECT)
  Tools and techniques used
   Budget for project: [Your hourly rate is $100. Cost for Hosting  in your case it is $200 per year --for hosting). Make assumptions. ]
   Risk Management (Identification, quantification, mitigation, Contingency plan)
   Quality Standards & Quality management approach & Quality Control
   Change and control procedures (tell us how you managed changes/scope creep)
   Project Notebook
  --Roles/responsibilities
  --Team Blog
  --Team contact directory, Team meetings (dates and who attended and who requested to be absent).
  --Weekly Status Report (See table 3-12)
  --Who does what when (MS PROJECT gives this report)
  All of the above plus the IT system below constitutes your Final Project Report (Also see table of content in Table 3-15 in Chapter 3 of your Scwalbe text.)

Web System (35%)

You will get a B to A- range if you provide a fully functional web system that successfully implements the web based project.
To get an A for the project you must EXCEED expectations. Document the cool Web features programmed, whatever they may be. Communicate that clearly to your facilitator.
Technical Documentation that you are strongly encouraged to submit:

• Design Specs and Code.
• Site map and user Manual (how to use your web application) turn in URL and passwords.
• Quality Planning, Testing and QA evidence. (No need if you turned this in the Project Management section.)
• Technical Specifications
• Database Schema

Powerpoint Project Presentation is Required:

• You are required to participate as a team in the final project presentation. More details on that from your instructor in the last week of the course.
• We will also email you a sample PPT from the previous students.