Project Schedule main content
Assignment Learning Objectives
Be able to
- Use Microsoft Office Project 2007
- Create a Work Breakdown Structure with summary tasks, subtasks, and milestones
- Estimate effort (duration), assign task dependencies (links), and resources (names) to schedule a project
- Use a Gantt chart to illustrate the schedule of a software project
- Use a Resource Usage Report to fairly allocate project work
Assignment
Use Microsoft Project to develop a work breakdown structure and schedule for the team work in CS 480 for this quarter only.
- Use the CS 480 Assignments deliverables for the major phases (summary tasks) for the project
- Limit this assignment to the work required for CS 480
- Develop a detailed work breakdown structure by creating a hierarchy of summary tasks, subtasks, and milestones for CS 480 project work
- Develop a project schedule based on the work breakdown structure and CS 480 deadlines
- Estimate durations in hours or minutes
- Create
FStask dependency relationships between tasks - Create your team people resources names and assign resources to all subtasks
Project Settings
For consistency,
- Start your project on October 23, 2007
- Assume a 2-hour workday, 5 days a week (10 hours per team member per week)
- Give yourselves the following holidays off
- Monday, Nov. 12 (Veterans Day)
- Wednesday, Nov. 21 through Friday, Nov. 23 (Thanksgiving)
- Set the default duration and work to display in hours
- From Tools menu, select Options..., click Schedule tab, and change days to hours
- Add the WBS outline number (1, 1.1, 1.1.1, etc.) to the display view
- from the Tools menu, select Options..., click View tab, and check show outline number
Note: Scheduling of your CS 480-481 project is simple compared to most real-world projects. You team must work within the constraints of the university's quarter system and most of the major milestone deadlines have already been set for you and cannot be extended.
The real scheduling task of CS 480-481 involves defining the scope of your project in such a way that it fits into the constrained time schedule. When specifying your project scope and requirements, do not err by becoming overly ambitious or overly optimistic. Software development usually takes longer than your initial estimates. Work with your faculty advisor to specify an appropriately sized project.
Grading criteria
A scoring rubric [PDF] will be used for assessing this assignment. You are encouraged to print this rubric and use it as a checklist for expectations, guidelines, and quality assurance.
Honor code: The work needs to be your own. You may receive assistance in the lab with the software, but you need to complete the work yourself.
Submission Guidelines
Prepare a short report consisting of
- Cover page
- Include your team name & logo, project name, and date
- Include the names of the team members who worked with Microsoft Project on the production of this CS 480 schedule
- Task Sheet
- In Microsoft Project, open the View menu, click More Views ..., and select Task Sheet
- Include the following column fields (default): ID, Indicators, Task Name, Duration, Start, Finish, Predecessors, and Resource Names
- Include the WBS hierarchical outline numbers (e.g. 1, 1.1, 1.1.1, 1.1.2, 2, 2.1, etc.).
- From Tools menu, select Options, click View tab, and check show outline number
- Use Page Setup when you print your task sheet so that it prints 1-page wide. It may need more than 1 page tall depending on your level of detail
- Gantt Chart
- Print your Gantt chart in landscape orientation, 1 page wide by 1 page tall, and use 11" x 17" paper size
- The printer in Hebeler 218 is capable of printing black and white 11" x 17" sheets of paper
- Jerrol's sells single sheets of 11" x 17" paper
- Check that your printout of the Gantt chart is correct first with MS Project's print preview
- Fan-fold your Gantt printout to 8.5" by 11"
- Your Gantt chart only needs the Task Name column (with WBS numbering) displayed on the printout
- Resource Usage Report
- Available from the Report menu, Reports ..., Workload, Resource Usage