PMP Certification Study Notes 1 – Terms and Concepts


PMP Terms and Concepts

Introduction: Essential terms from the PMBOK® Guide 5th Edition are highlighted here. PMP® aspirants need to learn these well in order to successful pass the PMP® exam. More information on my PMP® certification exam preparation can be found at my PMP® exam and certification journey here.

Important Terms and Concepts

  • Process – a package of inputs, tools and outputs, there are 47 processes defined by PMI
  • Phases – a group of related activities in a logical manner, produces one or more deliverables at the end of the phase (maybe with exit gate/kill point [probably in a sequential relationship])
  • Phase-to-Phase relationship: sequential -> finish-to-start; overlapping -> for schedule compression (fast tracking); parallel
  • Project – a temporary endeavor to create a unique product, service or result (or enhancement of existing services/products (e.g v.2 development is a project) ) as opposed to operation, may hand over the product to operation teams
  • Operation manages process in transforming resources into output
  • projects have more risks and uncertainties than operations and require more planning
  • Program – a group of coordinated projects, taking operations into account, maybe with common goals, achieving benefits not realized by running projects individually, if only the client/technologies/resource are the same, then the projects should be managed individually instead of a program
  • Portfolio – group of programs/projects to achieve organizational strategic goals within the organization/operation management, all investments of the organization, maximize the value by examining the components of the portfolio and exclude non-optimal components
  • Why projects: market demand, organizational need, customer request, technological advance, legal requirements, to support organization strategic plan -> projects bring values
  • Business Value is the total values (tangible and intangible) of the organization
  • Organization Strategy may be expressed through mission and vision
  • Use of portfolio/program/project management to bridge the gap between organization strategy and business value realization
  • Progressive Elaboration (rolling wave planning is one of the methods used in activity planning) – analysis and estimation can be more accurate and elaborated as the project goes (usually in phased projects) such that detailed planning can be made at that point

Project Management

  • Project Management – the application of (all appropriate) knowledge, skills, tools & techniques and whatsoever to manage project activities with a view to meet the project requirements and achieve customer satisfactions
  • The most important task is to align stakeholder expectations with the project requirements, around 90% of the PM’s work is related to communication with stakeholders
  • PMBOK® Guide is a framework/standard but not methodology (agile, scrum, PRINCE3, etc.)
  • should be aligned with organization governance (through EEF and OPA)
  • Competing constraints: time, cost, scope, quality, risk, resources
  • Project Management Office (PMO) – standardizes governance, provides training, shares tools, templates, resources, etc. across all projects/programs/portfolios
  • 3 forms: supportive, controlling and directing (lead the project as PM)
  • functions: training, resource coordination, methodology, document repository, project management oversight, standards, career management of PMs
  • may function as a stakeholder / key decision maker (e.g. to terminate the projects)
  • align portfolios/programs/projects with business objectives and measurement systems
  • control shared resources / interdependence across projects at the enterprise level
  • play a decisive role in project governance
  • Organizational Project Management (OPM)
    • strategy execution framework utilizing portfolios, programs and projects and organizational enabling practices (technology, culture, etc.) for achieving organizational objectives
    • linking management principles with strategy, advance capabilities
  • Management by Objectives (MBO) : define objectives for an organization so that management and employees can agree to the objectives and understand what they need to do in the organization in order to achieve them.
  • Organizational Project Management Maturity Model (OPM3) : givess a methodological approach for organizations to understand their Organizational Project Management processes and measure their capabilities for planning for improvement.

Project Manager

  • Project Manager: knowledge, performance, personal – general (organization, planning, meeting, control) management, interpersonal (communication, leadership, motivation, influence, negotiation, trust building, political and cultural awareness) skills
  • leader of the project irrespective of the authority
  • should consider every processes to determine if they are needed for individual projects
  • may report to the functional manager, program manager, PMO manager, operation manager, senior management, etc., maybe part-time or devoted
  • identifies and documents conflicts of project objectives with organization strategy as early as possible
  • skills: leadership, team building, motivation, influencing, coaching, trust building, communication, political awareness, cultural awareness, decision making, conflict management, negotiation
  • PM must balance the constraints and tradeoffs, effectively communicate the info (including bad news) to the sponsor for informed decisions
  • PM need to involve project team members in the planning process
  • Project Team includes PM, project management staff, project staff, PMO, SME (subject matter experts can be outsourced), customer representative (with authority), sellers, business partners, etc., maybe virtual or collocated
  • Senior management must be consulted for changes to high-level constraints

Organization Types

  • Organization Types: Projectized (project manager has the ultimate authority over the project, team members are often collocated), Matrix (Strong, Balanced, Week), Functional
  • Composite – a combination of different types, depending on the actual need
  • Tight Matrix = co-location, nothing to do with the organization type (not necessarily a matrix org.)
  • Functional organizations => the project manager has little authority, often called project expeditor (no authority) or coordinator  (little authority), project coordination among functional managers
  • Matrix organization => multiple bosses and more complex
  • Project Based Organization (PBO) – conduct the majority of activities in the form of projects and/or privilege project over functional approaches, they can include: departments with functional organizations; matrix organizations; projectized organizations and other forms of organizations that privilege a project approach for conducting their activities, success is measured by the final results rather than position/politics

Project Lifecycle vs Project Management Lifecycle vs Product Lifecycle

  • Project Lifecycle: includes: initiating, planning and organizing, carrying out/executing work, closing the project
  • Predictive [plan driven/waterfall] – scope, time and cost determined early in the lifecycle, may also employ rolling wave planning
  • Iterative [incremental] – repeat the phases as understanding of the project increases until the exit criteria are met, similar to the rolling wave planning, high-level objectives, either sequential / overlapping phases, scope/time/resources for each phase may be different
  • Adaptive [change driven/agile] – for projects with high levels of change, risk and/or uncertainty, each iterative is very short (2-4 weeks), work is decomposed into product backlog, each with a production-level product, scrum is one of the most effective agile methods, stakeholders are involved throughout the process, time and resources are fixed, allow low change cost/keep stakeholder influence high
  • each project phase within the product lifecycle may include all the five project management process groups
  • product lifecycle: development > production > adoption & growth > maturity > decline > end of life

Other Terms

  • Organization Process Assets is a major input in all planning process, which may be kept at PMO, directly related to project management, including Processess and Procedures (including templates (e.g. WBS, schedule network diagrams, etc.), procedures for issuing work authorizations, guidelines, performance measurements) and Corporate Knowledge Base
  • The Configuration Management Knowledge Bases contain baselines of all organization standards
  • Lessons Learned – focus on the deviances from plan (baseline) to actual results
  • Enterprise Environment Factors (often are constraints) are influences not under control of the project team that will affect the project, either intra-organization and extra-organization, e.g. organizational culture, organization structure (functional/matrix/projectized structure), existing human resources, work authorization system, PMIS
  • The work authorization system (WAS) is a system used during project integration management to make sure that the right work gets done at the right time
  • EEF are inputs for all initiating, most planning process, not much in the executing/controlling process, none in closing process
  • Organization culture: process-oriented/results-oriented, job-oriented/employee-oriented, professional-oriented/parochial-oriented, open system/closed system, tight control/loose control, pragmatic/normative
  • Project Governance – for the whole project lifecycle, fits in the organization’s governance model, define responsibilities and accountabilities, controlling the project and making decisions for success, alignment of project with stakeholders’ needs/objectives, provides a framework for PM and sponsors to make decisions to satisfy both parties, should be described in the PM plan
  • Analytical Techniques: used to find the root cause or to forecast
  • PMIS includes configuration system and change control system
  • Never accept a change request to trim down one element of the triple constraint without changing the rest.
  • Sponsor – provides resources/support to project, lead the process through initiation (charter/scope statement) through formally authorized, later involved in authorizing scope/budget change/review
  • Customer – NOT necessarily provide the financial resources, maybe external to the organization, final acceptance of the product
  • Business Partners – certification body, training, support, etc.
  • Organizational Groups – internal stakeholders
  • Business Case : background, analysis of the business situation, costs and benefits (cost-benefit analysis), to help in selection of project created by the initiator
  • Project Statement of Work (SOW) : describes the business need, high level scope of deliverables and strategic plan of the organization, created by the sponsor/initiator/buyer
  • Project Charter : formally authorizes the project, includes all those from above plus approval criteria, preliminary budget, primary stakeholders, the name of PM, assumptions and decisions etc., usually created by PM (in develop project charter process) and signed by the sponsor, remains fairly the same during project lifecycle, except big changes like sponsor has resigned [the current sponsor should initiate the change to the charter before he leaves]
  • Project Charter is not a contract
  • Project Management Plan: how the project will be performed and managed – documents assumptions & decisions, helps communication between stakeholders, goals, costs & time scheduling (milestones), project management system and subsidiary management plans and documents
  • Project Management Plan is NOT a project schedule
  • Project Management System: includes a list of project management processes, level of implementation (what actions to take in the management processes), description of tools and techniques, resources, procedures, change control system [forms with tracking systems, approval levels]
  • Requirement Traceability Matrix (RTM) – a matrix connecting deliverables to requirements and their sources (for managing scope)
  • Work Breakdown Structure (WBS) – a hierarchal chart of decomposing deliverables into work packages
  • Activity List – a full list of all activities with indication of relationship to the work packages
  • Activity Attributes – further information (duration, start date, end date, etc.) of all the activities in the list (for scheduling)
  • Roles and Responsibilities (RAR) – a document listing all the roles and description of their responsibilities in the project (often by category)
  • Responsibility Assignment Matrix (RAM) – a matrix connecting people to work packages/activities, e.g. the RACI matrix (responsible, accountable, consult, inform), usually only one person is accountable for each activity
  • Resources Breakdown Structure (RBS) – a hierarchical chart listing all the resources by categories, e.g. marketing, design, etc.
  • Risk Breakdown Structure (RBS) – a hierarchical chart listing all risks by categories
  • Project Information
    • Work Performance Data – raw data collected
    • Work Performance Info – analyzed in context and integrated data, e.g. some forecasts
    • Work Performance Reports – work performance information compiled in report format
  • Sunk costs – money already spent, not to be considered whether to terminate a project, similar to committed cost (often through contracts)
  • Direct costs, indirect (shared) costs, Fixed costs, Variable costs
  • Law of diminishing returns – beyond a point, the more input, the less return
  • Working capital – assets minus liability, what the company has to invest in the projects
  • Payback period – a time to earn back capital investment
  • Benefit-cost ratio (BCR) – an indicator, used in the formal discipline of cost-benefit analysis, that attempts to summarize the overall value for money of a project
  • Depreciation – straight-line depreciation vs accelerated depreciation (the amount of depreciation taken each year is higher during the earlier years of an asset’s life)
  • Under double declining balance, the asset is depreciated twice as fast as under straight line. Using the example above, 10% of the cost is depreciated each year using straight line. Doubling the rate would mean that 20% would be depreciated each year, so the asset would be fully depreciated in 5 years, rather than 10.
  • Under sum-of-the-years-digits, the asset is depreciated faster than straight line but not as fast as declining balance. As an example of how this method works, let’s say an asset’s useful life is 5 years. Adding up the digits would be 5+4+3+2+1 or a total of 15. The first year, 5/15 is expensed; the next year 4/15 is expensed, and so on. So if the asset’s cost is $1000, 5/15, or $333.34 would be expensed the first year, $266.67 the second year, and so on.
  • Economic value added – the value of the project brought minus the cost of project (including opportunity costs) e.g. for a project cost of $100, the estimated return for 1st year is $5, assuming the same money can be invested to gain 8% per year, then the EVA is $5 – $100 * 8% = -$3
  • Net present value (NPV) – the sum of the present values (PVs) of the individual cash flows of the same entity
  • Present value (PV) – or called present discounted value, is a future amount of money that has been discounted to reflect its current value, as if it existed today (i.e. with inflation, etc.)
  • Future value (FV) – is the value of an asset at a specific date
  • Internal Rate of Return (IRR) – The inherent discount rate or investment yield rate produced by the project’s deliverables over a pre-defined period of time.
  • Forecast (future) vs Status Report (current status) vs Progress Report (what have been done/delivered)
  • Journey to Abilene (Abilene’s Paradox) – committee decisions can have a paradox outcome, the joint decision is not welcome by either party (because of fear of raising objections)
  • when something unusual happens, always refer to the PM Plan/Charter for instruction on how to proceed; if not found, ask for direction from the management
  • unresolved issues will lead to conflicts

Further PMP® Study Resources

  • 46+ Commonly Confused PMP® Term Pairs with detailed explanations — there are many PMP® term pairs that look very similar but are quite different in meaning. The PMP® Exam questions may test Aspirants’ understanding of these terms and how to distinguish between them. The list of 46+ Commonly Confused terms will help Aspirants to distinguish between the term pairs with live examples and mock exam questions (if applicable).

 

 

Most Popular PMP Certification Exam Articles

GreyCampus PMP online training course bundle for US$149 only

Support website running for FREE, thanks!

If you find this post helpful and if you are thinking of buying from Amazon, please support the running cost of this website at no extra cost to you by searching and buying through the search box below. Thank you very much for your help!

Edward Chung

Edward Chung aspires to become a full-stack web developer and project manager. In the quest to become a more competent professional, Edward studied for and passed the PMP Certification, ITIL v3 Foundation Certification, PMI-ACP Certification and Zend PHP Certification. Edward shares his certification experience and resources here in the hope of helping others who are pursuing these certification exams to achieve exam success.

You may also like...

Leave a Reply

Your email address will not be published. Required fields are marked *

8 Responses

  1. sylvie says:

    Dear Edward,
    As I was studying for the PMP (started 3 months back), I discovered your website and I have to say that it is VERY good and useful and complete. It helped me greatly in my studies and learning. I read PMbok twice, Rita book twice (I recommend to do all the exercises as they really helped gain deep knowledge and understanding). I passed my PMP exam today, Proficient on all process groups… so happy!! the questions were 95% situational and it was a very dense focused 4-hour session; I did not have time to take a break. So thank you for the great website and all the information provided. I am thinking of doing other certification and your website is in my favorites!

  2. Aaron says:

    Hi Edward,

    I will sit for the PMP Exam in 13 days. I have read Rita twice, went through PMBOK once. I have done at least 2,000 practice test questions. I presently am scoring in 50 question lite exams from PMtraining.com in the 76%-90% range on each exam, with an average of 80%+ in total (paid exams). I did the PMstudy 200 question exam and scored a 76% and that was skipping about five questions regarding drawing network diagrams as I had no pen and paper with me while taking the exam. I scored a 77% on the Simplilearn free exam. I am nervous about the exam, as it seems many sites state on internet state one should be performing in the 80% plus range on mock exams regularly. Any thoughts on the matter?

    • Edward Chung says:

      Hi Aaron,

      Judged from your performance of the mock exams alone, I would say that you stand a high chance of passing the PMP Exam in your first try. Mock exams results in the range of 75-80% are already quite good indeed! Have you tried other mock exams listed here:
      https://edward-designer.com/web/list-of-free-pmp-exam-questions/

      Remember to be psychologically prepared for some more difficult questions at the beginning of the exam that may adversely affect your confidence. As you have already tried your best in your PMP preparation, have confidence in yourself!

      Wish you PMP success! Do let me know your success story!

  3. Kalander says:

    Hi Edward, so kind of you to share the notes to others. This is of great help to me and am sure its helpful for lots of others too.

  4. Das says:

    Hi Edward,

    would like to hilight that in your project charter statement it shows project charter signed by Sponsor, however as per PMBOK , project charter authorized by sponsor and commit to the project and signed done by Senior Management.

  5. Mark Campbell says:

    Hello Edward,

    I think this is great that you are offering these tips, notes and your perspective about the ITIL, PMP and Agile for the masses. I will continue to check your website. Great Job!

    Thank you,
    Mark

April 9, 2014