StakeholderAnalysisAssignment.pdf

06/21/2021

Stakeholder Analysis Assignment

This assignment uses two provided documents:

• Stakeholder_Analysis_Exercise.xls (spreadsheet)

• DMV Case Study

Purpose of this Assignment

This assignment gives you the opportunity to apply your understanding of the course

concepts to analyze how the enterprise architecture (EA) affects various elements of the

organization. This assignment specifically addresses the following course outcome:

• conduct stakeholder analysis to identify concerns and appropriate viewpoints

Background

One of the keys to successful enterprise architecture (EA) implementation is the support

offered by important stakeholders.

Stakeholders are those with an interest in a given project. There are varying degrees of

stakeholder involvement, which may be described as being in the following groups:

• Key Players—These are the most important stakeholders; they have a vested

interest in the approach, content, and output of the EA.

• Keep Satisfied—The next most significant group are those who must obtain what

they need from the EA and are less concerned with the construction and specific

content of the EA.

• Keep Informed—This group has a need to know what is being done and how it will

benefit the organization overall; they have little interest in any of the details of how

the EA is developed and used.

• Minimal Effort—This group has little interest in the EA and requires little attention

during the EA development effort.

The benefits of successfully managing stakeholders include the following:

• Obtaining support from the most influential stakeholders will help ensure that they

both help to shape the EA and to improve its content and products.

• Influential stakeholders are in a position to allocate human and financial resources to

the EA effort, making it more likely to succeed.

• Ongoing communication with stakeholders ensures their understanding of the

process and benefits of EA, and enables their support if needed.

• Successful management allows the EA team to draw on the support of stakeholders

with a positive view of the process if they need to address negative reactions or

setbacks in the organization.

(Concepts contained herein were derived in part from The Open Group Architecture

Framework (TOGAF), v. 9.)

06/21/2021

Assignment

Using the DMV Case Study and the Stakeholder Analysis Exercise spreadsheet provided, you

are to complete the columns of the spreadsheet for each of the ten stakeholder groups

listed on the spreadsheet.

Please refer to the reading link in your Course 5 content area called: TOGAF Standard:

Stakeholder Management. This link provides some excellent insights into the different roles

and influences of the stakeholders to assist in your assignment. Again, this is just a

reference for your benefit.

First, explain the interest or concern that the stakeholder has in the development of the EA.

Then, identify their “class” or role in the EA as one of the four shown above (Key Player,

Keep Satisfied, Keep Informed, or Minimal Effort). Finally, explain your reasoning for

selecting the class/role that you did.

Important: You are not being graded on whether you picked the “correct” stakeholder

involvement (i.e. key player, keep satisfied, keep informed or minimal effort). You might

see your Security Officer as a key player or as a stakeholder needing to be kept informed.

This is fine. What is important is that you provide a solid reason for why you chose this

classification as it relates to the interest/concern area. Please only pick one “class” or role

per stakeholder.

Complete the spreadsheet and submit it via your Assignments Folder by the due date shown

in the class schedule. Note: The filename of your submission should include your last name.

An example would be: Smith_Stakeholder_Analysis.xls.

Reference

The Open Group. (2018). TOGAF version 9.2: The Open Group architecture framework

(TOGAF). Retrieved from http://www.opengroup.org/togaf

The TOGAF Standard, Version 9.2: Part III: ADM Guidelines & Techniques; Stakeholder

Management. Retrieved from: http://pubs.opengroup.org/architecture/togaf9-

doc/arch/index.html

Grading Rubric

Your grade will be determined by the strength and validity of your analysis, rather than

what specific class/role you selected. Your work will be graded according to the grading

rubric below.

Criteria

90-100% Far Above Standards

80-89% Above Standards

70-79% Meets Standards

60-69% Below Standards

< 60% Well

Below Standards

Possible Points

Stake-

holder

Analysis

Interest/Concern and Class/Role of

the stakeholder

are correctly identified.

Interest/Concern and Class/Role of

the stakeholder

are correctly identified. Reason

Interest/Concern and Class/Role of

the stakeholder

are adequately identified. Reason

Interest/Concern and/or Class/Role

for the

stakeholder may be inadequately

No entries for this

stakeholder

or little

9 points for each

Stake-

holder

06/21/2021

Criteria

90-100%

Far Above Standards

80-89%

Above Standards

70-79%

Meets Standards

60-69%

Below Standards

< 60%

Well Below Standards

Possible Points

Reason for

Classification provides a full

explanation with

convincing justification; each

is clearly applicable to the

case study; demonstrates a

sophisticated

understanding of course concepts,

analysis, and/or critical thinking.

for Classification

provides a clear explanation with

justification; each

is applicable to the case study;

demonstrates an understanding of

course concepts, analysis, and/or

critical thinking.

for Classification

is adequately explained; each is

related to the

case study; demonstrates an

adequate understanding of

course concepts, analysis, and/or

critical thinking.

identified; and/or

Reason for Classification may

not be adequately

explained; and/or may not relate to

the case study; and/or

demonstrates an inadequate

understanding of

course concepts, analysis, and/or

critical thinking.

information

provided.

(see

below)

Head,

Dept. of Motor

Vehicles

9 Points 8 Points 7 Points 6 Points 0-5

Points

Chief

Financial Officer

9 Points 8 Points 7 Points 6 Points 0-5

Points

Program

Manage-ment

Office

9 Points 8 Points 7 Points 6 Points 0-5

Points

Line

Managers

for Service Delivery

Areas

9 Points 8 Points 7 Points 6 Points 0-5

Points

Creden-

tialing and

Tax Process-

ing Specialists

9 Points 8 Points 7 Points 6 Points 0-5

Points

Customer Service

Specialist

9 Points 8 Points 7 Points 6 Points 0-5 Points

Security Officer

9 Points 8 Points 7 Points 6 Points 0-5 Points

06/21/2021

Criteria

90-100%

Far Above Standards

80-89%

Above Standards

70-79%

Meets Standards

60-69%

Below Standards

< 60%

Well Below Standards

Possible Points

CIO 9 Points 8 Points 7 Points 6 Points 0-5

Points

Applica-

tion Software

Developer

9 Points 8 Points 7 Points 6 Points 0-5

Points

IT Opera-

tions

Manager

9 Points 8 Points 7 Points 6 Points 0-5

Points

Spread-

sheet

Format

9-10 Points

Spreadsheet

reflects effective

organization and sophisticated

writing; correct structure,

grammar, and spelling;

presented in a

professional format using

Excel.

8 Points

Spreadsheet

reflects effective

organization and clear writing;

correct structure, grammar, and

spelling; presented in a

professional

format using Excel.

7 Points

Spreadsheet is

organized; and/or

may contain some grammatical or

spelling errors; presented in Excel

format.

6 Points

Spreadsheet is

somewhat

organized, and/or contains

grammatical or spelling errors;

and/or does not use Excel

template.

0-5 Points

Spread-

sheet

content is extremely

poorly constructed

and does not convey

the

information.

TOTAL

Points

Possible

100