The continuous progress in the profession always driving changes and updates necessary to improve the practice among all the cultures. The Project Management Body of Knowledge (PMBOK® Guide) is a collection of processes and knowledge areas accepted as a best practice for the project management profession and it has to remain relevant to most projects, most of the time, for most of practitioners. (PMBOK® Guide) is being updated this year. This session shall provide insights into the new Sixth Edition, including a brief look at the new chapter on role of the project managers.
For each Knowledge Area, there are new sections too, describing key concepts, emerging trends, and different considerations.
Besides that, by attending this session you will be able to explore what are new, the main changes and understand how the new (PMBOK® Guide) will better fasten with the PMI Talent TriangularTM.
Imagine - HR; are handling the 'bad banter' - Stella Chandler.pdf
Insights into the Project Management Body of Knowledge (PMBOK® Guide) - Sixth Edition
1. KUWAIT
PROJECT MANAGEMENT CONFERENCE
25-26 April 2017 - Kuwait
Insights into
Project Management Body of Knowledge
(PMBOK® Guide) - Sixth Edition
TAREQ A. AL BEHEIRI, PMP,PMI-ACP
#kuwaitpmc
2017
1
13. 13
A. The Guide
A guide to project management body of
knowledge
A.1
Front- End
A.2
Knowledge
Area
Chapter (1-3) Chapter (4-13)
Not ANSI Standard ANSI Standard
14. 14
B. The Standard
A standard for project management
Section (i)Section (ii)
According to
the American National Standards Institute (ANSI)
ANNEX 1
17. 17
What is the standard?
According to ISO
A document approved by a
recognized body that provide for
common and repeated use
rules,guidelines,or characteristics
for products,processes,or services
with which compliance are not
mandatory ISO 9453
18. 18
Standard means…
A set of principles and rules considered by
an authority or general consent
as a basis of comparison and
judgment in approved model
19. The Standard Components
Section (i)
Introduces
The Role of Project
Management
Includes
Abbreviated
Key Concepts
Describes
Project Management
Process Groups
(IPECC)
Describes processes, grouped
into Process Groups
Key Benefit
Inputs
Outputs
Section (ii)
19
20. 20
Standardization
of the PMI
In 1998,PMI was accredited as a
standards developers by ANSI?
This process was outlined in the
ANNEX Part
and described in
the PMBOK Guide 5th edition part
22. 22
What is the standard
for
PROJECT MANAGEMENT?
ANSI requires an update at least every Fiveyears
23. 23
Requirements for COMPLIANCE
ANSI Formal Review Process
requires
BMBOK Guide
Exposure Draft
All comments reviewed formally
Decisions can be appealed and adjudicated
Member Advisory Group Review (MAG (
Consensus body vote
27. Front – End
(Chapter (1-3
Chapter 1
Chapter 2
Chapter 3
Introduction
Organizational Influence And Project Life Cycle
Project Management Processes
Cover key principles and broad concepts
Not an ANSI Standard
Formal Exposure Draft processNot REQUIRED
Reviewed along with Knowledge Area
chapters 4-1327
28. What’s new for the Front – End
(Chapter (1-3
Restructure
3=2
+1
Chapter 3 :The Role
of28
29. In the presence of a comprehensive knowledge
Area about the STAKEHOLDERS, Do you see good
importance to specially add a new chapter on the
PROJECT MANAGER role at the PMBOK® Guide
30. In your perspective, What is the most important
role(s) required from the Project Manager
orchestra
31. The New chapter Focus
Will discuss the PMI Talent Triangle™
and the skill sets organizations
demand that make project managers
more competitive and relevant
32. Link the New chapter with the
PMI Talent Triangle™
33. knowledge Areas
(Chapter (4-13
Chapter 4
Chapter 5
Chapter 6
Integration
Scope
Time
Chapter 7 Cost
Chapter 8 Quality
Chapter 9 Human Resources
Chapter 10 Communication
Chapter 11 Risk
Chapter 12 Procurement
Chapter 13 Stakeholders
Cover project management knowledge areas
Introductory
section / each
Processes with
inputs, tools & techniques, outputs
An ANSI Standard
Formal Exposure Draft process
1 2
33
34. Introductory Section
1
Common structure for
each knowledge area
Definition
Key Benefits
List of Processes
Overview Diagram
Data Flow Diagram
Key Concepts
Number of processes
with
inputs, tools &
techniques, outputs
2
34
35. What’s new for knowledge Areas
Chapter (4-13) Introductory Section
Improve
Trends and Emerging Practices
Approach for Iterative, Adaptive and
Agile environment
Tailoring Considerations
Consistency across knowledge areas
35
36. What’s new for knowledge Areas
Chapter (4-13) Processes with ITTO Section
ITTO Bundling
Inputs outputsT&T
36
37. What’s new for knowledge Areas
Chapter (4-13) Processes with ITTO Section
Grouping (T&T)
under Heading of AFFINITIES
DataGathering
DG
DataAnalysis
DA DecisionMakingDM
Interpersonal
andteamskills
ITS
Communication
skills
CS
Communication
COM
1 2 3 4 5 637
44. Rename Processes
• SIX processes have different names.
• In order to :
Be aligned the process name with the intent of it
To align with RESEARCH showing that project
management is more about FACILITATING and
MANAGING than CONTROLLING,
THREE of them have shifted from a Control
function to a Monitor function.
57. 57
The function of the
Close Procurement process
Control Procurements Close Project or Phase
- Research shows that few project managers have the
authority to formally and legally close a contract.
- Project managers are responsible to determine that
work is complete, records indexed and archived, and
responsibilities transferred appropriately.
- Project managers have no included work associated
with Close Procurements within the aforementioned
processes.
61. The main change in the Standard
Simplification of IO table
- Not Listed Individually
1. Project management plan
2. Project documents
……….
1. Project management plan
update
2. Project documents
updates ……….
Individual project management plan components and project
documents are listed beneath table:
Schedule management plan, Scope baseline, Cost estimates, Risk register
Inputs outputs
61
64. Why use simplified IO structure?
David Hillson
6th Ed.Core committee
Vice Chair
1. Provides a stable foundation
for future updates
Project management plan and Project documents
will always be inputs and outputs in IO table,
although specific components and documents may change
in future updates
64
65. Why use simplified IO structure?
David Hillson
6th Ed.Core committee
Vice Chair
2.Non-prescriptive, emphasizing
need for tailoring
- Specific Project management plan components and
Project documents are likely to be different for different
projects
- PM is responsible for identifying what is needed for
their project65
71. (Sept)2017
6.Final version will be
released
7.Printed version will
become available
Beginof2018
1.Development work
completed
December2015
2.Exposure Draft period
June-July2016
3.All comments reviewed
(July)2016
4. Integration, QC and final edit
(Aug)2016
5. CEO approval
(Sept)2016new PMP® Exam update to be based on PMBOK® Guide 6th edition
is in the first quarter of 2018
2017
2017
2017
2017
72. My Biography
in 4 snapshots
Instructor Construction manager
volunteer Civil engineer
72
73. • Name | (TAREQ A. AL BEHEIRI)
• Email | (tareq742@yahoo.com)
• Mobil | + 965 97818174
73