Computer Science Homework Help

Stakeholder support is very important to information technology projects. Stakeholders can be external and internal. External stakeholders could be members of the society who benefit from the technology. Internal stakeholders could be the executive management team responsible for funding the project.

If your project were to be implemented and deployed in a real-world environment, identify the key stakeholders whose support you would need. In your initial post, identify these stakeholders and describe the strategies you would take to get stakeholder buy-in. Also, describe how you could approach stakeholders that might resist the project.

Then, compare and contrast your ideas with your classmates.

Peer Review 1

Brandon Cota posted

Project stakeholders are those that have some benefit or personal gain associated with the project’s success or failure, a stake that they hold… (Kissflow, 2021). My project has a few main groups that would be directly affected by my project’s outcome. The main groups would be management, development teams, consumers (I.e., drivers) and the general public. To quickly recap, my project is going to take data from on-board diagnostics data on a vehicle and send it, along with real-time GPS coordinates, into a database. The data will be parsed and sent into autonomous cars (I.e., Tesla’s) and that data will be used to aid in automation logic while those vehicles are navigating cars around it. The obvious groups of stakeholders would be those who drive Tesla’s and would like the process to improve, people who drive vehicles around Tesla’s and appreciate increased safety on the road, and those who don’t want to share their information with anyone or anything, especially car driving robots. The first two main groups of stakeholders wouldn’t need much mitigation because they want to see the success of the project, the 3rd group would need assurances of how the information would be utilized and the tools and means used to gather it from vehicles and drivers. The information will be passed in using a tool hooked into the OBD-II, the on-board diagnostic computer in all vehicles made after a certain date. The information gathered can then be passed, via Bluetooth, in the driver’s mobile device and linked using API routes into the database. No driver information will be linked to the information coming into the database, only vehicle information (I.e., car type, speed, throttle pressure, brake pressure, etc.). The other two groups will want to see results from the system that are positive and increase the response time of automated vehicles as well as allow it to navigate roads more effectively.

Peer Review # 2

Christopher Matt posted

Good evening, class. Thinking about my project, there are many possible stakeholders that could be important. All scenarios I can think of would assume that I am working for a company. The size could vary. This could be a larger company looking to add a technology and related products. The nature of my project would more likely be found in a smaller startup-type of company who is launching this product. Even a third possibility, I suppose, is that I am brought on to some capacity to work with a car company, for example, to integrate the technology. Regardless, I would have sponsors for the project. This could be a VP or higher-level executive, or management group, internally. In addition, there could be other external supporters. In a smaller organization, there may be outside funding organizations, like venture capitalists.

The best strategies aimed at getting any stakeholders onboard would be solid business plans that clearly outline various perspectives and forecasts related to the product. In a larger corporate structure, this could be more complicated. There could be heads of multiple departments, all of which have different stakes in the product. Some factors that stakeholders would want to become familiar with are:

• Is the technology valuable?
• Is the technology sustainable?
• Can the product be produced in a way that it is of adequate functionality and durability, while still being functional and affordable?

Other considerations would include financial projections that outline the ongoing investment vs the likely payoff, or “Return on Investment” In addition, risk and security analysis would be key. Finally, Legal requirements must be addressed to the stakeholders’ satisfaction.

The question of resistance to the project is interesting. I suspect that resistance increases, in most cases, for projects introducing new technology. There are numerous examples of this effect. Again, the best way to deal with those challenges is to produce a good argument. In closing, it is worthwhile to point out that stakeholders may not have the intimate relationship with the product that the developers do. In this sense, they can often offer a more realistic approach to the project. If developers are receptive to the business realities attached to the product, the chance of success is greater.