CAPM Exam Prep 2026: 23 Contact Hours | PMBOK Guide

Clarify the product versus project distinction, define how objectives, constraints, and stakeholders drive deliverables, and outline product and project life cycles, scope management, and success criteria.

Explore how business analysis bridges strategy and delivery across portfolio, program, and project management, aligning initiatives, managing requirements, risks, and stakeholder engagement to realize value.

Master stakeholder engagement by identifying and analyzing internal, external, and hidden stakeholders; apply power and interest analysis, create a tailored engagement plan, and monitor communication to maximize project value.

Explore domain 5 traceability and monitoring, linking requirements through forward, backward, and bidirectional traceability, and monitor progress with RTM, KPIs, verification, validation, and change control to deliver business value.

Solution evaluation measures performance and validates that the final solution delivers business value. It uses gap analysis, verification, validation, benefit realization, and continuous improvement to guide stakeholders.

Discover why agile exists, when to use it, and how it differs from traditional project management, including the agile lifecycle, values, principles, and key roles.

Compare predictive and adaptive project life cycles, detailing traditional (waterfall) and agile approaches, when to apply each, and how hybrid models tailor methods for Capm success.

Explore agile values, principles, and mindset, including individuals and interactions, working software, customer collaboration, and responding to change, early delivery, and stakeholder engagement for value-driven projects.

Explore agile team structure and roles that drive cross-functional, self-organizing collaboration, empower stakeholder engagement, and deliver value through ceremonies led by the scrum master, product owner, and development team.

Scrum distributes value creation across three roles: the product owner defines the vision and prioritizes the backlog, the scrum master guides the process, and the development team self-organizes to deliver.

Learn how scrum events establish sprint rhythm, including sprint planning with product owner priorities and capacity, and the daily scrum for team alignment, all under timeboxing and ongoing backlog refinement.

Visualize the workflow with a Kanban board, limit work in progress, and manage flow for a smoother process. Use cycle time and lead time metrics to guide improvement.

Verify and validate project value by ensuring outputs meet requirements and deliver real benefits, linking quality, scope, stakeholder engagement, and benefits realization to strategic goals.

Learn value-driven decomposition techniques to align projects with stakeholder needs, apply the work breakdown structure, decompose requirements, and plan schedules and risks for measurable value.

Learn how agile estimation uses teamwork, conversation, and relative sizing with story points and planning poker to forecast delivery and guide planning, contrasting with traditional predictive approaches.

Explore agile estimation units such as story points and ideal days. Understand their relative sizing, velocity, and how they link to earned value management for CAPM-aligned forecasting.

Master structured estimation with planning poker, a four-step agile method using a Fibonacci-based deck to reach consensus, reduce anchoring bias, and connect to the Delphi technique for CAPM learners.

Explore quick lightweight estimation techniques like t-shirt sizing, affinity estimation, dot voting, and relative mass estimation for early backlog planning, linking to capm concepts and rom estimates.

Learn how estimation techniques connect to agile velocity as a forecasting tool, defining velocity, stabilizing it, and using it with earned value management (EVM) to forecast project completion.

Link estimation to agile and traditional planning, showing how sprint commitments and release forecasts derive from velocity, story points, and expert judgment, anchored in CAPM standards and WBS.

Distinguish risks from issues in agile projects and apply proactive, transparent risk management embedded in the product backlog through collaboration, kanban boards, and sprint reviews.

Explore risk identification and assessment in agile, linking estimation to prioritizing risks with techniques like risk-based spikes, risk-adjusted backlog, and risk burndown chart to reduce exposure.

Embed risk tasks in the backlog and use agile boards to track issues, aligning estimation with risk responses and assigning owners for timely resolution.

Agile reflection reveals hidden and recurring risks, linking retrospectives to continuous risk review, risk register, and lessons learned, strengthening organizational process assets and risk preparedness.

Foster a culture of reflection as an agile mindset grounded in psychological safety, openness, and constructive feedback, guided by scrum masters to capture lessons learned and organizational process assets.

Reflect on lessons learned to build OPAs, linking agile reflection with CAPM concepts and formal and informal insights.

Explore the foundations of agile in software projects and focus on estimation through sprints and user stories. Compare with waterfall, emphasize progressive elaboration, sustainable pace, and delivery with customer feedback.

Explore how scrum, kanban, and extreme programming use estimation—story points and planning poker—to forecast scope, schedule, and delivery, and scale these practices with pi planning and integration management.

Discover how estimation ties scope management and quality in agile by embedding test driven development and continuous integration and delivery, with automated testing.