PPMP20008 WBS and Work Package

This assignment requires the development of a Work Breakdown Structure (WBS) and a work package, adhering to PMBOK v5 and PRINCE2 (2009) standards. The WBS must have at least three levels, with work packages at the lowest level, and the work package should include details such as a signature block, work package description, configuration management requirements, joint agreements, tolerances, constraints, reporting arrangements, problem handling, references, and approval methods. The assignment emphasizes clarity, conciseness, and correct grammar, and requires submission in Microsoft Word format.

PPMP20008
Assessment 3:
Work Breakdown Structure and Work Package
(Extra voluntary activity: There is a mistake in this document. There were mistakes on the other
assessment documents. Did you notice them? If you find it, it might be worth noting down. Think
about your feedback on your assessments. Were there comments about checking your work?
What ways do you check your work before submitting it? In project management how would this
‘check’ occur?)
Assignment Overview
This assessment item requires you to develop :-
 Work Breakdown Structure (WBS), and
 a work package
The submission must comply with the requirements outlined in the PMBOK v5 and PRINCE2
(2009). You are to develop and complete the documents as the project manager for the project
supplied. Do not simply describe the purpose of the documents.
Assessment Due Date Week 8 Friday (08-Sep-2017) 11:45 PM AEST
Return Date to Students Week 10 Monday (18-Sep-2017)
Weighting 20%
Assessment Criteria
Your assignment will be assessed on the extent and quality to which it meets each of the
following criteria.
1. The project management concepts within the work breakdown structure are applied
appropriately and it is an accurate reflection of the project described in the selected
tender (5 marks)
2. The project management concepts within the work package are applied appropriately
and the quality management plan is an accurate reflection of the project described in the
selected tender (15 marks)
Ensure your submissions are submitted in an appropriate format, are concise, demonstrate clarity
of expression, and correct grammar and spelling.

Assessments provide the opportunity for students to demonstrate their knowledge and skills to
achieve the required standard. To do this, assessment responses need to be both clear and easy
to understand. If not, the University cannot determine that students have demonstrated their
knowledge and skills. Assessments will, therefore, be marked accordingly including the potential
for 0 (zero) marks where relevant.
Include only Microsoft Word Files for this assessment. There should be two separate files, one for
the WBS and one for the Work Package.
Do not include PDFs, Zip files or pictures within word files.
Work Breakdown Structure
For the assessment the WBS must have at least three levels (make this simple and don’t go further
than three). Make sure your lower level are WORK PACKAGES, not activities.
There should be no more than six to ten work packages in your work breakdown structure.
Include the WBS identifier on each item. It is likely better to have the project (top level) identifier as
zero.
Each parent item on the WBS must have at least two items coming from it.

Work Package
You only include one single example of a work package. Make sure you choose one that is at the
lowest level of your WBS. Be strategic about which one you choose. Make it one that you
understand well and can provide appropriate information for under each heading.
The below provides an outline of what will be required in the work package. If cutting and pasting
from this document to form a template, DO NOT include notes, hints etc. Ensure that you are clear
what the heading are and what they refer to.
Make sure that this is one of the items on the bottom level of your Work Breakdown Structure.
Markers will look at the consistency between the scope baseline and this document.
This information has been formulated from:-
Work Package (WP) composition is outlined in the Appendix at the back of the Prince2
text. (A.26) for the 2009 Edition of Managing Successful Projects with Prince2 the page
is 261.
Title Page (first page)
Index (2nd page)
On the third (and subsequent) page/s include the following:
Signature Block –
(NOTE: This can be at the front or the back of the WP. Include both the Project Manager and the
Work Package Team Manager (also termed WP Leader - who is responsible for delivering the work
package) that includes:
o Project Manager: (Name, role, organisation)
o Signature (space for signature)
o Date (Here the project manager notes the date they signed)
o Work Package Team Leader: (Name, role, organisation)
o Signature (space for signature)
o Date (Here the project manager notes the date they signed)
Work Package Description
Techniques, Processes and Procedures
Development Interfaces
Operations and Maintenance Interfaces
Configuration Management Requirements
For the assessment you only need to include a simple sentence or two explaining how you will
version both specialist and management products.

Students can get confused by this concept (as can organisations) although it is more than just
version control, it may be a good way to consider it.
Your text talks about configuration management and there are a lot of online blogs that explain in
simple terms what it is and why it is important e.g.
https://www.upguard.com/blog/5-configuration-management-boss
Most people utilise configuration management in their everyday lives, think about a smart phone, if
you are an Apple iPhone, what version of the iOS are you currently using? Why is it important to
know this? Why does Apple use a numbered system to name each version?
Do you version the drafts of your assessments? Or do you just know which draft you are working on?
Do you save drafts each time you make a substantial change or do you just type over a single
document?
Joint Agreements
Note: these are for the work package not for the entire project.
o Cost
o Start and end date of the work package
o Key milestones (note – don’t write these as activities)
o (note this would normally include effort as well but not needed for this assessment)
Tolerances
o Cost tolerance
o Time tolerance
o (this can also include tolerances for Scope and risk however this is not needed for
this assessment)
Constraints
Do not include cost or time constraints. Only include one contraint.
Reporting Arrangements
(Note the work package team manager will report progress to the project manager – not directly to
the project board. The project manager will collate all reports from the WP team managers and put
the information into the progress report to the board. This section asks you to specify when and how
the WP team manager reports progress of the WP to the Project manager.)
 Frequency of Reports
 Content of Checkpoint Report
Problem Handling and Escalation

Extracts or References
(Note these are not academic references here but relate to previous project documentation. For the
purposes of this assessment – this can be brief and can simply state something like ‘For [add in what
it is] please refer to the [what the document is] or similar). This wording is not to be used for any
other section of this document.
Approval Method
(Note this is not the signature block for this document) it states who will approve the completed
products within the work package (make it easy – in most cases this will be the project manager) –
and how the project manager is to be advised of the completion of the work package (think WP
finalisation report).