Presentation is loading. Please wait.

Presentation is loading. Please wait.

Critical Changes to PMBOK6

Similar presentations


Presentation on theme: "Critical Changes to PMBOK6"— Presentation transcript:

1 Critical Changes to PMBOK6
PMI-Midlands Annual Meeting December 5th, 2017

2 Good Evening! We are partners in the task of:
Understanding Critical Changes to the PM Body of Knowledge 6 So we can incorporate what makes sense for how we get work done

3 We Will Be Using Poll Everywhere Tonight
Poll Everywhere Information

4 E. Integrating Concepts Table Talk 5 F. Summary
Agenda The Big 3 Survey / Table Talk 1 Agile Survey / Table Talk 2 Processes Survey / Table Talk 3 D. PM Role Survey / Table Talk 4 E. Integrating Concepts Table Talk 5 F. Summary

5 Agile/Adaptive Concepts Renamed 6 Processes Added 3 Processes
Big 3 Changes to PMBOK 6 Agile/Adaptive Concepts Renamed 6 Processes Added 3 Processes Deleted 1 Process Net +2 = 49 Processes PM Role Agile Process Changes PM Role - Expanded

6 Biggest Changes to PMBOK 6
Addition of Agile framework concepts to 10 Knowledge Areas Changing Project Human Resource Management to Project Resource Management Changing Control to Monitor in Communications, Risks and Stakeholder Engagement Addition of “Implement Risk Responses” Process Addition of “Manage Project Knowledge” Process Addition of “Control Resources” Process Removal of “Close Procurement” Process

7

8 Survey 1: What do you think are the most important changes?
Monitor vs. Control Language Addition of Manage Project Knowledge Elements of Agile Methodology Addition of Control Resources Addition of Implement Risk Responses Change from Human Resources to Resources PM Role Elaboration Expansion

9 Table Talk 1 Using your choice from the survey – discuss why X was the most important change to you Now share how you think this change could impact how you or your team delivers value

10 Inclusion of Agile Methodologies in Each Knowledge Area

11 Agile “Fit” for Different Organizational Settings
Sponsor support for Agile? Stakeholders trust the team? Team able to make local decisions? Team Size? Team Experience? Daily Access to Customer? % of Requirements Changing Monthly? Product Critical – Impact of Fail? Can product/service be built in portions? Buy-in 10 9 8 7 6 5 4 3 2 1 1 is the highest Score 10 lowest Trust Access Decision Making Pred- ictive Agile Hybrid Experience Delivery Team Size Criticality PMI Agile Practice Guide p. 134 Changes

12 Agile Concepts Applied to Knowledge Areas
Communications Project visibility, frequent team checkpoints, collocated teams Cost Management Lightweight estimation and modification of scope or schedule Integration Mgmt. Team controls the detailed product planning and delivery Procurement Mgmt. Add adaptive work sections to appendices of larger contract Resource Mgmt. Collaborative, self-organizing, cross-functional teams Risk Management Frequent product reviews and re-prioritization of tasks for risk mgmt. Quality Management Sprint Retrospectives regularly check quality and identify root causes Schedule Mgmt. Pull-based scheduling and short work cycles Scope Mgmt. Less time defining scope at start – iteratively refine requirements Stakeholder Mgmt. Client, User and developer exchange info. in dynamic co-creative process

13 Survey 2 - Which Agile Element is Most Important?
1 Communications Project visibility, frequent team checkpoints, collocated teams 2 Cost Management Lightweight estimation and modification of scope or schedule 3 Integration Mgmt. Team controls the detailed product planning and delivery 4 Procurement Mgmt. Add adaptive work sections to appendices of larger contract 5 Resource Mgmt. Collaborative, self-organizing, cross-functional teams 6 Risk Management Frequent product reviews and re-prioritization of tasks for risk mgmt. 7 Quality Management Sprint Retrospectives regularly check quality and identify root causes 8 Schedule Mgmt. Pull-based scheduling and short work cycles 9 Scope Mgmt. Less time defining scope at start – iteratively refine requirements 10 Stakeholder Mgmt. Client, User and developer exchange info. in dynamic co-creative process

14 Table Talk 2 Using your choice from the survey – discuss why X was the most important Agile element to you Now share how you think this change could impact how you or your team delivers value

15 VS VS Process Changes Communications Risks Stakeholders Monitor
Control Knowledge Management Risk Response Control Resources Communications Risks Stakeholders VS Resources Human Resources

16 Survey 3: What do you think is the most important change is to processes?
Addition of Manage Project Knowledge Addition of Control Resources Addition of Implement Risk Responses Deletion of Close Procurements Change from Monitor to Control on Communications, Risks and Stakeholder Engagement

17 Table Talk 3 Using your choice from the survey – discuss why X was the most important process change to you Now share how you think this change could impact how you or your team delivers value

18 Role of the Project Manager
PM Stakeholders, Suppliers, End Users, Customers Sponsors, PMO, Governing Bodies Leadership Management PM Competencies Project Team Product Mgrs. Processes Project Integration People Knowledge PM Sphere of Influence Align w/Strategic Objectives Integrate to Focus on Essentials

19 Survey 4: What do you think is the most important change is to the PM Role Description?
Talent Triangle Elaboration on Leadership and Management Project Integrator Role Project Manager Influence

20 Table Talk 4 Using your choice from the survey – discuss why X was the most important PM Role Section change to you Now share how you think this change could impact how you or your team delivers value

21 Work as a team to summarize the changes to the PMBOK in 2-3 sentences
Table Talk 5 Work as a team to summarize the changes to the PMBOK in 2-3 sentences

22 Putting It All Together
In today’s less predictable business environment, PMs must implement Agile methodologies and use their influence to help collaborative teams focus on essential, valuable deliverables. This leadership must be based less on direct control and more on monitoring and making project knowledge available

23 You can find me at sdavisb@gmail.com
Questions or Comments? You can find me at


Download ppt "Critical Changes to PMBOK6"

Similar presentations


Ads by Google