Domain
A high-level knowledge area tested on the PMP exam.
Getting Started: PMP Exam Essentials
Free knowledge base
Everything from the course in one searchable place: 182 entries. Use it to review before a practice test or look up a word you forgot.
182 results
A high-level knowledge area tested on the PMP exam.
Getting Started: PMP Exam Essentials
Specific responsibilities within a domain that a PM performs.
Getting Started: PMP Exam Essentials
Examples of the work associated with a task.
Getting Started: PMP Exam Essentials
Exam Content Outline, the blueprint for the PMP exam.
Getting Started: PMP Exam Essentials
Method used to determine the passing score for the exam.
Getting Started: PMP Exam Essentials
A question type requiring selection of multiple correct answers.
Getting Started: PMP Exam Essentials
Combines elements of both agile and predictive approaches.
Getting Started: PMP Exam Essentials
To remember the PMP domains, think 'PPP': People, Process, and Profit (Business Environment).
Getting Started: PMP Exam Essentials
Memorize the three PMP exam domains: People, Process, and Business Environment. Know their approximate percentage weightings (People 42%, Process 50%, Business Environment 8%) as these are frequently referenced.
Getting Started: PMP Exam Essentials
Not reviewing the latest PMP Exam Content Outline (ECO) and studying outdated material.
Getting Started: PMP Exam Essentials
Underestimating the importance of agile and hybrid methodologies, as the exam has a significant focus on them.
Getting Started: PMP Exam Essentials
Failing to practice different question types, leading to surprise and time management issues during the actual exam.
Getting Started: PMP Exam Essentials
Specific requirements, education and experience, to qualify for PMP.
Getting Started: PMP Exam Essentials
Formal project management education hours required for eligibility.
Getting Started: PMP Exam Essentials
Random verification process for PMP application details.
Getting Started: PMP Exam Essentials
Units earned to maintain PMP certification every three years.
Getting Started: PMP Exam Essentials
PMI's online system for tracking and reporting PDUs.
Getting Started: PMP Exam Essentials
Five phases of a project lifecycle used to describe experience.
Getting Started: PMP Exam Essentials
Project experience that does not count concurrently for multiple projects.
Getting Started: PMP Exam Essentials
To remember the PMP eligibility criteria, think: '35 Hours, then Experience!' (35 contact hours, then either 36 or 60 months of experience).
Getting Started: PMP Exam Essentials
The PMP exam content outline emphasizes the importance of understanding the application process, as it directly relates to the professional standards PMI upholds. Keywords to spot in questions might include 'eligibility,' 'audit,' 'PDU,' or 'certification renewal.' Memorize the two main eligibility paths (degree vs. no degree) and their corresponding experience requirements (36 vs. 60 months).
Getting Started: PMP Exam Essentials
Underestimating the detail required for project experience descriptions, leading to rejection.
Getting Started: PMP Exam Essentials
Not preparing for a potential audit by having documentation readily available.
Getting Started: PMP Exam Essentials
Failing to track PDUs after certification, resulting in loss of credential.
Getting Started: PMP Exam Essentials
Techniques used to address disagreements within a team.
People: Leading Project Teams and Stakeholders
Imposing a solution; win-lose approach, often by authority.
People: Leading Project Teams and Stakeholders
Working together to find a mutually beneficial solution; win-win.
People: Leading Project Teams and Stakeholders
Finding a middle ground where both parties give up something.
People: Leading Project Teams and Stakeholders
Avoiding or postponing the conflict; lose-lose approach.
People: Leading Project Teams and Stakeholders
De-emphasizing differences and focusing on areas of agreement.
People: Leading Project Teams and Stakeholders
Adapting leadership style based on team's needs and situation.
People: Leading Project Teams and Stakeholders
Environment where team members feel safe to take risks and speak up.
People: Leading Project Teams and Stakeholders
To remember conflict resolution techniques: 'Can We Solve Conflicts Effectively?' (Collaborate, Withdraw, Smooth, Compromise, Force).
People: Leading Project Teams and Stakeholders
The PMP exam often presents scenarios where you must choose the BEST conflict resolution technique. Look for keywords indicating urgency, importance of relationship, or desire for a lasting solution. Collaboration is generally preferred, but other techniques are appropriate in specific contexts. Memorize the 5 conflict resolution techniques and when to use each.
People: Leading Project Teams and Stakeholders
Always using the same conflict resolution technique, regardless of the situation.
People: Leading Project Teams and Stakeholders
Ignoring conflict, hoping it will resolve itself, which often escalates issues.
People: Leading Project Teams and Stakeholders
Adopting a rigid leadership style instead of adapting to team maturity and project needs.
People: Leading Project Teams and Stakeholders
Giving team members authority to make decisions.
People: Leading Project Teams and Stakeholders
Identifying differences between required and current skills.
People: Leading Project Teams and Stakeholders
Discussion to reach an agreement, often involving compromise.
People: Leading Project Teams and Stakeholders
Best Alternative To a Negotiated Agreement.
People: Leading Project Teams and Stakeholders
A negotiation result where all parties feel satisfied.
People: Leading Project Teams and Stakeholders
Fully concentrating on what is being said, not just hearing.
People: Leading Project Teams and Stakeholders
Underlying needs and concerns of stakeholders.
People: Leading Project Teams and Stakeholders
To 'TRAIN' your team and 'NEGOTIATE' effectively, remember: T-rust, R-esources, A-uthority, I-nterests, N-eeds. Then N-o-lose, E-xplore, G-ain-gain, O-ptions, T-alk, I-ntegrity, A-greement, T-ime, E-xecute!
People: Leading Project Teams and Stakeholders
The exam emphasizes understanding stakeholder interests over positions in negotiation. For training, recognize that continuous learning and development are key to team performance and project success.
People: Leading Project Teams and Stakeholders
Failing to identify and address team training needs early, leading to project delays or quality issues.
People: Leading Project Teams and Stakeholders
Micromanaging empowered teams, which undermines trust and reduces initiative.
People: Leading Project Teams and Stakeholders
Entering negotiations without understanding your own or the other party's underlying interests, leading to suboptimal outcomes.
People: Leading Project Teams and Stakeholders
Common interpretation of project elements by stakeholders.
People: Leading Project Teams and Stakeholders
Geographically dispersed team relying on technology for collaboration.
People: Leading Project Teams and Stakeholders
Agreed-upon rules for how and when to communicate.
People: Leading Project Teams and Stakeholders
Online tools for shared work, documents, and task management.
People: Leading Project Teams and Stakeholders
Standardized terminology used across a project.
People: Leading Project Teams and Stakeholders
Document authorizing a project and outlining its objectives.
People: Leading Project Teams and Stakeholders
Diagrams, charts, or images to convey information.
People: Leading Project Teams and Stakeholders
To ensure 'Shared Understanding,' remember 'V.C.C.D.I.': Vision, Communicate, Clarify, Confirm, Document, Iterate.
People: Leading Project Teams and Stakeholders
The PMP exam emphasizes the project manager's role in creating a collaborative project environment. Look for questions about communication strategies, conflict prevention, and stakeholder engagement, particularly in diverse or distributed teams.
People: Leading Project Teams and Stakeholders
Assuming everyone understands just because you've said it once.
People: Leading Project Teams and Stakeholders
Neglecting informal communication channels for virtual teams.
People: Leading Project Teams and Stakeholders
Not using visual aids to explain complex concepts.
People: Leading Project Teams and Stakeholders
Guidance from an experienced person to a less experienced one.
People: Leading Project Teams and Stakeholders
Agreed-upon behaviors and expectations for team interaction.
People: Leading Project Teams and Stakeholders
Ability to understand and manage emotions in self and others.
People: Leading Project Teams and Stakeholders
Recognizing one's own emotions, strengths, and weaknesses.
People: Leading Project Teams and Stakeholders
Understanding and sharing the feelings of another.
People: Leading Project Teams and Stakeholders
Controlling one's impulses and adapting to change.
People: Leading Project Teams and Stakeholders
Managing relationships and building networks effectively.
People: Leading Project Teams and Stakeholders
To remember the components of EQ, think of 'SMES': Self-Awareness, Motivation, Empathy, and Social Skills. (Self-Regulation is often grouped with Self-Awareness or as a separate 'S').
People: Leading Project Teams and Stakeholders
The PMP exam often tests your ability to apply these concepts in scenario-based questions. Look for keywords like 'fostering growth,' 'establishing expectations,' 'resolving interpersonal issues,' or 'understanding team dynamics' to identify questions related to mentoring, ground rules, and emotional intelligence. Remember that EQ is crucial for effective leadership.
People: Leading Project Teams and Stakeholders
Failing to involve the team in creating ground rules, leading to lack of ownership.
People: Leading Project Teams and Stakeholders
Ignoring violations of ground rules, which undermines their effectiveness and team trust.
People: Leading Project Teams and Stakeholders
Assuming emotional intelligence is an innate trait rather than a skill that can be developed and improved.
People: Leading Project Teams and Stakeholders
Sequential approach with upfront planning.
Process: Project Execution and Control
Iterative approach with flexible planning.
Process: Project Execution and Control
Uncontrolled expansion of project scope.
Process: Project Execution and Control
Hierarchical decomposition of project work.
Process: Project Execution and Control
Approved time-phased project budget.
Process: Project Execution and Control
Method to measure project performance.
Process: Project Execution and Control
Estimating using historical data from similar projects.
Process: Project Execution and Control
Estimating using statistical relationships.
Process: Project Execution and Control
To remember the core of scope and budget: 'S.C.O.P.E. = See Clearly, Outline Precisely, Estimate Costs.'
Process: Project Execution and Control
The PMP exam frequently tests your understanding of the differences between predictive and adaptive lifecycle approaches. Keywords to spot include 'stable requirements' for predictive and 'high uncertainty' or 'evolving requirements' for adaptive. Also, remember that the Work Breakdown Structure (WBS) is a key output of the Plan Scope Management process and is fundamental for defining project scope.
Process: Project Execution and Control
Failing to get formal sign-off on project scope, leading to disputes later.
Process: Project Execution and Control
Not establishing a robust change control process, allowing scope creep to derail the project.
Process: Project Execution and Control
Underestimating costs due to insufficient research or ignoring contingency reserves.
Process: Project Execution and Control
Determines the longest sequence of activities.
Process: Project Execution and Control
Measures scheduling efficiency (Earned Value / Planned Value).
Process: Project Execution and Control
Auditing quality requirements and results.
Process: Project Execution and Control
Monitoring specific results against standards.
Process: Project Execution and Control
Buyer pays a fixed amount; seller bears most risk.
Process: Project Execution and Control
Buyer pays costs plus a fee; buyer bears most risk.
Process: Project Execution and Control
Hybrid contract for hourly rates and material costs.
Process: Project Execution and Control
Details work to be performed by external vendor.
Process: Project Execution and Control
SQP: 'Schedule Quickly, Quality Perfectly, Procure Smartly!' – a reminder of the three key areas.
Process: Project Execution and Control
The PMP exam frequently tests your ability to select the appropriate contract type for a given scenario. Pay close attention to keywords indicating scope clarity, risk tolerance, and desired incentives. Remember that Fixed-Price contracts are for well-defined scopes, while Cost-Reimbursable contracts suit less defined scopes.
Process: Project Execution and Control
Failing to establish a clear quality baseline early in the project, leading to scope creep and rework.
Process: Project Execution and Control
Choosing a Fixed-Price contract for a project with a highly uncertain scope, transferring too much risk to the buyer or leading to change order disputes.
Process: Project Execution and Control
Not actively monitoring and controlling the schedule, only reacting to delays rather than preventing them.
Process: Project Execution and Control
Document listing identified risks, analysis, and responses.
Process: Project Execution and Control
The degree of uncertainty an entity is willing to accept.
Process: Project Execution and Control
Budget or schedule allocated for known-unknown risks.
Process: Project Execution and Control
Budget held for unknown-unknown risks.
Process: Project Execution and Control
Group responsible for reviewing and approving changes.
Process: Project Execution and Control
Document outlining how project information will be shared.
Process: Project Execution and Control
Involving individuals who can affect or be affected by the project.
Process: Project Execution and Control
Original approved plan for scope, schedule, or cost.
Process: Project Execution and Control
For risk responses, remember 'ATM-E' for Threats: Avoid, Transfer, Mitigate, Escalate. And 'EES-A' for Opportunities: Exploit, Enhance, Share, Accept. Just add 'Accept' to both!
Process: Project Execution and Control
The PMP exam emphasizes that all changes to project baselines (scope, schedule, cost) must go through a formal change control process, typically involving a Change Control Board (CCB). Look for questions testing your understanding of when and how to engage the CCB.
Process: Project Execution and Control
Ignoring small changes: Even minor changes can accumulate into significant scope creep if not managed through a formal process.
Process: Project Execution and Control
Failing to communicate negative risks: Hiding potential problems from stakeholders can erode trust and lead to bigger issues later.
Process: Project Execution and Control
Not updating baselines after approved changes: If baselines aren't updated, the project will be measured against an outdated plan.
Process: Project Execution and Control
Formal completion of all project activities.
Process: Project Execution and Control
Framework guiding project decision-making and alignment.
Process: Project Execution and Control
Ongoing effort to enhance processes and performance.
Process: Project Execution and Control
Knowledge gained from project experiences.
Process: Project Execution and Control
Sharing project insights across the organization.
Process: Project Execution and Control
Plans, processes, procedures, and knowledge base.
Process: Project Execution and Control
Formal sign-off by the customer or sponsor.
Process: Project Execution and Control
To remember Project Closure steps: 'C-L-O-S-E': Confirm deliverables, Lessons learned, Obtain acceptance, Settle contracts, End resources.
Process: Project Execution and Control
The PMP exam emphasizes that project closure is not merely ending tasks, but a formal process involving administrative and contractual closure, and updating organizational process assets. Look for questions about final deliverable acceptance and lessons learned documentation.
Process: Project Execution and Control
Failing to get formal sign-off for project completion, leading to scope creep or disputes post-closure.
Process: Project Execution and Control
Neglecting to document lessons learned, resulting in the same mistakes being repeated on future projects.
Process: Project Execution and Control
Not properly closing out contracts or financial accounts, which can lead to legal or financial liabilities.
Process: Project Execution and Control
Anything blocking a team's progress.
Process: Project Execution and Control
An ordered list of all project work.
Process: Project Execution and Control
Adding detail, estimates, and order to backlog items.
Process: Project Execution and Control
Tangible outputs created during a project.
Process: Project Execution and Control
Managing changes to documents over time.
Process: Project Execution and Control
Raising an issue to a higher authority.
Process: Project Execution and Control
A short, simple description of a feature.
Process: Project Execution and Control
To remember the key aspects of managing impediments, backlog, and artifacts, think: 'I B A C K': **I**mpediments resolved, **B**acklog refined, **A**rtifacts controlled, **C**ommunication clear, **K**nowledge shared.
Process: Project Execution and Control
The exam often tests your understanding of the PM's role in agile environments, particularly in removing impediments and facilitating backlog refinement. Look for keywords like 'servant leadership' and 'empowering the team.' Remember that the Product Owner owns the Product Backlog, but the PM facilitates its management.
Process: Project Execution and Control
Ignoring minor impediments, allowing them to snowball into major blockers.
Process: Project Execution and Control
Failing to regularly refine the backlog, leading to unclear or outdated work items.
Process: Project Execution and Control
Not establishing a clear system for artifact management, resulting in lost or outdated documents.
Process: Project Execution and Control
Adherence to laws, regulations, standards, and policies.
Business Environment: Strategic Project Alignment
General Data Protection Regulation; EU data privacy law.
Business Environment: Strategic Project Alignment
Ensuring project outputs deliver intended value and outcomes.
Business Environment: Strategic Project Alignment
Tangible result or deliverable produced by the project.
Business Environment: Strategic Project Alignment
Change in behavior or state resulting from using an output.
Business Environment: Strategic Project Alignment
Measurable improvement or value derived from an outcome.
Business Environment: Strategic Project Alignment
Adherence to rules set by specific regulatory bodies.
Business Environment: Strategic Project Alignment
Adherence to national and international laws.
Business Environment: Strategic Project Alignment
Compliance is like a 'COMPASS' – it guides your project in the right direction, avoiding legal storms and ensuring you reach your destination (benefits).
Business Environment: Strategic Project Alignment
The PMP exam frequently tests your understanding of the difference between outputs, outcomes, and benefits. Memorize that outputs are what the project creates, outcomes are the results of using those outputs, and benefits are the value derived from those outcomes, aligning with strategic goals.
Business Environment: Strategic Project Alignment
Treating compliance as an afterthought rather than integrating it from project inception.
Business Environment: Strategic Project Alignment
Confusing project outputs (what's delivered) with project benefits (the value derived).
Business Environment: Strategic Project Alignment
Failing to assign a 'benefits owner' to track and ensure benefits are actually realized post-project.
Business Environment: Strategic Project Alignment
Factors outside a project/organization influencing its success.
Business Environment: Strategic Project Alignment
Systematic monitoring of external factors for potential impact.
Business Environment: Strategic Project Alignment
Framework for analyzing Political, Economic, Social, Technological, Legal, Environmental factors.
Business Environment: Strategic Project Alignment
Assessing the potential effects of a change on project objectives.
Business Environment: Strategic Project Alignment
Flexible planning approach allowing for frequent adjustments.
Business Environment: Strategic Project Alignment
Mechanisms for continuous information exchange and adjustment.
Business Environment: Strategic Project Alignment
Ensuring project goals support organizational objectives.
Business Environment: Strategic Project Alignment
To remember key external factors, think of PESTLE: Political, Economic, Social, Technological, Legal, Environmental. It's a 'PEST' if you don't 'LE'arn it!
Business Environment: Strategic Project Alignment
The PMP exam often tests your ability to identify external factors and propose appropriate responses. Keywords like 'regulatory changes,' 'market shifts,' 'technological advancements,' and 'economic downturns' should trigger thoughts about environmental scanning and adaptive planning.
Business Environment: Strategic Project Alignment
Ignoring external signals: Failing to continuously monitor the environment and assuming project conditions will remain static.
Business Environment: Strategic Project Alignment
Delaying response: Waiting too long to address identified changes, leading to more costly and difficult adjustments.
Business Environment: Strategic Project Alignment
Lack of stakeholder communication: Failing to inform and involve stakeholders in understanding and adapting to external changes.
Business Environment: Strategic Project Alignment
Processes to help people adopt new ways of working.
Business Environment: Strategic Project Alignment
Individual who champions and facilitates change.
Business Environment: Strategic Project Alignment
Opposition or reluctance to adopt new processes.
Business Environment: Strategic Project Alignment
Active support from leadership for a change initiative.
Business Environment: Strategic Project Alignment
Details how to move from current to future state.
Business Environment: Strategic Project Alignment
To remember the PM's role in Change: C.A.R.E. - Communicate, Advocate, Resolve resistance, Empathize.
Business Environment: Strategic Project Alignment
The PMP exam frequently presents scenarios where a project delivers a technical solution, but the organization struggles to adopt it. Look for keywords like 'user adoption,' 'resistance,' 'training,' 'communication,' and 'sponsorship' as indicators that organizational change management principles are being tested. The exam expects you to understand that project managers play a key role in facilitating this adoption, not just delivering the technical output.
Business Environment: Strategic Project Alignment
Assuming technical delivery alone guarantees successful change adoption.
Business Environment: Strategic Project Alignment
Underestimating the time and resources needed for effective change management activities.
Business Environment: Strategic Project Alignment
Failing to engage key stakeholders and executive sponsors early in the change process.
Business Environment: Strategic Project Alignment
Benefits a project delivers relative to its costs.
Business Environment: Strategic Project Alignment
Document justifying a project, including value.
Business Environment: Strategic Project Alignment
Financial metric: project's profitability over time.
Business Environment: Strategic Project Alignment
Financial metric: ratio of profit to investment.
Business Environment: Strategic Project Alignment
Time to recover project investment costs.
Business Environment: Strategic Project Alignment
Centralized management of projects/programs.
Business Environment: Strategic Project Alignment
Think 'VALUE' when evaluating projects: Vision (strategic fit), Assets (resource utilization), Logic (business case), Understanding (stakeholder support), and Earnings (financial returns).
Business Environment: Strategic Project Alignment
The PMP exam often presents scenarios where you must choose the best project to support a strategic objective. Look for keywords like 'organizational goals,' 'strategic objectives,' 'business value,' and 'prioritization.' Remember that projects are tools for strategy execution.
Business Environment: Strategic Project Alignment
Focusing solely on financial metrics without considering qualitative benefits or strategic fit.
Business Environment: Strategic Project Alignment
Starting projects without a clear, documented link to organizational strategy.
Business Environment: Strategic Project Alignment
Failing to re-evaluate project alignment as organizational strategies or external conditions change.
Business Environment: Strategic Project Alignment