1 / 34

PMBOK GUIDELINES

PMBOK GUIDELINES. PRESENTED BY TRUST THOMAS EROMOSELE STUDENT NO: 125385. Project Management Body of Knowledge. A Guide to the Project Management Body of Knowledge (PMBOK® Guide)

amish
Download Presentation

PMBOK GUIDELINES

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. PMBOK GUIDELINES PRESENTED BY TRUST THOMAS EROMOSELE STUDENT NO: 125385

  2. Project Management Body of Knowledge A Guide to the Project Management Body of Knowledge (PMBOK® Guide) • The PMBOK® is an inclusive term that describes the sum of knowledge within the profession of project management • PMBOK® Guide Identifies and describes that subset of the project management body of knowledge that is generally accepted

  3. The Definition of a “Project” • Program: an exceptionally large, long-range objective that is broken down into a set of projects • Project: a specific, finite task to be accomplished • Task: set of activities comprising a project A Guide to the Project Management Body of Knowledge (PMBOK® Guide)

  4. Key Players • Stakeholders • Anyone actively involved, or have an interest at stake in the project • May have influence, responsibility, and authority over the project • Project Team • Individuals that are performing the project work • Typically involves the use of cross-functional teams • Project Management Team • Project team members that have management responsibilities for the project

  5. Key Players • Project Manager • The individual with overall responsibility for the project • Project Sponsor • The individual with the authority and resources needed to champion the project effort • Typically functions as the linking pin between the project and the parent organization • Customer • The individual/organization that represents the end-user of the project’s resulting product or service

  6. PMI Standards Background • 1969 – PMI founded • 1983 – PMI Special Report on Ethic, Standards, and Accreditation – the Standards portion was The Project Management Body of Knowledge (PMBOK) • 1987 – PMBOK Standard was published • 1996 – A Guide to the Project Management Body of Knowledge (PMBOK® Guide) [first edition] was published • 1999 – PMI accredited as a Standards Development Organization (SDO) by ANSI • 2000 – The PMBOK® Guide - 2000 Edition

  7. PMBOK(Project Management Body of Knowledge) • PMBOK guidelines consist of five process group • Initiating • Planning • Executing • Controlling • Closing

  8. PMBOK • PMBOK five process groups

  9. PMBOK Process Groups and Knowledge Areas

  10. Knowledge Areas • The knowledge areas represent the body of knowledge that a project manager must have in order to consistently deliver successful projects that meet a customer’s expectations in terms of scope, time, cost, and quality of the project deliverables

  11. PMBOK • PMBOK nine knowledge areas • Project integration management • Project scope management • Project time management • Project cost management • Project quality management • Project human resource management • Project communications management • Project risk management • Project procurement management

  12. Knowledge Areas: Definitions and Component Processes IntegrationManagement:Describes the processes and methodsrequired to identify, define, combine,unify, and coordinate the variousprocesses with the other eightknowledge areas Component Processes:Develop project charter,developproject management plan, direct andmanage project execution, monitorand control project work, performintegrated change control, and closeproject or phase

  13. Knowledge Areas: Definitions and Component Processes ScopeManagement:Describes the processes and methodsrequired to ensure that the projectdelivers exactly what the customerrequested and only what the customerrequested to create a successful project Component Processes:Collect requirements, define scope,create WBS, verify scope, andcontrol scope

  14. Knowledge Areas: Definitions and Component Processes TimeManagementDescribes the processes and methodsrequired to create and manageappropriate schedules to completethe project Component Processes:Define activities, sequence activities, estimate activityresources, estimateactivity durations, develop schedule,and control schedule

  15. Knowledge Areas: Definitions and Component Processes CostManagementDescribes the processes and methodsrequired to create and manage theproject budget Component Processes:Estimate costs, determine budget,and control cost

  16. Knowledge Areas: Definitions and Component Processes QualityManagement Describes the processes and methodsrequired to ensure that the projectdelivers the stated and implied needsfor which it was designed Component Processes:Plan quality, perform qualityassurance, and perform qualitycontrol

  17. Knowledge Areas: Definitions and Component Processes HumanResourcesManagement Describes the processes and methodsrequired to eeffectively use the peopleassociated with the project Component Processes:Develop humanresources plan,acquire project team, developproject team, and manage projectteam

  18. Knowledge Areas: Definitions and Component Processes CommunicationsManagement Describes the processes and methodsrequired to create, collect, disseminate, and store information about the project Component Processes:Identify stakeholders, plancommunications, distribute information, manage stakeholderexpectations, report performance

  19. Knowledge Areas: Definitions and Component Processes RiskManagementDescribes the processes and methodsrequired to identify, quantify, andcontrol risks associated with the project Component Processes:Plan risk management, identify risks,perform qualitative risk analysis,perform quantitative risk analysis,plan risk responses, and monitor andcontrol risk

  20. Knowledge Areas: Definitions and Component Processes ProcurementManagementDescribes the processes and methodsrequired to acquire and manage goodsand resources from a source outsidethe project team Component Processes:Plan procurements, conductprocurements, administerprocurements, close procurements

  21. PMBOK Initiating Processes Initiation (5.1)—committing the organization to begin the next phase of the project.

  22. PMBOK Planning Processes • Scope Planning —developing a written scope statement as the basis for future project decisions. • Scope Definition —subdividing the major project deliverables into smaller, more manageable components. • Activity Definition —identifying the specific activities that must be performed to produce the various project deliverables. • Activity Sequencing —identifying and documenting interactivity dependencies. • Activity Duration Estimating —estimating the number of work periods which will be needed to complete individual activities. • Schedule Development —analyzing activity sequences, activity durations, and resource requirements to create the project schedule.

  23. PMBOK Planning Processes. cont. • Resource Planning —determining what resources (people, equipment, materials) and what quantities of each should be used to perform project activities. • Cost Estimating —developing an approximation (estimate) of the costs of the resources needed to complete project activities. • Cost Budgeting —allocating the overall cost estimate to individual work items. • Project Plan Development —taking the results of other planning processes and putting them into a consistent, coherent document.

  24. PMBOK Planning Processes cont. • Quality Planning —identifying which quality standards are relevant to the project and determining how to satisfy them. • Organizational Planning —identifying, documenting, and assigning project roles, responsibilities, and reporting relationships. • Staff Acquisition —getting the human resources needed assigned to and working on the project. • Communications Planning —determining the information and communications needs of the stakeholders: who needs what information, when will they need it, and how will it be given to them

  25. PMBOK Planning Processes cont. • Risk Identification —determining which risks are likely to affect the project and documenting the characteristics of each. • Risk Quantification —evaluating risks and risk interactions to assess the range of possible project outcomes. • Risk Response Development —defining enhancement steps for opportunities and responses to threats. • Procurement Planning —determining what to procure and when. • Solicitation Planning —documenting product requirements and identifying potential sources

  26. PMBOK Executing Processes

  27. PMBOK Executing Processes • Project Plan Execution —carrying out the project plan by performing the activities included therein. • Scope Verification —formalizing acceptance of the project scope. • Quality Assurance —evaluating overall project performance on a regular basis to provide confidence that the project will satisfy the relevant quality standards. • Team Development —developing individual and group skills to enhance project performance.

  28. PMBOK Executing Processes cont. • Information Distribution —making needed information available to project stakeholders in a timely manner. • Solicitation —obtaining quotations, bids, offers, or proposals as appropriate. • Source Selection —choosing from among potential sellers. • Contract Administration —managing the relationship with the seller.

  29. PMBOK Controlling Processes

  30. PMBOK Controlling Processes • Overall Change Control —coordinating changes across the entire project. • Scope Change Control —controlling changes to project scope. • Schedule Control —controlling changes to the project schedule. • Cost Control —controlling changes to the project budget.

  31. PMBOK Controlling Processes cont. • Quality Control —monitoring specific project results to determine if they comply with relevant quality standards and identifying ways to eliminate causes of unsatisfactory performance. • Performance Reporting —collecting and disseminating performance information. This includes status reporting, progress measurement, and forecasting. • Risk Response Control —responding to changes in risk over the course of the project.

  32. PMBOK Closing Processes

  33. PMBOK Closing Processes • Administrative Closure —generating, gathering, and disseminating information to formalize phase or project completion. • Contract Close-out —completion and settlement of the contract, including resolution of any open items

  34. THANK YOU FOR LISTENING!

More Related