pmbok key concepts

PMP Fundamentals

Every facet of human life is a project. Every little step we take, from the moment we wake up up to the time we settle to sleep, is filled with mini projects. It's then not a stretch to assume that the way we handle actual projects (from work, school, etc.) is reflection of the way we handle the biggest project there is - our existence. That's why it's doubly important to come up with the perfect habit of proper planning and management of projects.This page covers general information about the discipline of project management.1. A project is a temporary endeavor. Projects are unique and non-repetitive. Building a road is an example of a project. The process of building a road takes a finite amount of time, and produces a unique product. Operations on the other hand are repetitive. Delivering mail every day is an example of operation.2. The characteristics associated with a project are - unique purpose, temporary in nature, require resources (often from various domains), should have a primary sponsor and/or customer, and involves uncertainty.3. Project management is the application of knowledge, skills, tools, and techniques to project activities in order to meet project requirements4. A program consists of a related group of projects. Projects are finite where as programs are ongoing and continuous. Programs may be repetitive and cyclic. In some cases Project Management is a subset of Program Management. The project manager may report to the program manager in such cases. A project may or may not be a part of a program, but a program will always have projects.A portfolio consists of multiple programs. As an example Building a house may be a project. Building a colony consisting of row of houses is a program. Building a set of colonies to develop a new city can be considered a portfolio.5. A subproject is a subset of a project. Subprojects can be subcontracted. Technical or Functional Manager may be in charge of a subproject.6. Type of organization - This is an important concept to understand for the PMP exam. The type of organizations in decreasing order of Project Manager's authority are - Projectized Strong Matrix Weak Matrix FunctionalProject Manager has maximum authority in a Projectized organization and least authority in a Functional organization. In Functional organizations staff is organized based upon their specialty, such as engineering or sales. In these organizations, functional managers are responsible for specialized departments like marketing. In Functional organization, the role of Project Manager is limited. In Projectized organization, PMs have more authority and independence. All the persons in the project team report to the Project Manager.Real situations are a mixture of functional and projectized organizations. These mixed situations are called matrix organizations. Strong matrix organizations have characteristics of projectized organizations. Weak matrix organizations have characteristics of functional organizations.7. Leadership style varies from autocratic to democratic. Shared leadership involves team members taking most of the decisions. It encourages team development.8. Project Management consists of ten Knowledge Areas. These are Project Integration Management Project Scope Management Project Cost Management Project Time Management Project Risk Management Project Quality Management Project HR Management Project Communication Management Project Procurement Management Project Stakeholder ManagementEach Knowledge area has further Processes. There are a total of 47 processes. Each process has inputs, outputs and "tools and techniques" (ITTO). The PMBOK primarily covers each of the processes and it's ITTO in detail. You need to understand the concepts related to each of the input, output and "tools and techniques".9. Further the discipline of Project Management has five process groups. These are - Initiation Planning Execution Control ClosureEach process is part of one of these five project phases. It is important to know the process group for each of the 47 processes.10. Project Sponsors are primarily involved in funding the project. Tasks performed by project sponsor include Provides financial support Accepts the project during scope verification May provide key milestone and deliverables due dates Does not sign the Project Charter. This is done by Senior Management.Tasks performed by the senior management include Issues the project charter Helps organize the work into projects Helps identify risks Approves the final project planStakeholders are all the individuals that are concerned with the project. Stakeholders have vested interest in the outcome of the project. They include project team members, customers, management, and other individuals who get impacted by the project. Stakeholders role includes - Distributed information during the project. Notified of project plan changes Are listed in the project team directory. Become risk owners.11. At the end of each project phase, reviews against a set of metrics are performed. If the project fails to meet these metrics, the project may not be allowed to continue. These phase end reviews are called Stage gates or Phase exits.12. Project Life cycle: All projects have four parts in life cycle. These are -12. Starting the project12. Organizing and preparing12. Carrying out the project work12. Closing the project1. At the beginning of the project there is less cost and less demand for resources. Also there is a higher risk of failure at the beginning of the project. The risk reduces over the life of the project. The stakeholder influence is maximum at the beginning of the project and reduces over the life of the project.1. Projects have multiple competing constraints. These are -. Scope. Quality. Schedule. Budget. Resources. RiskDifferent stakeholders may give different priority to these constraints. As an example budget may be the most important constraint for the project sponsor. Scope may be imortant for a customer support engineer, and quality may be important for the testing team. A project team has to balance the demand of these constraints. Progressive Elaboration means adding more details in an iterative fashion. Project Management Plan is developed using progressive elaboration. Project Management Office (PMO) is a group in an organization providing centralized project management services. The exact role of PMO may vary across organizations. PMO may provide services related to project management or may be directly responsible for project management. Enterprise Environmental Factors refer to external factors in the company, that may influence the project. Enterprise Environmental Factors may include cultural factors, political climate, infrastructure and other external factors within the organization that may impact the project. Enterprise Environmental Factors are input to many planning processes.

Project Integration Management

This chapter covers key concepts related to Project Integration Management.1. The knowledge area of Project Integration Management consists of the following seven processes -

Project Integration ProcessesProcessProject PhaseKey Deliverables

Develop Project CharterInitiatingProject Charter

Develop Project Management PlanPlanningProject Management Plan

Direct and Manage Project WorkExecutionDeliverables

Monitor and Control Project WorkMonitoring and ControlChange Requests

Perform Integrated Change ControlMonitoring and ControlChange Requests status updates

Close Project or PhaseClosureFinal product

2. A project charter Formally authorizes the project. Gives the objectives and business case Identifies the Project Manager. Generic enough not to change often. Written by a Manager higher in authority than Project Manager. Includes name, description, deliverables A project does not start unless it has a Project charter.3. The Inputs, Tools and Techniques and Output of Develop Project Charter process are given below.

Develop Project Charter processInputsTools & TechniquesOutputs

Project Statement of workExpert judgmentProject Charter

Business case

Contract

Enterprise environmental factors

Organizational process assets

4. During project execution the project team focuses on completing the tasks assigned. The Senior Management protects the project from changes and loss of resources. The Project Manager integrates all the pieces into the project as a whole.5. The Inputs, Tools and Techniques, and Outputs of the Develop Project Management Plan process are given in the table below.

Develop Project Management Plan processInputsTools & TechniquesOutputs

Project charterExpert judgmentProject Management Plan

Outputs from planning processes



6. At the end of each phase of a project, a lessons learned document must be prepared. The lessons learned document defines what was done right, wrong etc. It is required to be completed in order for the project to be completed.7. Project Management Information System (PMIS) is a system that keeps track of status of all the project tasks. It is used to track the status of the project. The exam does not focus on any specific system (for example Microsoft Project ).8. Project Management Plan is developed by Project Manager with inputs from the team, stakeholders and management. Project Management Plan development is iterative. A Project Management Plan is bought into, approved, realistic and formal.9. A Project Management Plan includes - Project Charter Budget Schedule Resources Scope Statement WBS Responsibility charts/assignments Management Plans10. A Project Management Plan consolidates other management plans. These are:J. Scope management planJ. Requirement management planJ. Schedule management planJ. Cost management planJ. Quality management planJ. Process improvement planJ. Human resource planJ. Communication management planJ. Risk management planJ. Procurement management planThe Project Management Plan also includes project baselines. These are:J. Schedule baselineJ. Cost performance baselineandJ. Scope baseline1. Project baseline refers to the original version of the project management plan. Once the project management plan is baselined, it may only be changed by raising a change request.1. Progressive Elaborationinvolves the process of taking a project from concept to detailed design.1. Kick-off meeting happens after the planning phase and before the project execution. It is typically used to communicate responsibilities of key stakeholders.1. Direct and Manage Project Work process includes performing the work defined in the PMP to achieve project goals. The Input, Tools and Techniques and Outputs of this process are given below.

Direct and Manage Project Work processInputsTools & TechniquesOutputs

Project management planExpert judgmentDeliverables

Approved change requestsProject management information systemWork performance information

Enterprise Environmental factorsChange requests

Organizational process assetsProject management plan updates

Project document updates

1. Monitor and Control project work process includes tracking and reviewing the progress of the project. The Input, Tools and Techniques and Outputs of this process are given below.

Monitor and Control project work processInputsTools & TechniquesOutputs

Project management planExpert judgmentChange requests

Performance reportsProject management plan updates

Enterprise environmental factorsProject document updates


1. The change requests that get generated are evaluated as part of the Perform Integrated Change Control process. The change requests on the project deliverables and project artifacts are managed in this process. The Input, Tools and Techniques and Outputs of this process are given below.

Perform Integrated Change Control processInputsTools & TechniquesOutputs

Project management planExpert judgmentChange request status updates

Work performance informationChange control meetingsProject management plan updates

Change requestsProject document updates



1. Change Control Boardis formed to review change requests. It is used to approve or reject change requests. After the project scope has been baselined, each requested change must go through a change control review process.1. Project Manager needs to be proactive in looking for deviations from project plan and then take timely corrective action. After that the Project Manager needs to evaluate the effectiveness of corrective action, and measure performance of corrective action, and then determine the need for further corrective action.1. When a change request is received, the following steps must be taken (in this order) -19. Evaluate (assess) the impact of change to the project19. Create alternatives including cutting other tasks, crashing, fast-tracking etc.19. Meet with management, sponsors etc.19. Meet with the customer if necessary1. The Close Project or Phase is the process of formal completion of all project related activities. The Input, Tools and Techniques and Outputs of this process are given below.

Close Project or PhaseInputsTools & TechniquesOutputs

Project management planExpert judgmentFinal product, service or result transition

Accepted deliverablesOrganizational process assets updates


1. At the end of each phase of a project, a lessons learned document must be prepared. The lessons learned document defines what was done right, wrong etc. It is required to be completed in order for the project to be completed.

Project Scope Management

This chapter covers key concepts related to Project Scope Management.1. The knowledge area of Project Scope Management consists of the following processes -Scope Management ProcessesProcessProject GroupKey Deliverables

Plan Scope ManagementPlanning

Collect RequirementsPlanningRequirements document

Define Scopeplanningproject scope statement

Create WBSplanningWBS, WBS dictionary

Validate ScopeMonitoring and ControllingAcceptance deliverables

Control ScopeMonitoring and ControllingChange Requests

2. The knowledge area ofScope Managementincludes the processes required to ensure that the project includes all the work, and only all the work required to complete the project successfully. It is primarily concerned with controlling what is and what is not in the scope.3. Project Portfolio Management is the process of project selection. It involves making a decision about which project an organization should execute.4. There are two types of project selection methods. These are Benefits Measurement Constrained Optimization5. Benefits Measurement project selection methods involve comparing the values of one project against another. There are the following type of Benefit Measurement project selection techniques - Murder Boards - This involves a committee asking tough questions from each project Scoring Models - Different projects are given scores based on certain defined criteria. Project with higher score is selected. Benefits Cost Ratio - This technique involves computing benefits to cost ratio (BCR) for a project. Project with higher BCR is selected. Payback period - This technique involves considering how long it takes back to "pay back" the cost of the project. Inflation or interest earned in not considered in this technique. A project with lower pay back period is better. Discounted Cash Flow - This technique takes into account the interest earned on the money. The Future Value (FV) of projects is compared.FV=PV(1+i)nPV is the present value of the project. A project with higher present value is better. Internal Rate of Return (IRR) - A project that has higher IRR is better, as it is giving higher return on money.6. Constrained Optimization Project selection methods are used for large projects. These are techniques based on mathematical models. The Constrained Optimization techniques are - Linear Programming Non-Linear Programming Integer Algorithm Dynamic Programming Multi-objective Programming7. Expected monetary value of a project (or expected value) is equal toprobability*impact. So if probability of a project's success is 20% and revenue earned if successful is $100000, then the net value of the project will be $20,000. A project with higher net value should be selected when performing project selection.8. Management by Objective (MBO)is a management philosophy with three objectives - Establish unambiguous and realistic objectives Periodically Evaluate if objectives are being met Take corrective actions.MBO works only if management supports it.9. Collect Requirements process involves documenting stakeholders needs to meet project objectives. The Inputs, Tools and Techniques, and Outputs of Collect Requirements process are given below.Collect Requirements ProcessInputsTools & TechniquesOutputs

Project charterInterviewsRequirements documentation

Stakeholder registerFocus groupsRequirements management plan

Facilitated workshopsRequirements traceability matrix

Group creativity techniques

Questionaires and surveys

Observations

Prototypes

Group decision-making techniques

10. The Define Scope process involves defining detailed description of the project and major deliverables. The Input, Tools and Techniques and Output of the Define Scope process are:Define Scope ProcessInputsTools & TechniquesOutputs

Project charterExpert judgmentProject scope statement

Requirements documentationProduct analysisProject document updates

Organizational process assetsAlternative identification

Facilitated workshops

11. Create WBS is the process of dividing the project deliverables into smaller components. The Inputs, Tools and Techniques and Outputs of Create WBS process are:Create WBS ProcessInputsTools & TechniquesOutputs

Project Scope StatementDecompositionWBS

Requirements documentationWBS dictionary

Organizational process assetsScope baseline

Project document updates

12. Work Breakdown Structure (WBS) is an important part of the exam. It is a graphical representation of the hierarchy of the project. The WBS template can be reused across projects. WBS forces the project team to think through all the levels of the project. If a task is not in the WBS, then it is not part of the project.13. 8/80 rule for WBS- No task should be less than 8 hours or more than 80 hours.14. WBS dictionaryexplains all the WBS components. Also WBS is input to most of the planning processes. Specifically WBS is input to the following processes - Cost Estimating Cost Budgeting Scope control Activity Definition Plan Purchases and Acquisitions15. The Validate Scope is the process in which the project customer formally accepts the project deliverables. Scope Validation happens at the end of each phase. During the Validate Scope process customer gives feedback on work performed. While Validate Scope process focuses on customer acceptance, Perform Quality Control process focuses on correctness of work.16. The table below gives inputs, Tools & Techniques, and Outputs of the Validate Scope process.Validate Scope ProcessInputsTools & TechniquesOutputs

Project management planInspectionAccepted Deliverables

Requirements documentationChange requests

Requirements traceability matrixProject document updates

Validated deliverables

17. Control Scope process involves monitoring the status of project and managing scope changes. The Inputs, Tools and Techniques and Outputs of Control Scope process are:Control Scope ProcessInputsTools & TechniquesOutputs

Project management planVariance analysisWork performance measurements

Requirements documentationChange requests

Requirements traceability matrixProject management plan updates

Organizational process assetsOrganizational process assets updates

Work performance informationProject document updates

Project Time / Schedule Management

This chapter covers key concepts related to Project Time Management.1. The knowledge area of Project Time Management consists of the following processes -Time Management ProcessesProcessProject PhaseKey Deliverables

Plan Schedule ManagementPlanning

Define ActivitiesPlanningActivity List, Milestone list

Sequence ActivitiesPlanningProject Schedule network diagrams

Estimate Activity ResourcesPlanningActivity resource requirements,Resource breakdown structure

Estimate Activity DurationsPlanningActivity duration estimates

Develop SchedulePlanningProject Schedule

Control ScheduleMonitoring and ControllingWork Performance measurements,Change Requests

2. The Define Activities process has the following Inputs, Tools and Techniques and Outputs -Define Activities ProcessInputsTools and TechniquesOutputs

Scope baselineDecompositionActivity list

Enterprise environmental factorsRolling wave planningActivity attributes

Organizational process assetsTemplatesMilestone list

Expert judgment

3. The Sequence Activities process has the following Inputs, Tools and Techniques and Outputs -Sequence Activities ProcessInputsTools and TechniquesOutputs

Project scope statementPrecedence diagram method (PDM) or AONProject schedule network diagrams

Activity ListApplying leads and lagsProject document updates

Activity attributesSchedule Network Templates

Milestone listDependency determination


4. The Estimate Activity Resources process has the following Inputs, Tools and Techniques and Outputs -Estimate Activity Resources ProcessInputsTools and TechniquesOutputs

Activity ListExpert judgmentActivity resource requirements

Activity attributesAlternative analysisResource breakdown structure

Resource calendarsPublished estimating dataProject document updates

Enterprise environmental factorsBottom-up estimating

Organizational process assetsProject Management software

5. The Estimate Activity Durations process has the following Inputs, Tools and Techniques and Outputs -Estimate Activity Durations ProcessInputsTools and TechniquesOutputs

Activity listExpert judgmentActivity duration estimates

Activity attributesAnalogous estimatingProject document updates

Activity resource requirementsParametric estimating

Resource calendarsThree-point estimates

Project scope statementReserve analysis



6. The Develop Schedule process has the following Inputs, Tools and Techniques, and Outputs-Develop Schedule ProcessInputsTools and TechniquesOutputs

Organizational process assetsSchedule network analysisProject Schedule

Project scope statementCritical path methodSchedule baseline

Activity ListSchedule CompressionSchedule data

Activity attributesWhat-if scenario analysisProject document updates

Project Schedule Network diagramResource levelling

Activity Resource requirementsCritical chain method

Resource CalendarsScheduling tool

Activity duration estimatesApplying calendars

Project Management Plan -Risk RegisterAdjusting Leads and Lags


7. The Control Schedule process has the following Inputs, Tools and Techniques and Outputs -Control Schedule ProcessInputsTools and TechniquesOutputs

Project management planPerformance reviewsWork performance measurements

Project scheduleVariance analysisOrganizational process assets updates

Work performance informationProject management softwareChange requests

Organizational process assetsResource levelingProject management plan updates

What-if scenario analysisProject document updates

Adjusting leads and lags

Schedule compression

Scheduling tool

8. Bar charts (or Gantt charts) are used to display tasks and their dates in a graphical fashion. They are used to display information of the type task 1 is scheduled from date A to date B. Typically the date range is displayed in the X-axis and the tasks on the Y-axis. Bar charts do not show task dependencies. They are generally used to track progress and show to the team.9. Milestone charts are similar to bar charts but display only major events. They display major milestones (for example bridge design completed). They are used to report status to Management.10. Network diagrams are used to display activities and their dependencies. Network diagrams can be used to perform critical path analysis. Network diagrams can also be used to perform crashing and fast tracking of the project.There are two type of network diagrams - Activities on Node (or Precedence) Activities on Arrow (or AOA)Precedence is most commonly used. AON and AOA cannot have loops or conditional relationships.11. An activity in a network diagram is displayed as shown below.Activity name

Activity NumberEstimate

12. As an example -Documentation

25 days

13. In the above example Documentation is activity number 2 and is estimated to last 5 days.14. Precedence (or Activity on Node) diagrams can be used to display four type of relationship between activities. These are Finish-To-Start Start-To-Start Start-To-Finish Finish-To-FinishFinish-to-start relationship means the dependent activity cannot start until the first activity is finished. This is the most common way to represent relationships between activities.15. Activity on Array (AOA) network diagrams have the following characteristics. AOA only uses Finish-To-Start relationship between tasks. PERT and CPM can only be used with AOA. Dummy events are shown with dotted lines. They do not take any time. They show dependencies between tasks.16. Longest path through the network diagram is called the critical path. The activities on the critical paths are called critical activities.17. Lags are inserted waiting times in between tasks. For example Task B cannot start until three days after task A completes.18. Slack or Float is the amount of time a task can be delayed without delaying the project. Tasks on the critical path have zero float.19. Critical Path Method (CPM) has the following characteristics. It uses one time estimate per activity It can be drawn only using AOA diagrams It can have dummy events20. Program Evaluation and Review Technique (PERT) has the following characteristics. It uses three estimates per activity - optimistic, pessimistic and most likely It can be drawn only using AOA diagrams It can have dummy events21. PERT utilizes more information than CPM as it considers the "Pessimistic" and "Optimistic" values in addition to the "Most Likely" value in its calculations. The following are formulae used by PERT -Mean = (P + 4M + O)/6Standard Deviation = (P-O)/6Variance = ((P-O)/6)2Here P is the pessimistic estimate, O is the optimistic estimate and M is the most likely estimate.22. GERT is another type of network diagram. It can support looping.23. If a project has more than one critical paths then the risk to the project increases.24. Resource levelling refers to keeping the resources same across the duration of the project.

Project Cost Management

This chapter covers key concepts related to Project Cost Management.1. The knowledge area of Project Cost Management consists of the following processes -Project Cost ProcessesProcessProject PhaseKey Deliverables

Plan Cost ManagementPlanning

Estimate CostsPlanningActivity Cost Estimates,Basis of estimates

Determine BudgetPlanningCost performance baseline

Control CostsMonitoring and ControllingWork performance measurements

2. Alternative identification process identifies other solutions to an identified problem.3. Value Analysis approach is used to find more affordable, less costly methods for accomplishing the same task.4. The Estimate Costs process takes the following inputs - Scope baseline Project schedule Human resource plan Risk register Enterprise environmental factors Organizational process assets5. Depreciation is technique used to compute the estimated value of any object after few years. There are three type of depreciation techniques. These are Straight line depreciationThe same amount is deprecated (reduced) from the cost each year. Double-declining balance- In the first year there is a higher deduction in the value - twice the amount of straight line. Each year after that the deduction is 40% less than the previous year. Sum of year depreciation- Lets say the life of an object is five years. The total of one to five is fifteen. In first year we deduce 5/15 from the cost, in second year we deduce 4/15, and so on.6. Analogous Estimating is an estimating technique with the following characteristics - Estimates are based on past projects (historical information) It is less accurate when compared to bottom-up estimation It is a top-down approach It takes less time when compared to bottom-up estimation It is a form of an expert judgment7. InParametric Modeling Estimation, you use a mathematical model to make an estimate. It is of two types. Regression Analysisis a mathematical model based upon historical information. Learning Curvemodel is based upon the principal that the cost per unit decreases as more work gets completed.8. Bottom up estimation is same as WBS estimation. It involves estimating each work item and adding the estimates to get the total project estimate.9. You can expect five to ten questions related to Earned Value Management. These are generally pretty simple once you have good understanding of the concepts, and remember the formulae. These formulae are explained below.10. Planned Value (PV)refers to what the project should be worth at this point in the schedule. It is also referred as BCWS (Budgeted Cost of Work Scheduled).11. Earned Value (EV)is the physical work completed to date and the authorized budget for that. It is also referred as BCWP (Budgeted Cost of Work Performed).12. Actual Cost (AC)is the actual amount of money spent so far. It is also referred as ACWP (Actual Cost of Work Performed).13. Estimate At Completion (EAC)refers to the estimated total cost of the project at completion.14. CPIrefers to Cost Performance Index. It is defined asCPI = EV/ACIf CPI is less than 1, this means that the project is over budget.15. BACrefers to Budget at Completion. It is related to EAC.EAC = BAC/CPI16. ETCrefers to Estimate to Completion. It is defined asETC = EAC - AC17. CVrefers to Cost Variance. It is defined asCV = EV - AC18. SVrefers to Schedule Variance. It is defined asSV = EV - PVNegative cost or schedule variance means that project is behind in cost or schedule.19. SPIrefers to Schedule Performance Index. It is defined asSPI = EV/PV20. VACrefers to Variance At Completion. It is defined asVAC = BAC - EAC21. The process of Cost budgeting defines time phased cost estimates for the project. For example, in the first month the project will require $10,000. Cost estimating involves defining cost estimates for tasks. Cost budgeting defines cost estimates across time.22. The tools and techniques used for Estimate Costs are - Expert judgment Analogous estimating Parametric estimating Bottom-up estimating Three-point estimates Reserve analysis Cost of quality Project Management estimating software Vendor bid analysis23. Cost baseline refers to what is expected to be spent on the project. It is usually an S-curve. That is the expenditure is less in the beginning, and the end. The expenditure is maximum during the middle of the project.24. The after project costs are called life cycle costs.

Project Quality Management

This chapter covers key concepts related to Project Quality Management.1. The knowledge area of Project Quality Management consists of the following processes -Quality Management ProcessesProcessProject PhaseKey Deliverables

Plan Quality ManagmentPlanningQuality Management Plan,Quality Metrics

Perform Quality AssuranceExecutionChange Requests

Perform Quality ControlMonitoring and ControllingQuality control measurements

2. The process of Plan Quality Management includes defining quality requirements of the project and documenting how the project will ensure compliance. The ITTO of Plan Quality Management process are given below.Plan Quality ProcessInputsTools and TechniquesOutputs

Scope baselineCost-benefit analysisQuality management plan

Stakeholder registerCost of qualityQuality metrics

Cost performance baselineControl chartsQuality checklists

Schedule baselineBenchmarkingProcess improvement plan

Risk registerDesign of experimentsProject document updates

Enterprise environmental factorsStastical sampling

Organizational process assetsFlowcharting

Proprietary quality management methodology

Additional quality planning tools

3. Grade refers to category or rank given to entities having same functional use but different technical characteristics. As an example, for different grades of hotels, the customers expectations are different. Poor grade may be acceptable, but poor quality is not.4. The aim of quality is to ensure "Conformance to requirements" and "fitness for use".5. Quality Policy defines the company goals and how to adhere to them. This acts as an input to Quality Planning for a project. Quality Policy is part of Organizational Process assets.6. Deming suggested a process of Plan-Do-Check-Act to improve quality. According to Deming, each process should go through these steps to improve the quality.7. Kaizen Theory- Apply continuous small improvements to reduce costs and ensure consistency.8. Marginal Analysis- You compare the cost of incremental improvements against the increase in revenue made from quality improvements. Optimal quality is reached when cost of improvements equals the costs to achieve quality.9. The value of sigma of Normal Distribution are given below. These are important for the exam.Normal Distribution Sigma valuesSigmaPercentage covered

One sigma68.26%

Two sigma95.46%

Three sigma99.73%

Six sigma99.99%

Based on the above table, we can see that in six sigma one out of 10,000 items can have defects. In three sigma, twenty seven out of 10,000 items can have defects.10. Giving extras i.e. doing more than the project scope is called gold-plating. PMI does not recommend gold-plating.11. Quality must be planned in and not inspected in. Prevention is more important than inspection.12. Quality Assurance is done during execution of the project. It includes - Process of evaluating overall performance on a regular basis Re-evaluating quality standards Quality audits - structured review of quality activities that identify lessons learned. These lessons learned are used for process improvement.Perform Quality Assurance involves reviewing the quality requirements and auditing the results from quality control measurements. Perform Quality Assurance uses data created during Perform Quality Control.ITTO of Perform Quality AssuranceInputsTools and TechniquesOutputs

Project management planPlan Quality and Perform Quality Control tools and techniquesOrganizational process updates

Quality metricsQuality auditsChange requests

Work performance informationProcess analysisProject management plan updates

Quality control measurementsProject document updates

13. Perform Quality Control focuses on correctness of work. It includes inspections. The inputs, tools and techniques and outputs (ITTO) used for Perform Quality Control process are -ITTO of Perform Quality ControlInputsTools and TechniquesOutputs

Project management planCause and effect diagramQuality control measurements

Quality metricsControl chartsValidated changes

Quality checklistsFlowchartingValidated deliverables

Work performance measurementsHistogramOrganizational process assets updates

Approved change requestsPareto chartChange requests

DeliverablesRun chartProject management plan updates

Organizational process assetsScatter diagramProject document updates

Statistical Sampling

Inspection

Approved change requests review

14. In Just-In-Time (JIT) Quality, the amount of inventory is zero. The inputs are made available, just when they are required. This reduces the storage cost.15. Rule of seven: In control charts, if there are seven points on one side of mean, then an assignable cause must be found.16. The process ofAnalogous Estimationinvolves looking at the history of past projects, and use them to make estimates.

Human Resource Management

This chapter covers key concepts related to Project Human Resource Management.1. The knowledge area of Project Human Resource Management consists of the following processes -Human Resource Management ProcessesProcessProject PhaseKey Deliverables

Plan Human Resource ManagementPlanningHuman Resource Plan

Acquire Project TeamExecutionProject Staff assignments

Develop Project TeamExecutionTeam performance assessments

Manage Project TeamExecutionChange requests

2. Plan Human Resource Management process involves identifying and documenting project roles and responsibilities. The table below gives the inputs, tools and techniques, and Outputs for the Plan Human Resource Management process -Plan Human Resource Management ProcessInputsTools and TechniquesOutputs

Enterprise environmental factorsOrganization charts andposition descriptionsHuman resource plan

Organizational process assetsOrganizational Theory

Activity resource requirementsNetworking

3. Acquire project team process involves identifying and obtaining the team necessary to execute the project. The table below gives the inputs, tools and techniques, and Outputs for the Acquire project team process -Acquire project team processInputsTools and TechniquesOutputs

Project management planPre-assignmentProject staff assignments

Enterprise environmental factorsNegotiationResource calendars

Organizational process assetsAcquisitionProject management plan updates

Virtual teams

4. Develop project team process involves improving the competencies of the team members and improving teamwork between the team. The table below gives the inputs, tools and techniques, and Outputs for the Develop project team process -Develop project team processInputsTools and TechniquesOutputs

Project staff assignmentInterpersonal skillsTeam performance assessments

Project management planTrainingEnterprise environmental factors updates

Resource calendarsTeam-building activities

Ground rules

Co-location

Recognition and rewards

5. Responsibility Assignment Matrix (RAM)defines who does what. TheStaffing Management Plandefines when will people get added and removed from the project.6. A Project Manager may yield authority over the project team in one of the following ways - Referent - project team knows the PM Formal Power - Power due to Project Managers position Technical Power - Project Manager has strong technical skills in the projects domain. Coercive Power - The project team is afraid of the power the Project Manager holds.7. Conflicts in the team are caused due to the following reasons in decreasing order of occurrences. Schedules Project Priorities Resources Technical OpinionsSo the most common cause of conflicts in projects are issues related to schedules.8. Conflicts are best resolved by those in the team.9. There are standard conflict resolution techniques available to resolve conflicts. These are (from best to worst) - Problem Solving or Confrontation (look at the facts, analyze them and find a solution). This is an example of win-win situation. Compromising (Find the middle route). This is an example of loose-loose situation. Withdrawal or Avoidance Smoothing (Emphasize the agreements) Forcing (Do it my way). This is an example of win-loose situation.10. The process of problem solving has these steps - Define the cause of the problem Analyze the problem Identify solution Implement a decision Review the decision, and confirm that the problem is solved.11. Manage project team process is the process of tracking team member performance and managing issues within the team. The table below gives the inputs, tools and techniques, and Outputs for the Manage project team process -Manage project team processInputsTools and TechniquesOutputs

Project staff assignmentsObservation and conversationEnterprise environmental factors updates

Project management planProject performance appraisalsOrganizational process assets updates

Team performance assetsConflict managementChange requests

Performance reportsIssue logProject management plan updates

Organizational process assetsInterpersonal skills

12. War room is a technique for team building. As part of this the project team meets in one room. It helps to create a project identity.13. Halo Effectis the assumption that because the person is good at a technology, he will be good as a project manager.14. There are many organizational theories. Some of the main ones are - Expectancy Theory, McGregory Theory, Herzberg Theory, Maslow's Hierarchy of needs.15. Expectancy Theory- People accept to be rewarded for their efforts. This is a motivation factor. People put in more efforts because they accept to be rewarded for their efforts.16. McGregory Theory of X and Y- There are two type of employees. Employees of type X need to be always watched. They cannot be trusted and need to be micro managed. Employees of type Y, on the other hand, are self-motivated. They can work independently.17. Herzberg Theory- Hygiene factors (salary, cleanliness etc.) if not present can destroy motivation. However good hygiene alone does not improve motivation. What motivates people is the work itself. The motivation factors for employees include responsibility, self-actualization, growth, recognition etc.18. Maslow's Hierarchy of needs- there are various levels of needs for an employee. When a lower level is met, employee attempts to reach the next higher level. The maximum satisfaction is achieved when the employee reaches the highest level of satisfaction - self-fulfillment. These level of needs from the highest to lowest are - Self-fulfillment Esteem Social Safety Physiology

Project Communications Management

This chapter covers key concepts related to Project Communications Management.1. The knowledge area of Project Communications Management consists of the following processes -Communications Management ProcessesProcessProcess GroupKey Deliverables

Plan Communications ManagementPlanningCommunication Management Plan

Manage CommunicationsExecutingOrganization processassets updates

Control CommunicationMonitoring and ControllingPerformance Reports

2. Plan Communications Management defines how and when the various stakeholders receive information, and communicate with each other.3. Memos, emails are examples of non-formal communication.4. The total number of communication channels between n stakeholders is n(n-1)/2. So if there are ten stakeholders in a project, there are 45 channels of communication.5. Plan Communications process involves determining what kind of information should be shared with which project stakeholder. This is documented in the Communication management plan. Also documented is how and when the communication needs to be shared with stakeholders. The Inputs, Tools and Techniques, and Output of Plan Communications process is given below.Plan Communications ProcessInputsTools & TechniquesOutputs

Stakeholder registerCommunication requirements analysisCommunications management plan

Stakeholder management strategyCommunication technologyProject document updates

Enterprise environmental factorsCommunication models

Organizational process assetsCommunication methods

6. Throughout the project duration, information is shared with stakeholders as planned. This sharing of information is part of the Manage Communications process. The Inputs, Tools and Techniques, and Output of Manage Communications process is given below.Manage CommunicationsInputsTools & TechniquesOutputs

Project management planCommunication methodsOrganizational process assets updates

Performance reportsInformation distribution tools


7. The Control Communications process involves sharing the project status reports and measurements with appropriate stakeholders.Control Communications ProcessInputsTools & TechniquesOutputs

Project Management PlanVariance analysisPerformance reports

Work performance informationForecasting methodsOrganizational process assets updates

Work performance measurementsCommunication methodsChange requests

Budget forecastsReporting systems


Project Risk Management

This chapter covers key concepts related to Project Risk Management.1. The knowledge area of Project Risk Management consists of the following processes -Risk Management ProcessesProcessProject PhaseKey Deliverables

Plan Risk ManagementPlanningRisk Management Plan

Identify RisksPlanningRisk register

Perform Qualitative Risk AnalysisPlanningRisk register updates

Perform Quantitative Risk AnalysisPlanningRisk register updates

Plan Risk ResponsesPlanningRisk related contract decisions

Monitor and Control RisksMonitoring and ControllingRisk register updates

2. A project risk is a potential source of deviation from the project plan. Project risks can have a negative or positive impact on the project. Project risks that are negative are called threats. Project risks that are positive are called opportunities.3. Responses to threat include -- Reducing the probability of risk Developing contingency plans Passively accepting consequences. Transferring riskInsurance is an example of transferring risk.4. Non-critical risks should be documented. They should be revisited and reviewed regularly.5. Risks are identified in all phases.6. Work-around refers to how to handle risks that have occurred but are not part of risk response plan. This happens in risk monitoring and control phase.7. Delphi technique is most commonly used to obtain expert opinions on technical issues. It can be used to get inputs on Scope, Estimates or Risks. Some characteristics of the Delphi technique are - The experts identities are anonymous. They are not in the same room. The PM tries to build a consensus among the experts.

Procurement Management

This chapter covers key concepts related to Project Procurement Management.1. Procurement Management involves getting work done by people outside the project team. Project Procurement Management includes administering contracts and change control process to manage contracts or purchase orders. The knowledge area of Project Procurement Management consists of the following processes -Procurement Management ProcessesProcessProject PhaseKey Deliverables

Plan Procurement ManagementPlanningProcurement Management Plan

Conduct ProcurementsExecutionSelected Sellers, Procurement contract award

Control ProcurementsMonitoring and ControllingChange requests

Close ProcurementsClosureClosed procurements

2. The Plan Procurement process involves build versus buy decisions. The Inputs, Tools and Techniques, and Outputs of Plan Procurement process are listed in the table below.Plan Procurement Management processInputsTools and TechniquesOutputs

Scope baselineMake-or-buy analysisProcurement management plan

Requirements documentationExpert judgmentProcurement statements of work

Teaming agreementsContract typesMake-or-buy decisions

Risk registerProcurement documents

Risk-related contract decisionsSource selection criteria

Activity resource requirementsChange requests

Project schedule

Activity cost estimates

Cost performance baseline



3. A contract is a formal agreement. It is a legal document biding to both seller and buyer. Changes to contract must be in writing and formally controlled. Most Governments back all contracts by providing a court system.4. The process of Conduct Procurement involves receiving seller responses, selecting a seller, and awarding a contract. During this process bids or proposals from sellers are evaluated, and one or more seller is selected to execute the work.Conduct Procurement processInputsTools and TechniquesOutputs

Project Management PlanBidder conferencesSelected sellers

Procurement documentsProposal evaluation techniquesProcurement contract award

Source Selection criteriaIndependent estimatesResource calendars

Qualified seller listExpert judgmentChange requests

Seller proposalsAdvertisingProject management plan updates

Project documentsInternet searchProject document updates

Make-or-buy decisionsProcurement negotiations

Teaming agreements


5. Sole Sourcerefers to a market condition in which only one qualified seller exists in the market.Single Sourcerefers to a market condition in which the company prefers to contract with only one seller.Oligopolyrefers to a market condition where very few sellers exist, and the action of one seller will have impact on other seller prizes.6. Bidder conferences are meetings between buyer and sellers before the bid is submitted. The conference is used by buyers to provide consistent information to all sellers.7. The process of Control Procurement involves managing procurement relationships and ensuring the seller performance meets the procurement requirements.Control Procurement processInputsTools and TechniquesOutputs

Procurement documentsContract change control systemProcurement documentation

Project management planProcurement performance reviewsOrganizational assets updates

ContractInspection and auditsChange requests

Performance reportsPerformance reportingProject management plan updates

Approved change requestsPayment systems

Work performance informationClaims administration

Records management system

8. Contract can be used as a risk management tool, as in transferring risk.9. Centralized Contractingrefers to a separate contracting office that handles contracts for all projects. InDe-centralized Contractinga contract administrator is assigned for each project.10. Force majeure is a powerful and unexpected event, such as hurricane or other disaster.11. Privity is contractual information between customer and vendor.12. The process of Close Procurement involves completing each procurement. The process involves verifying that all planned work as per the contract has been completed.Close Procurement processInputsTools and TechniquesOutputs

Project management planProcurement auditsClosed procurements

Procurement documentationNegotiated settlementsOrganizational process updates

Records management system

Project Stakeholder Management

Project stakeholder management is comprised of the processes required to identify the people, groups, and organizations that can impact or be impacted by the project. It involves analyzing stakeholder expectations in developing management strategies for effectively engaging stakeholders and project decisions and execution. Stakeholder management also focuses on continuous communications with stakeholders, managing conflict, and promoting appropriate stakeholder engagement in project decisions and activities.The following processes and primary goals of project stakeholder management are defined below: Identify Stakeholders. Goal: stakeholder register. Plan Stakeholder Management. Goal: stakeholder management plan. Manage Stakeholder Engagement. Goal: issue log, change requests. Control Stakeholder engagement. Goal: work performance information, change requests.The high level Project Stakeholder Management output elements, by Process Group, are:InitiatingPlanningExecutingMonitoring and ControllingClosing

Stakeholder registerStakeholder Management planStakeholder registerCR'sWork Performance InfoCR's

Project stakeholder management focuses on the processes required to identify the people, groups, or organizations that can either impact or be impacted by the project. Some of these processes include the following: Analyzing stakeholder expectations and their impact on the project. Developing appropriate management strategies for engaging stakeholders. Implementing continuous communications with stakeholders to understand needs and expectations. Fostering stakeholder engagement in the project for decisions and activities. Focusing on stakeholder satisfaction as a key project objective.Identify Stakeholders is the process of identifying all individuals or organizations that can be positively or negatively impacted by the project, and documenting their influence, impact, interest, and involvement on project success.This is a key area in the project management process, as many projects fail due to a lack of complete stakeholder identification. Most projects will have a large number of stakeholders, and it is a project manager's job to identify stakeholders and understand the impact of the project on their specific business areas. In this respect, the project manager's job amounts to a relationship management function.The key output of this process is to create a stakeholder register which identifies in great detail, everything about the stakeholders on the project.For further information on Project Stakeholder Management, consult EdWel'sPMP Textbook 5th Edition.As part of the Manage Stakeholder Expectations process, the project manager works with the stakeholders, understands and addresses their needs and expectations. The Inputs, Tools and Techniques, and Output of Manage Stakeholder Expectations process is given below.Manage Stakeholder Expectations ProcessInputsTools & TechniquesOutputs

Stakeholder registerCommunication methodsOrganizational process assets updates

Stakeholder management strategyInterpersonal skillsChange requests

Project management planManagement skillsProject management plan updates

Issue logProject document updates

Change log


Control stakeholders engagement process is a newly added process group. See PMBOK for details.

PMP Code of Professional Ethics

This chapter covers PMI's code of Professional Conduct. The PMP code of Professional Conduct is definedhere1. Culture Shockrefers to the initial disorientation that a person first experiences when visiting a country other than his own.2. Ethnocentrismis a typical belief that one's culture is superior to the foreigner's culture.3. PMP's Code of Professional Conductis a document provided by PMI. It is a guide to Project Managers on how to conduct as a professional.4. PMP aspirants need to provide accurate and truthful information through out the application process. Any violations can lead to disciplinary action.5. If a project team member or the project manager has a conflict of interest, then it must be brought into notice of all the stake-holders, to prevent any appearance of improperiety. As an example of this consider a case where a Project Manager is evaluating some vendors. Lets assume the Project Manager has friendship with one of the vendors. In such a situation, the Project Manager should let all the stakeholders know, and offer herself to be excluded out of the evaluation process.6. The confidentiality of any intellectual property information that a PMP professional works with, must be maintained.7. Any information that a PMP provides to general public must be accurate and truthful.8. A PMP must not accept any form of inappropriate gifts. Similarly a PMP must not offer inappropriate compensation for personal gains.

pmbok key concepts

Documents