dc dotCreds
Reference guide

PMP Course Notes

Study PMP section notes, then jump straight into the guided course or related practice questions without losing your place.

Continue CourseStart PracticePDF downloads available in Pro.
Checking access

Checking Pro access...

Looking for your active Pro access before showing Course Notes. This usually takes just a moment.

Course Notes preview

Unlock Pro for the full per-exam reference guide.

Preview one piece from each section. Pro includes every Course Notes section, summary, key point, common mistake, exam tip, related-question review, and PDF export.

Includes full Course Mode and Course Notes.

Section 1Team PerformancePreview
More in this section
  • 2 more summary sections in Pro version
  • 11 more key points in Pro version
  • 4 more common mistakes in Pro version
  • 4 more exam tips in Pro version
  • 76 more related questions in Pro version

Summary

The exam tests the 'People' domain of the PMP exam, specifically addressing how to build and manage high-performing teams. Effective team performance isn't just about assigning tasks; it's about fostering collaboration, resolving conflict constructively, and empowering team members to take ownership.

Key Points

  • **Constructive Discussion Facilitation:** Knowing how to guide discussions when disagreements arise, ensuring all viewpoints are heard and refocusing on project goals is essential. This isn't about choosing a 'winner,' but finding a path forward.

Common Mistakes

  • **Coaching vs. Mentoring:** Coaching focuses on specific skills or behaviors, while mentoring is a broader developmental relationship. The exam will test your ability to differentiate when to use each approach.

Exam Tips

  • Read the scenario carefully and identify the underlying team dynamic issue before selecting an answer.
Section 2Process ManagementPreview
More in this section
  • 2 more summary sections in Pro version
  • 9 more key points in Pro version
  • 3 more common mistakes in Pro version
  • 4 more exam tips in Pro version
  • 58 more related questions in Pro version

Summary

The exam tests the 'Process' domain of the PMP exam, emphasizing how project managers proactively manage and adapt processes to deliver value. It's not just about following a plan; it's about understanding *why* processes exist, tailoring them to the project's unique context, and responding effectively to changes and challenges.

Key Points

  • **Business Value Prioritization:** Project work should always be aligned with and prioritized based on the business value it delivers. This means understanding the project's objectives and ensuring that tasks and deliverables contribute to those objectives.

Common Mistakes

  • Understand the difference between risk avoidance, transference, mitigation, and acceptance โ€“ and when each is appropriate.

Exam Tips

  • Always consider the business value when making decisions about prioritization or scope changes.
Section 3FoundationsPreview
More in this section
  • 2 more summary sections in Pro version
  • 7 more key points in Pro version
  • 4 more common mistakes in Pro version
  • 5 more exam tips in Pro version
  • 7 more related questions in Pro version

Summary

The exam tests the Business Environment domain, specifically how external factors like compliance, organizational change, and stakeholder engagement directly impact project success. Understanding these influences is critical because projects rarely exist in a vacuum; they are interwoven with organizational processes, regulatory requirements, and the need to deliver tangible business value.

Key Points

  • **Compliance Impact:** Regulatory and legal requirements are not just constraints; they are integral to project scope, delivery, and stakeholder expectations. Assess these impacts early and continuously throughout the project lifecycle.

Common Mistakes

  • Distinguish between *identifying* compliance requirements and *implementing* them. The exam often tests your ability to recognize the need for compliance and plan accordingly.

Exam Tips

  • Always consider the broader business context when analyzing scenarios. Don't get bogged down in technical details.