Project

Assignment
Project Stakeholder Register
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 Stakeholder Register 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 a minimum of three of 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 a minimum of three peer-review evaluations in order to get credit for the assignment.

Assignment Requirements

Due Date: The assignment must be submitted by the start of Module 5 of this Course. Late assignments
may not be Peer-reviewed and therefore not receive a grade.

The assignment should be uploaded into Coursera in the space provided in Module 5 of this Course.

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

You are the DroneTech Engineering’s Project Manager for the Wilmont’s Pharmacy Drone Project. As
part of the process of planning your Project, you need to identify the Project Stakeholders and create a
Project Stakeholder Register.
Create a Stakeholder Register for the Wilmont’s Pharmacy Drone Project. The Stakeholder Register
should include:

• Name of the Stakeholder

• Organizational Position
• Location
• Role on the Project
• Project Expectations
• Interests
• Influence on Project Outcome
• Type of Communication Recommended

The Stakeholder Register is a compilation of those who will have an influence on the outcome of the
project and will include people in the Wilmont’s organization, the DroneTech organization and
potentially third parties. It should be a tabular document and have the capability to be updated
throughout the project.

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 Stakeholder Register. If you are uncertain as to the
specific requirements, please refer to the Project Stakeholder Register Template in the Resources
section of Coursera, the Assignment Video, Chapter 13 of The Project Management Body of Knowledge,
6 th edition, and pages 423 to 436 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 Stakeholder Register Grading Rubric
The Project Stakeholder Register document will be rated based on the following scales. Provide specific
written feedback to explain your rating.

Project Name, Project Phase and Date – The Project Name and any reference information should be
included in the Register. There may be different registers for different phases of the project. The
Stakeholder Register should indicate which Project Phase is represented. The Stakeholder Register is
likely to go through several revisions throughout its life. The form should include the date of the current
revision and may also include a revision number.

Poor (1) Average (3) Good (4) Very Good (5) Rating =
The Project The Project Name One of the items The Project Name, the
Name, Phase is included but not is missing. Project Phase, the
and Date are the Phase or the revision date and the
not included revision date. revision number are all
included as part of the
Register
Comments:

Name of the Stakeholder – At its heart, the Stakeholder Register is a list of the key Stakeholders on the
Project. It should contain the names of these Stakeholders in both the Wilmont’s organization, the
DroneTech organization and any third parties (if any)

Poor (1) Average (14) Good (16) Very Good (20) Rating =
The The 4+ Most of the key All of the Key
stakeholders stakeholders are stakeholders are Stakeholders are listed by
are not not listed or the listed, but 2-3 name. Both
included on stakeholders are have been left organizations are
the register listed by position out. included.
only.
Comments:

Organizational Position – The stakeholder’s position in their organization including their title should be
included in the Register.

Poor (1) Average (14) Good (16) Very Good (20) Rating =
Organizational The title of each The title of each The title of each
Positions are stakeholder is stakeholder is stakeholder plus a brief
not included listed. listed. A brief description of their
description of position in their
their position in organization is included.
their organization
is included for
some of the
stakeholders.
Comments:

Location – The location of the stakeholder relative to the Project should be included. This may include
the city, office and whether they are stationed on or off the Project.

Poor (1) Average (3) Good (4) Very Good (5) Rating =
Stakeholder Some but not all 75% of the The physical location of
location not stakeholder stakeholder each stakeholder is
included in the locations are locations are included plus an
register as an included. included in the indication of whether
item register. they are on or off
project.
Comments:

Role on the Project – In addition to their Organizational Position, it is important to understand the
Stakeholders role on the Project. Are they a decision maker, influencer, interested party? What is their
formal role?

Poor (1) Average (7) Good (8) Very Good (10) Rating =
Project Roles Some stakeholder At least 75% of The role of each
are not roles on the project the stakeholders stakeholder on the
included are listed. have roles listed. project is listed.
Comments:

Project Expectations – Based on the information you have gathered, you should summarize the
Stakeholder’s expectations for the Project. What do they expect from the outcome?

Poor (1) Average (7) Very Good (10) Rating =

Stakeholder Some but not all of Each stakeholder has a
expectations the stakeholders brief description of their
are not expectations are expectations for the
included listed. Project.
Comments:

Interests – As you build relationships with your Stakeholders, it will be important to understand their
personal interests. The Register should contain any information you are able to obtain.

Poor (1) Average (7) Good(8) Very Good (10) Rating =

Stakeholder The category is Some but not all Over 50% of the
interests are included, but is not of the stakeholders have their
not included populated with stakeholders’ interests listed.
as an item in information. interests are
the chart listed.
Comments:






Influence on Project Outcome – Many, if not all, of the Stakeholders will be able to influence the
outcome of the Project through their actions. These may include decision authority, staffing control,
etc.

Poor (1) Average (7) Good (8) Very Good (10) Rating =
The Register The top 3+ Over 75% of the Each stakeholder has
does not stakeholders have stakeholders have their ability to influence
include Project their ability to their ability to the Project outcome
Outcomes influence the influence the accurately described.
Project outcome Project outcome
listed. accurately listed.
Comments:

Type of Communication Recommended – Different Stakeholders require different levels of

communication. In this area you should record the level of communication required by the Stakeholder
(informed, consulted, approval authority) and the types of reports he or she should be provided. The
frequency of the communication should also be noted.

Poor (1) Average (7) Good (8) Very Good (10) Rating =
The type Most of the Each stakeholders Each stakeholder has the
communication stakeholders have has the type of type of communication
is not included the type of communication planned for them
as a category communication planned for them recorded. Several
planned listed. listed and some stakeholders have more
have the than one type listed. In
frequency listed. addition the frequency of
this communication is
listed.
Comments:

TOTAL =

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