Did you know Cybrary has FREE video training? Join more than 2,500,000 IT and cyber security professionals, students, career changers, and more, growing their careers on Cybrary.
This lesson focuses on management and controlling stakeholder engagement. This is the process focuses on communicating with the stakeholders, meeting their expectations, and addressing problems in a timely manner. This encourages stakeholder commitment, which is very important to a project's ultimate success. Controlling stakeholders focuses on stakeholder relationships and modifying strategies and plans as needed. The instructor also offers a brief summary of the module and points to remember for the exam. [toggle_content title="Transcript"] Next process on our executing is management stakeholder engagement. Management stakeholder is a process focused on communicating with the stakeholders – meeting their expectations and addressing problems in a timely manner. It also helps with encouraging stakeholders' commitment. This process creates issue logs, change request and the project management planning updates. The inputs are the stakeholder management plan, communication management plan and changes log. The tools that are used are communication methods, personal skills and management skills. This is under executing so issue logs could be problems that are occurring. This is trying to track problems within the project and trying to communicate them up to the stakeholder. Change requests are requests to the plan so maybe some stakeholders don't want to be engaged… as much as they were in the past or some want more information or they want weekly reports, monthly reports. It's basically just changing how your plan is done. You are going to consider the project management plan updates from other areas. The inputs are rapport to other areas within the project management plan. The inputs are, stakeholder management plan. You want to know how you are engaging stakeholders. That's there, communication management plan. The history of stakeholder knowledge area used to be considered the communication knowledge area. You got notice some similarities between communication knowledge area and stakeholder knowledge area. The communication management plan is trying to tell you how to communicate to stakeholders. The changes log is if you have to change how you are communicating to those stakeholders after the plan has been created. Tools they use; communication methods. Communication methods can be push, pull or interactive if you remember from the communication knowledge area. Push is sending one way information out. An example can be a mass email without getting any responses to it. Pulling information and receiving information from others. You send a survey out and all the information that's coming back is one direction to you. Interpersonal interactive is a two way conversation. Interpersonal skills, this could establishment of trust, conflict resolution. It could be resisting change or active listening. Management skills can be facilitation, negotiation, influence and the ability to modify behavior. The next knowledge area is control stakeholder engagement. Control stake holder engagement focusses on stakeholder relationships and modifying strategies and plans as appropriate. This process creates work performance information, change request and project document updates. The inputs are the project management plan, issue logs, work performance data and project documents. The tools used are information management systems, expert judgment and meetings. We haven't seen this one in a while, information management systems. This is how your team will communicate. It could be through a Microsoft project, it could be an ERP system. It could also be something like SharePoint, where you are sharing information amongst project members. In summary of stakeholder knowledge area… The stakeholder knowledge area was created because PMI felt that stakeholders needed to be engaged. They are the reason why the project exists. If you notice, identified stakeholders at the very beginning of the project and it goes all the way up until, almost closing. You have four knowledge areas. For stakeholder knowledge area know your inputs and outputs and know your tools just like every other knowledge area. You should be fine for the test. [/toggle_content]