PRJM 6000 Project Management Overview :
PRJM 6000 Project Management Overview Assessment 2: Report and Case Study – Project Charter, Scope Management, Project Planning (40%)
Aim of Assessment:
- Create a Project Charter & Work Break Down Structure
- Apply scope change management processes
- Demonstrate understanding of project planning through the analysis of a case study
Project Charter, WBS, Scope Changes
[NOTE: Part A is a practical assignment. No academic references are required. It is not presented as a piece of academic writing. The Charter and WBS must be written as formal project documents to the presentational style expected in a real project]
Select a project.The project can be:
- One that you are presently involved in or a project happening in the future in which you will be involved – either a business or social project.
- A hypothetical but relevant project.
- Produce a project charter for your project containing the following sections (template is available on Blackboard under Assessments)
- Problem / Opportunity Statement (6 marks)
- Strategic Alignment (6 marks)
- Benefits (6) and their KPIs (6) (12 marks)
- Deliverables (6 marks)
- Functional requirements (6 marks)
- Risks, Cost, Timeframe (0 marks–just provides experience of completing full charter)
- Produce a Requirements Traceability Matrix using the template provided in Blackboard under Assessments, list 3 non-functional -requirements then trace to features in the final deliverable components (6 marks).
- Create a Work Breakdown Structure (WBS) using the template provided in Blackboard under Assessments: (list format, not chart format). (Note: the WBS must contain at least 15 work packages/tasks. If you have a large project, provide the top-level elements, and decompose 1, 2 or 3 of these elements so that at least 15 work packages/task are created (12 marks).
- Describe a possible scope changerequested by the sponsor. Fully evaluate the requested change. Produce and explain revised sections of WBS, assuming that the change is accepted(10 marks).
Case Study: Victoria Level Crossings Project (See link for Case Study) (See separate information sheet within Assessment menu for case study)
Part B can be undertaken as a GROUP assessment. Groups of 2 or 3 can be formed by signing up to a group via the Groups menu item.
In answering the case study, make any necessary but reasonable assumptions. Support any answers with direct reference to the text in the case study. Some outside research may be required to sufficiently answer all questions.
- What are the (16 Marks):
- One suitable KPI for one of the benefits from the overall project – Do not use a benefit listed in the auditor general report
- Strategic alignment
- Describe one specific project planning problem encountered in this project, and how each may have been avoided or better managed. (10 marks) (200-300 words).
- Describe one specific example of good project planning in the project. (10 marks) (200-300 words).
Students must use the templates provided in Blackboard under Assessment.
- Do not change fonts, spacing, text size or format. The assessments must be A4 paper in one-and-half spacing using Arial Narrow, 12 font.
- All pages should be numbered.
- All assessments should be thoroughly checked for typing, spelling and grammatical errors before being submitted.
- Submit both parts of the assessment as WORD document through Turnitin.
All source material MUST be acknowledged and any form of plagiarism will result in the appropriate measures being taken. Do not copy other student’s work or assist by showing your work to others.
Assessments must be submitted online through the correct Turnitin drop-box on Blackboard (not through email or in person).
Late submissions will be penalised as per the Curtin Late Assessment Policy in the Unit Outline.
Note: Each Student must complete and submit Part A individually. Only one member of each group should submit Part B. Groups where more than one member submits a final draft of Part B will receive a 5 mark deduction.
Assessment 2 Marking Criteria (40%)
|Charter – Problem/Opportunity||/6|
|Charter – Strategic Alignment||/6|
|Charter – Benefits||/6|
|Charter – Key Performance Indicators||/6|
|Charter – Deliverables||/6|
|Charter – High-level Functional Requirement(s)||/6|
|Requirements Traceability Matrix||/6|
|Work Breakdown Structure||/12|
|Part A: Charter, WBS, scope||/64|
|Deliverables, Benefits, KPI, and Strategic alignment||/16|
|Project planning problem||/10|
|Good project planning||/10|
|Part B: Case Study||/36|
|Key Functional Requirements|
|APPROVAL Yes / No Authority: ______________________________ Date:____________ Sponsor|
|REQUIREMENTS TRACEABILITY MATRIX|
|Non-Functional Requirements||Deliverable component|
|WBS #||WBS – ELEMENT|
(insert extra rows as needed)