Project Management Professional (PMP) Process: Managing the Project Through Execution Syllabus

Process: Managing the Project Through Execution syllabus — full chapter and topic list

Expand any chapter to see its topics and sub-topics. This is the whole examinable outline for Process: Managing the Project Through Execution in Project Management Professional (PMP), not a summary of it.

1. 1

   Planning, Tailoring, and Governance

   4 topics

   • Determining the appropriate methodology and practices
     • Tailoring to project, team, and organization
   • Integrating planning activities across knowledge areas
   • Establishing project governance and decision authority
   • Managing assumptions, constraints, and dependencies
2. 2

   Executing and Delivering Value

   4 topics

   • Managing project work to deliver business value
     • Minimum viable product and incremental delivery
   • Managing changes throughout the project
     • Integrated change control and change control board
     • Configuration management
   • Managing project artifacts and information
   • Establishing project knowledge transfer
3. 3

   Monitoring, Controlling, and Issue Management

   4 topics

   • Measuring project performance against the plan
     • Variance analysis and trend analysis
     • Key performance indicators and acceptance criteria
   • Managing issues with the issue log
   • Determining and applying corrective and preventive actions
   • Managing project compliance and audits
4. 4

   Project and Phase Closure

   4 topics

   • Closing the project or phase
     • Final deliverable acceptance and handover
     • Administrative and contract closure
   • Capturing lessons learned and updating OPAs
   • Confirming benefits realization and transition to operations
   • Releasing resources and celebrating success

Process: Managing the Project Through Execution flashcards for Project Management Professional (PMP)

22 of 50 cards from the Process: Managing the Project Through Execution deck — real questions with worked answers.

1. What three primary categories of project life cycle / development approaches does the PMBOK recognize, and how do they differ?

   Predictive (plan-driven, fully scoped upfront, e.g. waterfall), Adaptive (agile/iterative/incremental, scope evolves), and Hybrid (a combination of predictive and adaptive). Choice depends on uncertainty, rate of change, and stakeholder involvement.

2. When choosing a delivery methodology, which factors push a project toward an adaptive (agile) approach rather than predictive?

   High requirements uncertainty/volatility, rapid change, frequent customer feedback, need for early/incremental value delivery, and ability to deliver in small increments. Stable, well-understood requirements favor predictive.

3. What is a 'tailoring' decision in project management, and why is it necessary?

   Tailoring is deliberately selecting and adapting processes, inputs, tools, methods, and life cycles to fit the specific project, organization, and environment. It is necessary because no single approach fits all projects; it optimizes value while meeting governance needs.

4. What is integration management's central purpose during execution?

   To unify, consolidate, communicate, and coordinate the various processes and project activities across all knowledge areas so they work together coherently to meet objectives and deliver value.

5. What is the Direct and Manage Project Work process, and what key output does it produce?

   It is the integration process of leading and performing the work defined in the project management plan and implementing approved changes. Key outputs include deliverables, work performance data, issue log updates, and change requests.

6. Define 'project governance' and name what it provides to a project.

   Project governance is the framework, functions, and processes that guide project management activities to create a unique product/service. It provides decision-making authority, oversight, control, accountability, and alignment of the project with organizational strategy.

7. What is a RACI chart and what do its four letters stand for?

   A RACI chart is a responsibility assignment matrix (RAM) clarifying roles: Responsible (does the work), Accountable (ultimately answerable, one person), Consulted (provides input, two-way), and Informed (kept up to date, one-way).

8. Differentiate an assumption from a constraint in project planning.

   An assumption is a factor considered true, real, or certain without proof, used for planning (carries risk if wrong). A constraint is a limiting factor that restricts options (e.g., fixed budget, deadline, regulation, resources).

9. What are the three classic constraints of the 'triple constraint' (iron triangle)?

   Scope, Schedule (time), and Cost (budget) — with quality often at the center. Changing one typically affects the others.

10. What is a dependency in scheduling, and name the four logical dependency types.

    A dependency is a logical relationship between activities. The four types are Mandatory (hard logic), Discretionary (preferred/soft logic), External (outside the project), and Internal (within the project/team control).

11. Define the four precedence relationship types used in the Precedence Diagramming Method (PDM).

    Finish-to-Start (FS), Finish-to-Finish (FF), Start-to-Start (SS), and Start-to-Finish (SF). FS is the most commonly used; SF is the rarest.

12. What does 'managing the project to deliver business value' emphasize over simply completing scope?

    It emphasizes delivering measurable benefits and outcomes aligned with the business case—prioritizing the highest-value work, delivering value incrementally, and ensuring the project remains aligned with strategic objectives, not just outputs.

13. What is the difference between an output, an outcome, and a benefit?

    An output is a deliverable produced (the 'what'). An outcome is the change resulting from using the output. A benefit is the measurable improvement/value (often financial or strategic) realized from the outcome.

14. What is the Perform Integrated Change Control process?

    The integration process of reviewing all change requests; approving, deferring, or rejecting changes; managing changes to deliverables, documents, and the project plan; and communicating decisions—ensuring changes are evaluated holistically before implementation.

15. What is a Change Control Board (CCB) and what is its role?

    A formally chartered group responsible for reviewing, evaluating, approving, deferring, or rejecting change requests and recording/communicating those decisions. It provides controlled, documented authority over changes.

16. List the four common categories of change requests.

    Corrective action (realigns performance to the plan), Preventive action (ensures future performance aligns), Defect repair (fixes a nonconforming component), and Updates (to plan documents/baselines).

17. What is 'scope creep' and how does change control prevent it?

    Scope creep is the uncontrolled expansion of scope without adjustments to time, cost, and resources. Formal integrated change control prevents it by requiring all changes to be documented, evaluated, and approved before implementation.

18. What is a configuration management system versus a change control system?

    Configuration management focuses on the specification of deliverables/products and processes (identifying and controlling product characteristics). Change control focuses on identifying, documenting, and controlling changes to the project baselines. They work together.

19. What are 'project artifacts' and give examples managed during execution.

    Project artifacts are documents or templates produced/used during the project. Examples: project charter, plans, logs (issue/risk/assumption), registers (stakeholder/risk), baselines, reports, agreements, and lessons learned register.

20. What does effective project information management (data governance) require?

    Proper collection, storage, distribution, retrieval, version control, security/access control, and archiving of project information so the right stakeholders get accurate, timely information.

21. What is the difference between explicit knowledge and tacit knowledge?

    Explicit knowledge is readily codified using words, numbers, and pictures (documents, databases). Tacit knowledge is personal, experience-based, and hard to express (beliefs, insights, know-how).

22. What is the Manage Project Knowledge process and its key output?

    The process of using existing knowledge and creating new knowledge to achieve objectives and contribute to organizational learning. Its key output is the Lessons Learned Register.

See more Process: Managing the Project Through Execution flashcards →

Planning Process: Managing the Project Through Execution for Project Management Professional (PMP)

Process: Managing the Project Through Execution (Project Management Professional (PMP)) FAQ