The document outlines the credentials and expertise of Syed Basharat Aziz in project management and IT over a 10-year span. It details PMI's roles, the significance of stakeholder management, and the processes for identifying and managing stakeholders, referencing the PMBOK guide. Additionally, it chronicles the historical development of PMI and its standards, alongside various management knowledge areas essential for project success.

1. Syed Basharat Aziz
Program Manager, Araamis and Director of IT, PMI-AGC-KSA
Tuesday, 02nd June 2015

2. 2
Experience: 10 years in Project Management and 17 years in
information technology.
Domain Expertise:
• Project Management
• IT Service Management
• ISO 20000
• Payment Card Industry
Roles: Consultant, Trainer, Volunteer and Entrepreneur.
Certifications: PCIP, ISO 20 K, ITIL Expert, PCI-ISA, ITIL-SM,
Six Sigma, CA-CUSE, ITILF, CA-DMC, RMTP, CA-CUSA,
CCNA, MCSE.

3. • What is PMI, PMBOK, Knowledge Areas and Processes?
• What is meant by Stakeholder?
• What are Common Roles of Stakeholders?
• Why to Identify Stakeholders?
• How to Identify Stakeholders?
• How to Manage Stakeholders?
• Key Documents
• Re Cap
PMI, PMBOK are registered trademark of PMI 3

4. • PMI official website www.pmi.org
• PMI is the world’s leading not-for-profit membership association for
the Project Management profession.
• PMI offers PMP (Project Management Professional) and other certifications.
• PMBOK Guide: Project Management Body of Knowledge
• PMBOK Guide is the principal reference for the PMP exam and an
Approved American National Standard (ANSI)
• Latest Edition of PMBOK is PMBOK 5th Edition
4PMI, PMP and PMBOK are registered trademark of PMI

5. • 1969 - Project Management Institute was founded.
• 1976 - Discussion on Standards
• 1981 - PMI board of Directors Approved the Proposal
• 1984 - Approval of the 2nd standards; launch of PMP certification
• 1985 - Workshop as part of PMI Annual Seminars
• 1986 - Three New Sections (Project Management Framework, Risk and Contract/Procurement
Management)
• 1987 - PMBOK was Approved and Published
• 1996 - A guide to the PMBOK (PMBOK Guide)
• 2000 - Second Edition.
• 2004 - Third Edition.
• 2008 - Fourth Edition with examination changes in 2011.
• 2012 - Fifth Edition published
5PMI, PMP and PMBOK are registered trademark of PMI

6. 1. Integration Management – To ensure integration of the all Project Management
processes and activities in meeting the project's objectives.
2. Scope Management – To ensure that the project contains all the work required to meet
the objectives, nothing more, nothing less.
3. Time Management – To ensure that the project is completed within the time
constraints.
4. Cost Management – To ensure that the project can be completed within the approved
budget.
5. Quality Management – To ensure that the project meets the quality requirements of the
stakeholders.
6PMBOK is a registered trademark of PMI

7. 6. Human Resource Management – To organize, develop and manage the project team
7. Communications Management - To ensure the management of project info, from
collection to disposition
8. Risk Management – To increase the Probability (P) & Impact (I) of opportunities and
decrease P and I of threats
9. Procurement Management – To ensure products or services of the required quality are
procured for integration with the final product
10. Stakeholder Management – To identify and manage stakeholders throughout the
life cycle of the project and increase the chance of project success.
7PMBOK is a registered trademark of PMI

8. 8
Control
Stakeholder
Engagement
Manage
Stakeholder
Engagement
Plan
Stakeholder
Management
Identify
Stakeholders

9. 9

10. Reference: PMBOK 05th Edition 10

11. • Sponsor.
• Project Manager / Project Team.
• Customer / User.
• Functional Managers.
• Organizational groups.
• Sellers.
• Business partners.
11

12. 12

13. 13Reference: http://ctb.ku.edu/en/table-of-contents/participation/encouraging-involvement/identify-stakeholders/main

14. 14

15. 15Reference: http://ctb.ku.edu/en/table-of-contents/participation/encouraging-involvement/identify-stakeholders/main

16. 16
It is a process of systematically gathering and analyzing quantitative and qualitative
information to determine whose interests should be taken into account throughout the
project.
1. Information Collection - Roles – Departments – interests – knowledge levels –
Expectations – influence levels – secondary stakeholders from interviewing major
Stakeholders.
2. Classification for Strategy - Analyze the potential impact or support each stakeholder
could Generate, and classify them so as to define an approach strategy
3. Assessment for Influence - Assess how key stakeholders are likely to react or respond in
various situations in order to plan how to influence them to enhance their support and
mitigate potential negative impacts.

17. 17

18. 18

19. 19
It is used to know the current engagement level of stakeholders as compared to
the planned engagement.
Unaware Resistant Neutral Supportive Leading
Engagement levels can be:

20. 20Reference: PMBOK 05th Edition
C is for Current Engagement and D is for Desired Engagement
Stakeholder Unaware Resistant Neutral Supportive Leading
Stakeholder 1 C D
Stakeholder 2 C D
Stakeholder 3 C D

21. 21

22. • What is PMI, PMBOK and Knowledge Areas?
• What is meant by Stakeholder?
• What are Common Roles of Stakeholders?
• Why to Identify Stakeholders?
• How to Identify Stakeholders?
• How to Manage Stakeholders?
• Key Documents.
• Food for Thought. (Change Management)
22

23. 23