SCOPE MANAGEMENT PLAN TO DIRECT YOUR EFFORTS

Task

This assignment follows from the case study used in Assessment 2. For the same case study, complete the following tasks by creating the following:

1. Scope management plan( including Requirements, In scope-out scope items, Deliverables and scope verification process) to direct your efforts. (10 Marks)
2. WBS first using either the free-form or the org chart format. (20 Marks)
3. Gantt chart-Take the WBS you have already developed. Define all of the activities that will be necessary to create each deliverable in your WBS. Create a schedule for your project. First create the schedule by hand using Post-it® Notes, and then put the information into MS Project. Take screenshots of the schedule to be pasted ni your word document that you are submitting. Be sure to include all of the summary rows (including the first row for the project title) and any key milestones. Make sure the critical path is easy to see.- (10 Marks)
4. Create a time-phased budget for your example project using bottom-up estimating. To the extent your sponsor will supply rates for workers, use those. Approximate rates for ones you cannot get. Ask your sponsor how they treat indirect costs. Be sure to include direct labour costs for you and your team mates and add 20% for fringe. State all assumptions and constraints you have used when creating your budget. State how confident you are in your estimates and what would make you more confident. Give examples of known knowns and known unknowns on your project. Tell how you have budgeted for both of them plus how you have budgeted for unknown unknowns. (15 Marks)
5. Create a risk register ( 4 risks- 3 negative and 1 positive risk)for your example project. (20 Marks)

Rationale

This assessment task covers topics 1 to 9 and has been designed to ensure that you are engaging with the subject content on a regular basis. More specifically it seeks to assess your ability to:

• demonstrate how a practicing project manager actually applies project management skills,
• methods, techniques and tools ;
• use an industry standard project management software tool (Microsoft Project);
• apply project management skills, methods, techniques and tools to a real world problem typical of a project manager;

Marking Criteria

Requirements

Students are required to submit the range of documents describing their proposed project solution for the above tasks.

Work Breakdown Structure (WBS)

• The first major section (1.0) should be project management and include the various project management deliverables such as charter, WBS, schedule, progress reports, etc.
• Deliverables should match those in the charter.
• Each item on the WBS should have a unique name.  If there is possible confusion between two items add an extra adjective to differentiate them. For example, two items could be “first draft report” and “second draft report.”
• Each line should be numbered with major sections being 1.0 then 2.0, etc.
• Each major section should be broken down into between three and twelve subsidiary sections. If further breakdown is needed, more levels should be used.
• All items on WBS are deliverables oriented (they are the “whats” of the project). Activities are defined as an outgrowth of the WBS and will appear in the schedule.
• The WBS can be submitted in free-form, org-chart, or indented-outline format.
• The WBS should appear to be complete with all interim and ending deliverables included.

Schedule / Gantt chart

• The schedule should appear to be complete given the charter and WBS.
• The schedule should appear to be reasonable without requiring heroics to complete on time.
• Include WBS column to left of task name column.
• Include overall project name as top row.
• Have all summaries stated in noun only format (or adjective noun – but on present tense verbs).
• Have all tasks (activities) stated in present tense verb-adjective-noun format.
• Have all milestones stated in noun and past tense verb format.
• All tasks should have dependencies shown – no loose ends.
• Display Gantt portion of schedule as large as possible.
• Show critical path in red (or distinctive hash marks if printer is only black).
• Show arrows with dependencies.
• Include no more than 40 lines per page – ensure it is large enough to read easily.

Include no more pages than necessary so there is little need to align multiple pages for reading unless it is a large schedule