Assignment #1 Name: Hammad Sharif Roll No: 02-398192-047

MONITOR STAKEHOLDER ENGAGEMENT: INPUTS 

1. Project Management Plan
1. Resource management plan
2. Communications management plan
3. Stakeholder engagement plan
2. Project documents
1. Issue log
2. Lessons learned register
3. Project communications
4. Risk register
5. Stakeholder register
3. Work performance data
4. Enterprise environmental factors
5. Organizational process assets

MONITOR STAKEHOLDER ENGAGEMENT: Tools and Techniques 

1. Data analysis
1. Alternatives analysis
2. Root cause analysis
3. Stakeholder analysis
2. Decision making
1. Multicriteria decision analysis
2. Voting
3. Data representation
1. Stakeholder engagement assessment matrix
4. Communication skills
1. Feedback
2. Presentations
5. Impersonal and team skills
1. Active listening
2. Cultural awareness
3. Leadership
4. Networking
5. Political awareness
6. Meetings

MONITOR STAKEHOLDER ENGAGEMENT: Outputs 

1. Work performance information
2. Change requests
3. Project management plan updates
1. Resource management plan
2. Communications management plan
3. Stakeholder engagement plan
4. Project documents updates
1. Issue log
2. Lessons learned register
3. Risk register
4. Stakeholder register
Assignment #1 Name: Hammad Sharif Roll No: 02-398192-047

INTERPERSONAL AND TEAM SKILLS 

Interpersonal skills to that can be used for this process include:
• Active listening: Active listening is used to reduce misunderstandings and other miscommunication.
• Cultural awareness: Cultural awareness and cultural sensitivity help the project manager to plan
communications based on the cultural differences and requirements of stakeholder sand team members.
• Leadership: Successful stakeholder engagement requires strong leadership skills to communicate the vision and
inspire stakeholders to support the work and outcomes of the project.
• Networking: Networking ensures access to information about levels of engagement of stakeholders.
• Political awareness: Political awareness is used to understand the strategies of the organization, understand
who wields power and influence in this arena, and to develop an ability to communicate with these
stakeholders.

Control Scope Process

Control Scope is the process of monitoring the status of the project and product scope and managing changes to the
scope baseline. The key benefit of this process is that it allows the scope baseline to be maintained throughout the
project. The inputs, tools and techniques, and outputs of this process are depicted in Figure 5-16. Figure 5-17 depicts the
data flow diagram of the process.

Control Scope Process : Inputs

1. Project management plan
2. Work performance information.
3. Requirements documentation
4. Requirements traceability matrix
5. Organizational process assets

Control Scope Process : Tools and Techniques

1. Variance analysis
2. Trend Analysis

Control Scope Process : Outputs

1. Work performance measurements
2. Organizational process assets updates
3. Change requests
4. Project management plan updates
5. Project document updates
Assignment #1 Name: Hammad Sharif Roll No: 02-398192-047
Data Analysis
 Variance Analysis is comparing the change to the baseline and understand how big the change is and what the
variation is.
 Trend Analysis tells you how the project is performing over the period. It tells you whether the project
performance is increasing or decreasing over the period.

Steps to Control Scope Process Using Data Analysis

1. Change Occurrence in the project – one or more of the stakeholder(s) request the change in the
project.
2. Create Change Request – The first thing that you are going to do is to document the change by creating
a change request
3. Assess the impact of the change to Project constraints such as scope, time, cost, quality, risk,
resources.
4. Process the change through integrated change control process, which we learnt in project integration
management knowledge area.
5. If the change does not approve, then close the change request.
6. If the change gets approval, then perform Variance Analysis to understand how big the change is. And
how much variance the project has compare to its baseline.
7. Update all the necessary project documents such as project management plan, scope baseline, other
project documents and re-baseline them.