Project Schedule - Team Assignment
Description
Schedule:
For
the project schedule, you are going to create your estimate of the
full project execution. This should start where we are now
and continue through the rest of the lifecycle (design, construction,
testing, deployment). If you have planned to do an iterative process
you should break up the project into several smaller cycles
(minor releases) each with its own subphases. After completion the
construction portion of the schedule should have no tasks longer than 1
week. (Other sections may have longer more general tasks.)
EXAMPLE SCHEDULE
Note: I have not leveled the resources
Cost:
Using
the project scheduling tool, you should be able to assign a cost to
each resource and then determine the total project cost. (Hours *
hourly rate). Turn in the cost and number of hours for each employee.
Include also the total project cost.
Critical Path:
In
addition to the schedule, also turn in the list of tasks that form the
critical path. This can just be a Word document. The list of tasks
should include an overall liklihood estimate that the task will not be
on schedule (1-5 scale). In addition there should be an overall impact
if this task is not on schedule (1-5). The idea is to begin evaluating
the level of risk your project has and what happens if one of those
risks occur. This information will be used later during risk assesment
of your project.
Grading Criteria
Schedule (85%)
-
The schedule is done with an appropriate project scheduling tool (see
class website for a list). If you want to use another tool, ask in
advance
- All tasks have a person or people assigned to them
- All resources are leveled - no person works over 8 hours / day
- Project broken up into major sections (design, construction, testing, deployment)
- Construction broken down into smaller sections with lowest level tasks no longer than 1 week
- Construction phase is specific to your project -- your tasks should be in here, not general tasks
- All use cases are in the schedule (this also means that the schedule fully covers the requirements)
- Dependencies among tasks are present among tasks where appropriate
Cost Estimation (5%)
- Assuming a rate of $100/hour. What is the estimated cost for each person from this phase (design) to the end? (2.5%)
- What is the total estimated cost to implement the project from this phase (design) to the end? (2.5%)
Critical Path (10%)
- The correct critical path is given with each task and the corresponding ID from the schedule (5%)
- With each task there is an overall liklihood this task will not be on schedule (1-5) (2.5%)
- There is an overall impact of the task not being on schedule (1-5) (2.5%)
What to turn in:
- A printout of the Word document (including critical path, cost estimate)
- A printout of the Gantt chart
- A printout of the schedule including columns: description, start date, end date, duration, predecessors, resources