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.)
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.
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