You are on page 1of 6

Project

Assignment
Project Work Breakdown Structure (WBS) and WBS Dictionary
The goal of this Specialization is to provide you with the tools to more effectively and successfully
manage projects. A key part of this effort is to learn how to produce many of the key project planning
deliverables that are part of a well-developed project.

In this assignment, we will prepare a Project WBS based on the Wilmont’s Pharmacy Case Study found in
the Resource section of this Course. The student should use the Study as a basis to develop the assigned
deliverables for the project.

The Wilmont’s Pharmacy Case Study is based on a hypothetical case where a pharmacy company is
developing a drone project for home delivery of prescriptions. You may not be familiar with the
technology involved in the Case; however, the assignment is based on your knowledge of the typical life
cycle of a project and the contents of the associated deliverables. Therefore, you should focus on
developing a management plan for the project based on the lessons in the Specialization and not focus
on the technology and the details of the engineering.

The deliverable will be graded by your peers who are also taking the course. The grades will be based
on a Grading Rubric developed by the teaching staff and provided to each grader and your participation
in the grading process to review the deliverables of other students. Each student must complete peer-
review evaluations in order to get credit for the assignment.

Assignment Requirements

Format: The assignment must be uploaded in Electronic PDF-type print image file formatted in standard
US letter size pages by Adobe Acrobat or compatible software. The original document can be prepared
in any format of the students choosing as long as it can be converted/printed to a PDF deliverable.

Assignment Guidelines: Use the information provided in the Case Study as a guide to produce this
deliverable. You are not required to perform any outside research to add to the Case or to perform
additional studies over what is specified in the assignment to further define the Case.

A standard template is provided for this Deliverable. You are welcome to download and use these
templates to develop the assignment. Alternately, you can use a format that is derived from some other
standard from your organization or elsewhere as long as the contents contain the required information
and it is reasonably easy to follow by the Peer-reviewer without additional knowledge or training.

Assignment Deliverable Contents

Prepare a Work Breakdown Structure (WBS) for the entire scope of the Wilmont’s Pharmacy Drone
Project from the perspective of DroneTech Engineering. To complete the WBS, you should use the
information from both Part 1 and Part 2 of the case. The WBS should include all of the tasks to be
completed to complete the Project. The WBS should include the major deliverables outlined in the
Project Scope Statement plus the activities required to prepare them.

The WBS can be formatted as either as an organization chart or as a tabular listing. In either case, each
element must be numbered in a hierarchical fashion.
To complete the assignment, you should:

• Select a WBS shaping factor – Project Phase, System or Area – to help you structure the tasks.
The choice should reflect your thinking on how the Project will be executed and how the tasks
will be divided. Remember, it is usually a good idea to be able to assign each major area to one
manager responsible for that work. Consider how you structured your organization chart as a
guideline.
• Show at least 3 task detail levels in most areas of your WBS deliverables or phases(Major task
level and 2 additional subtask levels)
• Include appropriate Project Management tasks such as team meetings, training, and testing.
You should also include Project Controls, Quality and Procurement tasks.
• Break the work into manageable work packages that include all of the work to complete a
deliverable and all of the deliverables.
• Include all of the numbering features described in the Course Videos, PMBOK and Project
Management Toolbox
• Include a WBS Dictionary either as part of the WBS table (if the WBS is in tabular format) or as a
separate document. The WBS Dictionary should contain the following information as a
minimum:
o Code of Account identifier
o WBS element name
o Description of the Work
o Assumptions and constraints
o Exclusions (if required)

In preparing your WBS it is important to remember that it will form the basis of future cost estimates
and schedules. It is the next level of detail in your Project Scope Statement. To fully develop the WBS,
the student should reflect on the steps, procedures and systems required to properly take the
customer’s original order for a product through Wilmont’s and then carry through until DroneTech can
deliver the product according to plan. There are various aspects of this plan that must be added by the
student in addition to the key points mentioned in the Case. These might involve contract negotiations,
engineering of specialized devices, training of staff, preparation of manuals, management reporting and
developing information systems as examples.

Remember that the brief descriptions included in the WBS Dictionary will give guidance on your intent
to those reading the WBS and also in the future when you refer back to it.

Grading Rubric for Peer Review

Following are the general guidelines for evaluation of this assignment. The student should use these
guidelines to aide in the preparation of the Project WBS and WBS Dictionary. If you are uncertain as to
the specific requirements, please refer to the Project WBS and WBS Dictionary Templates in the
Resources section of Coursera, the Assignment Video, Chapter 5.4 of The Project Management Body of
Knowledge, 6th edition, and pages 126 to 143 of Project Management ToolBox, Tools and Techniques, 2
nd edition for additional information. Also, please feel free to post any questions you may have in one
of the discussion forums created for this Specialization.
Project WBS and WBS Dictionary Grading Rubric
The Project WBS and WBS Dictionary document will be rated based on the following scales. Provide
specific written feedback to explain your rating.

Project Name, Document Revision Number and Date – The Project WBS and WBS Dictionary contain
the Project Name, the Document Revision Number and the Revision Date.

Poor (0) Average (7) Good (8) Very Good (10) Rating =
Name and The Project WBS One of the two Both the Project WBS
Revision and the WBS documents includes and WBS Dictionary
Number Dictionary includes the Project Name, includes the Project
Missing. the Project Name, the Revision Number Name, the Revision
but not the Revision and Revision Date. Number and Revision
Number or the Date.
Revision Date.
Comments:



Project Scope – The WBS should describe the scope of the project down to the work package level. It
should describe both the product/physical scope of the project and the services scope.

Poor (1) Average (7) Good (8) Very Good (10) Rating =
The WBS does The WBS describes Project WBS Project WBS includes a
not reflect the the Project scope includes a detailed description of
Project Scope. but the main description of the the activities/scope of
activities/scope do main activities the Project. At least 3-4
not reflect the that make up the task detail levels included
deliverables/work scope, but does for most of the WBS. The
scope listed in the not include any WBS is well coordinated
Project Scope Project goals. with the Project Scope
Statement. Statement.
Comments:





Deliverables – Each major deliverable is listed in Level 2 with sublevels describing the activities or steps
required to accomplish the deliverable.
Poor (1) Average (14) Good (16) Very Good (20) Rating
=
No Project WBS contains Project WBS contains All of the major
deliverables deliverables and both product and Product and Services
list included outcomes, but they are services deliverables. deliverables are listed.
in Project not easily tied to the The deliverables can be They are tied to the
WBS. Project WBS. easily linked to the Project Scope
Project Scope Description and the
Description. deliverable description
makes them easily
identifiable.
Comments:






Logical Layout – The hierarchical structure of WBS makes logical sense. Only one WBS shaping factor is
employed for the entire structure and it is consistently applied.

Poor (1) Average (7) Good (8) Very Good (10) Rating =
The shaping One of the three The Project WBS Project WBS includes a
factor used – major shaping incorporates only single shaping factor for
phase, system factors – phase, one shaping the entire chart and it is
or area – is not system or area – is factor throughout broken down into a
readily used at the upper the document. minimum of 3 levels for
apparent. levels, but it is not most of the WBS. The
apparent in the lowest Work Package level
lower levels. represents manageable
tasks.
Comments:





Number Sequence – Each WBS element is number using a hierarchical number sequence similar to
those described in the Course material.

Poor (1) Average (14) Very Good (20) Rating


=
The Project WBS The numbering The Project WBS
does not system is included, includes a hierarchical
contain a but it does not follow numbering system in
numbering a hierarchical the proper format. It
system. methodology similar is clear and specific.
to that in the Course
Material.
Comments:




WBS Dictionary – A WBS dictionary should be included with the WBS. It can either be included with the
WBS if the WBS is in tabular form or it can be a separate document.

Poor (1) Average (7) Good (8) Very Good (10) Rating
=
A WBS The section is Each entry into the Each entry into the
dictionary is not included, but major WBS dictionary WBS dictionary
included. requirements are includes the includes the sequence
missing. sequence number, number, name, a brief
name, and a brief description plus any
description. assumptions,
However, constraints or
assumptions, exclusions, if required.
constraints and
exclusions are all
missing.
Comments:





WBS Format

Poor (1) Average (7) Good (8) Very Good (10) Rating =
The Project The information in the The format is easy to The Project WBS is
WBS is not Project WBS is laid out follow and well formatted in a
formatted. in a readable fashion. labeled. It is not standard easy to follow
Information is However the sections obvious that the format. Each section is
included in a are not well labeled format is standard labeled so it is easy to
random and the format should and can be used compare data to future
fashion. not be considered across projects. projects.
standard.
Comments:




WBS Dictionary Format

Poor (1) Average (7) Good (8) Very Good (10) Rating =
The WBS The information in the The format is easy to The Project WBS is
Dictionary is WBS Dictionary is laid follow and labeled. It formatted in a
not formatted. out in a readable is not obvious that standard easy to follow
Information is fashion. However the the format is format. Each section is
included in a sections are not standard and can be labeled so it is easy to
random labeled and the format used across projects. compare data to future
fashion. should not be projects.
considered standard.
Comments:




TOTAL =

General Comments and feedback – What specific approaches worked well? Areas for improvement?

You might also like