A Guide to the Project Management Body of Knowledge …

1 A Guide to the Project Management body of Knowledge (PMBOK Guide ) Sixth Edition Errata - (Fourth Printing) NOTE: The following errata is a cumulative list of the notable corrections that have been made since the first printing of the PMBOK Guide Sixth Edition. In order to verify the print run of your book (or PDF), refer to the bottom of the copyright page (which precedes the Notice page and Table of Contents). The last numeral in the string beginning "10 9 8" etc. denotes the printing of that particular copy. Part 1 A Guide to the Project Management body of Knowledge (PMBOK Guide ) Page Correction 75, 76 Figs 4-2 and 4-3. Removed bullet for benefits Management plan as input for business documents. 89 Table 4-1. Under Project Management Plan, added 19.

2 Management reviews. 98, 99 Figs 4-8, 4-9. Removed bullet for source selection criteria as input for Project documents. 105 Fig 4-10. Added bullet for voting as tool & technique for decision making. 114 Fig 4-13. Added following process box: Define Activities with the input change requests. 122 Fig 4-15. Changed input Project Documents to Business Documents. 138 Fig 5-4. Added bullet for autocratic decision making as tool & technique for decision making. 151 Section , 2nd paragraph, 1st sentence. Changed The preparation of a detailed Project scope statement builds upon the major deliverables, assumptions, and constraints that are documented during Project initiation. to: The preparation of a detailed Project scope statement builds upon the high-level Project description that is documented during Project initiation.

3 154 Section , 1st sentence. Changed The Project scope statement is the description of the Project scope, major deliverables, assumptions, and constraints. to The Project scope statement is the description of the Project scope, major deliverables, and exclusions. 161 Section , 1st bullet ( Project scope statement). Changed The Project scope statement includes the description of the Project scope, major deliverables, assumptions and constraints. to: The Project scope statement includes the description of the Project scope, major deliverables, and exclusions. 164 Fig 5-16. Revised input for process box to read Direct and Manage Project Work (was Direct and Manage Project Execution). 179 Fig 6-3. Added bullet for alternatives analysis as tool & technique for data analysis.

4 180. Section Moved the following bullet to Section : Guidelines and criteria for tailoring the organizaton s set of standard processes and procedures to satisfy the specific needs of the Project . 183 Fig 6-6. Changed bullet under the inputs for Project Management plan from scope Management plan to schedule Management plan. 184 Section , 2nd bullet (Scope baseline ), 2nd sentence. Changed The Project WBS, deliverables, constraints, and assumptions documented in the scope baseline are considered explicitly while defining activities. to The Project WBS, deliverables, and acceptance criteria documented in the scope baseline are considered explicitly while defining activities. 188 Section , 2nd bullet (Scope baseline ), 2nd sentence.

5 Changed The Project WBS, deliverables, constraints, and assumptions documented in the scope baseline are considered explicitly while sequencing activities. to The Project WBS, deliverables, and acceptance criteria documented in the scope baseline are considered explicitly while sequencing activities. 192 Fig 6-10. Changed labels to read FS with 2 Weeks (Lead) and SS with 15 Days (Lag). {By removing the dash, this eliminates possible confusion as to whether the figure is representing a positive or negative value for leads or lags.} 195 Fig 6-12. Added bullet for voting as tool & technique for decision making. 224 Section , 3rd bullet (Scope baseline ), 2nd sentence. Changed The Project WBS, deliverables, constraints, and assumptions documented in the scope baseline are considered explicitly while monitoring and controlling the schedule baseline .

6 To The Project WBS, deliverables, and acceptance criteria documented in the scope baseline are considered explicitly while monitoring and controlling the schedule baseline . 235 Fig 7-2. Added bullet for alternatives analysis as tool & technique for data analysis. 242 Section , 1st sub-bullet ( Project scope statement). Changed The scope statement (Section ) reflects funding constraints by period for the expenditure of Project funds or other financial assumptions and constraints. to The scope statement (Section ) includes the deliverables and acceptance criteria. 388 Figure 10-7. Changed .3 Data analysis to .3 Data representation. 389 Figure 10-8. For process box (Direct and Manage Project Work), changed work performance reports to work performance data.

7 483 Figure 12-5. Added a process box: Identify Risks with the output agreements. Part 2 The Standard for Project Management Page Correction 559 Table 1-2. Under the heading Project Management Plan, added 19. Management reviews. 566 Fig 3-1. Under Knowledge Area for Project Stakeholder Management , changed process name to Plan Stakeholder Engagement. 617 Section Added bullet for change log to Project document examples. Part 3 Appendices, Glossary, and Index Page Correction 717 Glossary definition for Project Scope Statement was changed from The description of the Project scope, major deliverables, assumptions, and constraints. to The description of the Project scope, major deliverables, and DEVELOP Project CHARTERD evelop Project Charter is the process of developing a document that formally authorizes the existence of a Project and provides the Project manager with the authority to apply organizational resources to Project activities.

8 The key benefits of this process are that it provides a direct link between the Project and the strategic objectives of the organization, creates a formal record of the Project , and shows the organizational commitment to the Project . This process is performed once or at predefined points in the Project . The inputs, tools and techniques, and outputs of the process are depicted in Figure 4-2. Figure 4-3 depicts the data flow diagram for the 4-2. Develop Project Charter: Inputs, Tools & Techniques, and OutputsTools & TechniquesInputsOutputsDevelop Project Expert judgment .2 Data gathering Brainstorming Focus groups Interpersonal and team skills Conflict Management Facilitation Meeting Business documents Business Enterprise environmental Organizational process Project Assumption log76 Part 1 - Guide Enterprise environmental factors Organizational process assetsBusiness documents Business case Assumption log Agreements Project Plan ScheduleManagement7.

9 1 Plan Plan Projector ProjectCharterFigure 4-3. Develop Project Charter: Data Flow Diagram89 Table 4-1. Project Management Plan and Project DocumentsProject DocumentsProject Management Plan 1. Scope Management plan 2. Requirements Management plan 3. schedule Management plan 4. Cost Management plan 5. Quality Management plan 6. Resource Management plan 7. Communications Management plan 8. Risk Management plan 9. Procurement Management plan 10. Stakeholder engagement plan 11. Change Management plan 12. Configuration Management plan 13. Scope baseline 14. schedule baseline 15. Cost baseline 16. Performance measurement baseline 17. Project life cycle description 18. Development approach 19. Management reviews 1.

10 Activity attributes 2. Activity list 3. Assumption log 4. Basis of estimates 5. Change log 6. Cost estimates 7. Cost forecasts 8. Duration estimates 9. Issue log 10. Lessons learned register 11. Milestone list 12. Physical resource assignments 13. Project calendars 14. Project communications 15. Project schedule 16. Project schedule network diagram 17. Project scope statement 18. Project team assignments 19. Quality control measurements 20. Quality metrics 21. Quality report 22. Requirements documentation 23. Requirements traceability matrix 24. Resource breakdown structure 25. Resource calendars 26. Resource requirements 27. Risk register 28. Risk report 29. schedule data 30. schedule forecasts 31. Stakeholder register 32.