CASE STUDY: PROJECT MODEL PART 1 INSTRUCTIONS

The following documents will be submitted in 1Word document.

1. Create a Project Proposal Form for your project in Microsoft Word.Use page 44 of the text as a guide.

2. Create a Responsibility Matrix for your project in Microsoft Word or Excel. Use page118 or page 119 ofthe text as a guide (select the one that best fits your project). Add this table to your developing project and use a new page to present your matrix.

3. Create a Risk Response Matrix for your project in Microsoft Word or Excel. Use page 217 ofthe text as a guide. Add this table to your developing project and use a new page to present your matrix.

4. Create a Stakeholder Communication Plan for your project in Microsoft Word. Use page 122 ofthe text as a guide. Add this table to your developing project and use a new page to present your plan.

5. Save the file in this format: LastName_Title_of_Project

CASE STUDY: PROJECT MODEL PART 2 INSTRUCTIONS

The following documents will be submitted in 2 Microsoft Project documents.

1. Open a new project in Microsoft Project. Save the file in this format: LastName_Project_Name

2. Provide some overarching information about your project. In the Notes file for the project, describe the project and list the keydeliverables. Include any other information that may be helpful to your project.

3. Establish a project start date. In the Notes section, explain why you selected this date.

4. Create a work breakdown structure (WBS) by decomposing the scope for your project into deliverables and enter these as "tasks" in your project file. You musthave at least 5deliverables.

5. Decompose the deliverables further into work packages (tasks) and enter them under your deliverables.It is helpful to keep your deliverables as nouns, and to use verbs for each task. Include enough detail to have 20-25 unique tasks.

6. Use the "Indent Task" button to create a hierarchy that delineates deliverables and tasks.

7. Code the project following the 1.1, 1.1.1, 1.2 format.

8. Establish the project schedule by estimating time durations for all of your individual tasks. Enter the duration (in days) for each task.

9. Using a task'sNotes feature, justify the time estimates for at least 5tasks. For example, you might make the following note: "This will take 3 days to allow the paint to dry before applying the trim."

10. Enter at least 3milestones for your project. Milestones typically use passive verbs (i.e. Phase 1 completed) and do not have any duration assigned to them (0 days).

11. Link all of your individual tasks and milestones. You can use the "link" button (appears as a chain link) after selecting the 2 tasks to be linked. Note that there are numerous ways to link tasks.Vary your linkages by including at least 2relationships that are not Microsoft Project's default(Finish-to-Start) relationships.

12. Not all tasks start immediately after a task ends (they "lag") or wait until a task is completely finished before starting (they "lead"). Therefore, have at least 1 task include lead time or lag time. In the Notes section for this task, indicate why there would be a lead/lag for that particular task.

13. Next, begin to assign workers and estimate your resource costs. Enter at least 6 humanresources on the Resource Sheet.

14. Add comments to at least half of your resources to provide information about those resources.Note things such as why they were selected, potential scheduling issues, a potential back-up, or other information that a project manager might find helpful.

15. In order to determine the budget for your project, you must input your labor costs. After your resources are entered, include wage rates for each individual resource.

16. For every task, assign the appropriate resource(s). Do not assign resources to summary tasks (your deliverables) or milestones (event markers).

17. If Microsoft Project displays a red human resource icon, the associated resource is over-allocated.Determine how best to address the problem and make the needed changes. If a resource can be over-allocated, justify the "why" in the task'sNotes.

18. When tasks, costs, and resources are entered correctly and you have double-checked for accuracy, set the project baseline. This sets the budget and schedule for the project.

19. Save the assignment.

20. Next, display the project as a network diagram toshow the critical path in your project. Remember, not all of your tasks should be in the critical path. If they are, change task relationships as needed.

21. Save the file in this format: LastName_Project_Name_ND and submit.