Agile, PMBOK Guide Sixth Edition and Your Future

Transcription

1 GR8PM Traditional Agile Hybrid Training Coaching Consulting Agile, PMBOK Guide Sixth Edition and Your Future How should PMP s interpret and respond to such huge changes?! The PMI Registered Education Provider logo is a registered mark of the Project Institute, Inc. Copyright, GR8PM, 2016, all rights reserved.

2 KEY QUESTION What makes the PMBOK Guide Sixth Edition coming out in January so important?

3 Quick History of the PMBOK Guide Important highlights in the growth of the project management profession. 1969: PMI is founded. 1976: Serious discussion of project management standards reaches critical mass in Montreal. 1981: PMI Board approves a project to create a standard focused on Professional Practices (Ethics) Body of Knowledge Structure (Standards) Professional Recognition (Accreditation)

4 Quick History of the PMBOK Guide Important highlights in the growth of the project management profession. 1984: ESA Baseline Report moves the PMI Board to approve a project to elaborate the proposed 6 knowledge areas. Six committees developed content and a 1985 workshop was convened to review the work The result included a: Project Framework Risk knowledge area Contract/Procurement knowledge area 1987: The Project Body of Knowledge is published.

5 Quick History of the PMBOK Guide Important highlights in the growth of the project management profession. 1991: Project to update the standard begins Exposure draft distributed to all 10,000 PMI members 1996: A Guide to the Project Body of Knowledge (PMBOK Guide) is published. Name was changed Framework completely rewritten Ninth knowledge area Project Integration was added

6 Quick History of the PMBOK Guide Important highlights in the growth of the project management profession. 2004: PMBOK Guide, Third Edition is published 2008: PMBOK Guide, Fourth Edition is published 2013: PMBOK Guide, Fifth Edition is published

7 Quick History of the PMBOK Guide Important highlights in the growth of the project management profession.

8 Quick History of the PMBOK Guide Important highlights in the growth of the project management profession. 2017: PMBOK Guide, Sixth Edition Framework will be completely revised Agile will be added to every knowledge area Unprecedented! Not since the original 1996 PMBOK Guide was published 20 years ago has this magnitude of change happened.

9 Quick History of the PMBOK Guide Important highlights in the growth of the project management profession. Also worth noting: 5 Process Groups Present in all Editions st edition = 199 pages & 8 Knowledge Areas nd edition = 216 pages & 9 Knowledge Areas rd edition = 402 pages & 9 Knowledge Areas th edition = 507 pages & 9 Knowledge Areas th edition = 616 pages & 10 Knowledge Areas

10 Quick History of the PMBOK Guide Important highlights in the growth of the project management profession. PMI-ACP surpassed 10,000 certification holders in November 2015 PMI-ACP is bigger than PgMP + PfMP + PMI-SP + PMI-RMP + PMI-BA! PMI-ACP = 12,000+

11 Quick Comparison of Agile and Traditional We Value Individuals and Interactions Working Software Customer Collaboration Responding to Change over over over over Processes and Tools Comprehensive Documentation Contract Negotiation Following a Plan We Would Add not a

12 Quick Comparison of Agile and Traditional Traditional: Graphical WBS Objective Agile / Scrum: Feature Structure Product Phase 1 Phase 2 Theme 1 Theme 2 Work Package 1 Work Package 2 Work Package 1 Work Package 2 Epic 1 Epic 2 Epic 3 Epic 4 Activity 1 Activity 2 Activity 3 Story 1 Story 2 Story 3 Task 1 Task 2 Task 3 Task 1 Task 2 Task 3

13 Quick Comparison of Agile and Traditional Definitions are completely arbitrary logical devices. PMBOK: 1. Objective 2. Phase.. 3. Work Pkg.. 4. Activity 5. Task AGILE: 1. Product 2. Theme.. 3. Epic. 4. Story 5. Task DEFINITION: 1. Business-level Full Function Vision 2. What a User Class wants to see or experience (Sub-function; End-toend workflow) 3. What a User will do and the result(s) they will see 4. Workflow component in User words 5. Technical job plus acceptance criteria

14 Quick Comparison of Agile and Traditional Taxonomy for Traditional vs. Agile Roles Traditional: Stakeholders & Sponsor Program or Sr. Project Manager Jr. PM or Team Lead Team and SME s Everybody else Agile / Scrum: Stakeholders & Sponsor Product Owner Scrum Master Team and SME s Everybody else

15 Do most PMP s have 1,500 hours of Agile? PROGRESSIVE ELABORATION

16 Do most PMP s have 1,500 hours of Agile? The PMBOK Guide, Fifth Edition states: 1.3 What is Project? development of the project management plan is an iterative activity and is progressively elaborated throughout the project's life cycle. Progressive elaboration involves continuously improving and detailing a plan Predictive Life Cycles Even projects with predictive life cycles may use the concept of rolling wave planning... for appropriate time windows, as new work activities are approaching

17 Do most PMP s have 1,500 hours of Agile? The PMBOK Guide, Fifth Edition states: 3.4 Planning Process Group The complex nature of project management may require the use of repeated feedback loops... This progressive detailing is called progressive elaboration, indicating iterative and ongoing activities. (paraphrased) Decomposition Decomposition is a technique used for dividing and subdividing project deliverables into smaller, more manageable parts. Activities represent the effort needed to complete a work package.

18 Knowledge Areas Project Integration Project Integration Project Scope Project Time Project Cost Project Quality Project Process Groups Initiating Planning Executing M & C Closing Develop Project Charter Develop Project Charter Develop Project Plan Collect Requirements Define Scope Create WBS Define Activities Sequence Activities Estimate Activity Resources Estimate Activity Duration Develop Schedule Plan Quality Direct and Manage Project Execution Develop Project Plan Estimate Cost the overall Determine project Budget good. Perform Quality Assurance Monitor and Control Project Work Perform Integrated Change Control Direct and Manage Project Execution Verify Scope Control Scope Fact Integration Control Schedule Control Costs Perform Quality Control Close Project or Phase Monitor and Control Project Work Perform Integrated Change Control Close Project or Phase Integration, in the context of managing a project, is making choices about where to concentrate resources and effort on any given day, anticipating potential issues, dealing with these issues before they become critical, and coordinating work for PMBOK Guide, Third Edition Integration management is a juggling act of trade-offs and coordination as part of balancing project execution and stakeholders expectations.

19 Knowledge Areas Project Integration Project Scope Project Scope Project Time Project Cost Project Process Groups Initiating Planning Executing M & C Closing Develop Project Charter Develop Project Plan Collect Requirements Define Scope Create WBS Define Activities Sequence Activities Estimate Activity Resources Estimate Activity Duration Develop Schedule Collect Requirements Define Scope Create WBS Direct and Manage Project Execution Fact Scope Monitor and Control Project Work Perform Integrated Change Control Verify Scope Control Scope Control Schedule Verify Scope Control Scope Close Project or Phase Project Scope includes the processes required to ensure that the project includes all the work required, and only the work required, to complete the project Estimate successfully. Cost Control Costs Determine Budget PMBOK Guide, Third Edition Project Quality Plan Quality Perform Quality Assurance Perform Quality Control Agile calls this concept Barely Sufficient meaning it is fully sufficient but not overly so (gold plating) and not insufficient (breach of contract).

20 Knowledge Areas Project Integration Project Time Project Scope Project Time Project Process Groups Initiating Planning Executing M & C Closing Develop Project Charter Develop Project Plan Collect Requirements Define Scope Create WBS Define Activities Sequence Activities Estimate Activity Resources Estimate Activity Duration Develop Schedule Define Activities Sequence Activities Estimate Activity Direct and Manage Project Execution Fact Time Monitor and Control Project Work Perform Integrated Change Control Verify Scope Control Scope Control Schedule Control Schedule Close Project or Phase Time management includes the processes required to accomplish timely completion of the project. PMBOK Guide, Third Edition Project Cost Project Quality Estimate Cost Determine Budget Control Costs Using high-precision low-accuracy information to plan or predict dates sets a project up for failure. Agile manages Plan Quality Perform Quality Perform Quality Assurance Control time by calculating schedules instead of predicting them.

21 Agile and the PMBOK Guide Sixth Edition How should PMP s respond?! GR8PM, Inc. Training Coaching Consulting Traditional Agile Hybrid Connect with John via at: jstenbeck@gr8pm.com and on Linked In too! Ask for free Whitepapers on: Goal Setting Situational Leadership Delegation Guidelines