Project Management Plan

Value:20%

Due date:16-May-2016

Return date:07-Jun-2016

Submission method options Alternative submission method

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. Change request form. (Determine what level of changes you as an individual can make without further approval, what changes you as a student team can make, and what changes your sponsor needs to approve.)(10 marks)
3. WBS first using either the free-form or the org chart format.(20 marks)
4. 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-itNotes, 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
5. RACI chart.(10 marks)
6. Histogram of demands on each key participants time from MS Project.(5 marks)
7. 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)
8. Create a risk register ( 4 risks- 3 negative and 1 positive risk)for your example project.(20 marks)
9. Length, format, References and writing style(5 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

	STANDARDS
Criteria	FL	P	C	D	HD
Task 1 Scope Mgt Plan - Requirements, Scope details (5 marks)	unclear attempt that is ambiguous / incomplete	Defined Requirements but ambiguous / incomplete.	Clear description of requirements and in scope items defined.	Defined description of Requirements and in-scope items and out-of-scope items.	Clear description of Requirements and in-scope items and out-of-scope items relevant to the case study
Task 1 Scope Mgt Plan - Deliverables and Scope verification (5 marks)	unclear attempt that is ambiguous / incomplete	Defined deliverables but ambiguous / incomplete.	Clear description of deliverables and scope verification defined.	Clear description of deliverables and scope verification	Clear description of project scope, including named deliverables. Scope verification/ acceptance is also defined relevant to the case study.
Task 2 - Change Request Process (5 marks)	unclear attempt that is ambiguous / incomplete	Considered CR process but unclear	Reasonable CR process is defined.	CR process includes approvals from appropriate stakeholders.	CR process includes approvals from appropriate stakeholders & forms / templates.
Task 2 -Change Request form (5 marks)	unclear attempt that is ambiguous / incomplete	Form included but unclear	Reasonable CR form is defined.	CR Form includes most important items.	CR form includes all items required by the process.
Task 2 - Work Breakdown Structure (WBS) - 20 marks	unclear attempt that is ambiguous / incomplete	WBS is mentioned with some breakdown of Project Scope.	WBS is structured, having detailed coverage for Project scope / Phase of project.	WBS is well structured, having logical and complete coverage for Project Execution	WBS is structured, having logical and complete coverage for Project Execution and integrated into Project Schedule and Resource Matrix.
Task 2 - Gantt Chart (10 marks)	unclear attempt that is ambiguous / incomplete	Gantt chart shows- some activities included, schedule created, summary rows shown, few /none milestones shown	Gantt chart shows- some activities included, schedule created, summary rows shown, first row shows project title , total duration shown, some milestones shown, critical path shown	Gantt chart shows- most activities included, schedule created, summary rows shown, first row shows project title , total duration shown, most milestones shown, critical path shown	Gantt chart shows- all activities included, schedule created, summary rows shown, first row shows project title , total duration shown, all necessary milestones shown, critical path shown and easy to see
Task 2 - RACI chart(10 marks)	unclear attempt that is ambiguous / incomplete	Tasks according to the WBS defined Role assignments done Parties identified to be responsible for, consulted on (i.e., help), informed, or approve results on a RACI chart	Tasks according to the WBS defined Tasks are clearly defined with no ambiguity Role assignments done Parties identified to be responsible for, consulted on (i.e., help), informed, or approve results on a RACI chart	Clearly state tasks according to the WBS Tasks are defined with clear completion exit points Tasks are clearly defined with no ambiguity Clear role assignments Appropriate parties identified to be responsible for, consulted on (i.e., help), informed, or approve results on a RACI chart	Clearly state tasks according to the WBS Tasks are defined with clear completion exit points Tasks are clearly defined with no ambiguity Thoroughness of tasks to be completed Clear role assignments Appropriate parties identified to be responsible for, consulted on (i.e., help), informed, or approve results on a RACI chart o Involved parties are appropriately identified
Task 2 - Resource Histogram(5 marks)	unclear attempt that is ambiguous / incomplete	Resource histogram shown but ambiguous / incomplete.	Resource histogram shown	Resource histogram shown clearly	Resource histogram shown clearly with resource names displayed and labelling done
Task 2 - Budget (15 marks)	unclear attempt that is ambiguous / incomplete	Bottom-up estimating done, few assumptions and constraints you have used when creating your budget stated. Budget extracted from MS Project showing overall budget	Bottom-up estimating done. some assumptions and constraints you have used when creating your budget stated. Examples of known knowns and known unknowns on your project given. Budget extracted from MS Project showing overall and breakdown for all summary tasks and resource	Bottom-up estimating done. Direct labour costs for you and your team mates and 20% for fringe included. Most assumptions and constraints you have used when creating your budget stated. Confidence level for estimation stated. Examples of known knowns and known unknowns on your project given. Budget extracted from MS Project showing overall and breakdown for all summary tasks and resource	Bottom-up estimating done. Direct labour costs for you and your team mates and 20% for fringe included. All assumptions and constraints you have used when creating your budget stated. Confidence level for estimation stated. Examples of known knowns and known unknowns on your project given with explanation. Budget extracted from MS Project showing overall and breakdown for all summary tasks and resource along with various costs
Task 2 -Risk Register(20 marks)	unclear attempt that is ambiguous / incomplete	Some values of Risk register are accurate and Consistent, someitems of the register complete.	Most values of Risk register are accurate and Consistent, most items of the register complete.	All values of Risk register are accurate and Consistent, all items of the register complete.	All values of Risk register are accurate and consistent, all items of the register complete. Risks are relevant to the case study
Length, Format, References and writing style. (5 marks)	No references given.	Exceed word or page limit criteria by over 1 page. Font, spacing, and citation format are incorrect or needs refinement.	Exceed word or page limit criteria by 1 page. Font, spacing, or APA format is mostly correct.	Exceed word or page limit criteria by less than 1 page. font or spacing and APA are correct.	Adheres to word or page length criteria, font, spacing, and APA or similar citation format are correct.

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.

RACI Chart

• Clearly state tasks according to the WBS
• Tasks are defined with clear completion exit points
• Tasks are clearly defined with no ambiguity
• Thoroughness of tasks to be completed
• Clear role assignments
• Appropriate parties identified to be responsible for, consulted on (i.e., help), informed, or approve results on a RACI chart
• Involved parties are appropriately identified

Resources on Schedule Show clearly the overall project, the individual tasks, which are critical and which are not, and who is assigned to each in the upper pane.In the lower pane, a resource who has multiple tasks is shown with any overloads identified.The scale is easy to read and includes the entire project.Columns may be hidden to allow as much room as possible for the detailed Gantt chart and the resource graph. All referencing in the project material must be in accordance with the APA style guide. A guide to the APA style of referencing (the style now used by the Faculty of Business) is available at:http://student.csu.edu.au/study/referencing-at-csu