PMI-ACP Exam Prep 28 PDUs/Contact Hours Course 2025 Updated

Explore the PMI-ACP basics section as a foundational primer that defines project, program, and portfolio management, and clarifies what is not covered on the exam while outlining essential concepts.

A project is a temporary, start-to-end endeavour that yields a unique product, service, or result, evolving through progressive elaboration and potentially forming part of a program or portfolio.

Project management applies knowledge, skills, tools and techniques to satisfy project requirements, guiding scope, budget, schedule, risks and changes while leading the project team from start to close.

Define how program management coordinates related projects to deliver benefits and control, then illustrate breaking large projects into subprojects with dedicated project managers to handle interdependencies.

Define a portfolio as a collection of projects, programs, and operations managed together to achieve strategic objectives, with portfolio managers aligning goals with senior leadership to select initiatives.

Explore how operations management drives the ongoing production of goods and services by acquiring, developing, and utilizing resources, contrasted with projects that have a start and end date.

Identify a project's value to secure approval by showing expected returns, such as higher revenue, lower costs, better brand reputation, or new or improved products.

Projects enable changes by moving an organization from its current state to a desired state, such as upgrading products or boosting revenue. Change is essential; without it, companies risk obsolescence.

Explore how phases group related activities to produce deliverables, the unique outputs of a project life cycle. Deliverables are accepted by customers or sponsors and may be tangible or intangible.

Explore the project lifecycle from start to finish, detailing phases such as initiation, design, development, and closure, and compare predictive, agile, and hybrid life cycles led by the project manager.

Establish project governance as the framework for making project decisions, guiding initiation, termination, and funding. Rely on structure, people, and information, and adapt uniquely to every organization.

Stakeholders are individuals, groups, or organizations affected by a project. They can be positively or negatively impacted and include the project manager, customer, project team, sponsor, and functional manager.

Identify and adapt to multiple roles on a project, from initiator and negotiator to coach and facilitator, guiding meetings and team members throughout the project.

Define milestones and task duration in project management; identify significant events like a permit or passing a test, and note that zero duration tasks are milestones in scheduling tools.

Explore organizational structures from functional to project-oriented to matrix, including weak and strong matrices and hybrids, and learn how structure determines a project manager's power and resource control.

Identify sponsor as boss on traditional projects, funding and approving changes. Report to a program manager when in a program; agile uses a product owner who is not the boss.

Identify and integrate key project areas—scope, schedule, budget, quality, resources, and procurement—while mastering communications, engagements, risk, and the project deliverable.

In large organizations, a project management office standardizes processes and enables sharing of methods, tools, and templates to support project managers, including supportive, control, and directive PMO types.

Product management guides the full life cycle from ideation to retirement, including market needs and launch. Project management delivers scoped work within that lifecycle on time and budget.

Identify and differentiate risk, issues, assumptions, and constraints in project management, and learn to use a risk register and issue log to plan responses.

Identify and manage the six project constraints: scope, schedule, cost, risks, quality, and resources, and plan ahead to protect customer satisfaction.

Contrast predictive (traditional/waterfall) and adaptive (agile) project management, highlighting upfront scope definition for predictive and iterative, feedback-driven changes for adaptive, with hybrid options.

Explore emotional intelligence as the core of people management in project work, recognizing, understanding, and empathically managing your own and others' emotions to lead, communicate, and resolve conflicts.

Compare leadership and management with a focus on when to apply each in projects. Learn how vision, motivation, and process efficiency shape success.

Explains what agile is, an umbrella term for adaptive project management, iterative and incremental methods originally developed for software, now used in all kinds of projects, often in hybrid approaches.

Differentiate iterative and incremental development within agile methods, showing how iterative builds the whole product with feedback, while incremental delivers software in small increments for early value, with dynamic requirements.

Discover why agile delivers greater customer involvement and ongoing feedback, enabling incremental value, welcoming changes, and aligning with customer requirements through a responsive product backlog.

Define value as worth, importance, or usefulness, driven by perspective. Show how projects deliver benefits relative to effort and cost, including tangible and intangible returns aligned with strategic objectives.

Prioritize high-value backlog items and release working software in 2–4 week iterations, testing in test environments to reduce costly fixes in production.

Learn how agile declaration of interdependence drives value through continuous flow and value delivery via increments; engage customers, embrace uncertainty with iterations, and foster creativity and innovation under servant leadership.

Adopt an agile mindset by welcoming changes, delivering value in increments with build and feedback loops, and prioritizing customer value through retrospectives.

Explore how agile delivers software incrementally, providing value sooner than traditional waterfall. Compare incremental planning and rapid customer feedback, noting contexts like regulated environments such as HIPAA where traditional prevails.

Explore the concept of inverting the triangle, contrasting traditional projects with fixed scope and varying time and cost, against agile projects that redefine scope while keeping time and cost constant.

Explore the 2001 agile manifesto and its values: individuals and interactions over processes and tools; working software over documentation; customer collaboration over contract; responding to change over following a plan.

Learn the 12 agile guiding principles from the Agile Manifesto, emphasizing early and continuous delivery of valuable software, welcoming changes, daily collaboration of business people and developers, self-organizing teams, and sustainable pace.

Explore the most popular agile methods, including scrum, kanban, scrum ban, DevOps, lean software development, and scale agile, to master delivering value sooner through collaborative teams.

Explore the scrum process and agile practices, from the product backlog and sprint planning to daily stand-up, sprint reviews, and retrospectives.

Explore scrum roles and responsibilities, including the product owner, scrum master, and development team, and how transparency, inspections, and adaptation guide their collaboration.

Explore scrum activities, including time-boxed sprints, sprint planning, daily stand-ups, sprint reviews, and retrospectives, and learn how these ceremonies shape the sprint backlog and stakeholder feedback.

Explore the product backlog, sprint backlog, and product increment, and how grooming and value-based prioritization shape them. Define the definition of done and emphasize customer feedback in delivering increments.

Define a shared definition of done at project start to specify when work is finished, aligning product owner, customers, and the team for project success.

Explore extreme programming (xp) in software development, compare it to scrum, and highlight xp values like simplicity, feedback, courage, respect, and roles from coach to testers.

Explore XP practices, including release planning, iterations, and continuous integration, with customer tests, test driven development, pair programming, and collective code ownership to achieve simple design and sustainable pace.

Compare scrum and XP: sprints last 1–4 weeks and include releases; product owner equals customer while scrum master maps to XP coach; daily stand-up and reflections complete the agile cycle.

Explore lean software development, drawn from the Toyota production system, to reduce waste, empower teams, identify customer defined value, and deliver high-quality software.

Explore Kanban development using a signboard, with columns like items, in-progress, testing, and done, to visualize flow and limit work in progress on a low-tech whiteboard.

Explore feature driven development, an agile, model-driven framework for large, complex projects that designs and builds features through an incremental, iterative five-step process, from modeling to per-feature delivery.

Adopt the Crystal framework, a lightweight agile method that adapts to team size, emphasizing people, safety, trust, and frequent delivery of usable features while encouraging reflection and experimentation.

Explore how SAFe coordinates lean, agile, and DevOps across large organizations with multiple teams. Emphasizes alignment, transparency, system thinking, incremental building, and strategic alignment across business and technology.

Discover Disciplined Agile, a PMI-owned toolkit that guides you to tailor your best way of working by blending lean, scrum, Kanban, and scaled agile approaches based on project context.

Learn how agile leadership contrasts with traditional management and empowers self-organizing teams through servant leadership. Shield the team from interruptions, remove impediments, and reinforce the project vision with essential resources.

Explore the 12 principles of servant leadership in agile teams, learning team needs, balancing welfare and project vision, guiding with ethics, integrity, and thinking backwards to foster accountability and conflict.

Mastering servant leadership tools and soft skills to communicate the project vision, foster inclusive collaboration, and create a safe, transparent space for experimentation and knowledge sharing.

Advocates face-to-face communication as the most effective way to engage stakeholders, emphasizing two-way knowledge sharing and low-tech, high-touch tools like whiteboards in agile settings.

Use low-tech, high-touch tools, sticky notes, whiteboards, and Kanban, to keep stakeholders engaged, build a shared vision, and define done through short iterations, reviews, and personas.

Explore agile roles—the delivery team, product owner, and Scrum Master—and how they collaborate to build increments, manage the backlog, and run daily stand-ups with information radiators.

Foster self-organizing agile teams with cross-functional skills and servant leadership. Share work to reduce bottlenecks, build a shared vision, and encourage constructive disagreement.

Design agile team spaces that prioritize face to face interaction, wall boards, and low tech collaboration. Balance co-location with distributed teams using osmotic communication and tacit knowledge in virtual collaboration.

Explore Shuhari and Dreyfus models to understand how individuals master skills from novice to expert. Apply Tuckman's five stages—forming, storming, norming, performing, adjourning—to guide team development in agile projects.

Engage the agile team to solve problems with practical, consensus-driven solutions drawn from the team's broad knowledge base, recognizing some problems are unsolvable and require facilitation for continuous improvement.

Explore the gulf of evaluation, the gap between stakeholder vision and implementation, and sharpen verification and validation through frequent feedback, peer programming, and continuous testing.

Develop negotiation skills to align stakeholders across the project, including vendors, team members, and product owners, by exploring options, practicing give and take, and prioritizing customer value.

Turn meetings into productive workshops where work gets done and solutions are tested. Use a diverse team, round-robin discussion, and user-story workshops to engage stakeholders for the next sprint.

Practice active listening by engaging with your team, interpreting body language, and becoming a level three listener to uncover issues and support project success.

Brainstorming helps teams resolve project problems by generating diverse ideas and evaluating options. Use structured approaches like quiet writing and round robin to avoid free-for-all chaos and ensure everyone contributes.

Learn to facilitate teams of experts by establishing a team charter and running goal-driven meetings. Use timeboxing and respectful communication to minimize conflict and maximize project outcomes.

Identify failure mode and success mode in agile teams and the psychological traits behind performance; apply strategies like balance, discipline, and feedback to sustain success.

Identify red zone and green zone behaviors, and learn to move team members from blame and defensiveness toward responsibility, welcoming feedback, and solving problems.

Explore five levels of project conflict, from disagreements to five escalations, and use root-cause problem solving with team decisions via simple voting and fist of five to keep conflicts constructive.

Examine motivation theories—Maslow, Herzberg, X/Y, Z, expectancy, and McClelland—to help agile and traditional project managers motivate teams, reward good work, and foster growth.

Deliver value early in agile projects by releasing high-value product increments, prioritizing components like accounts receivable to maximize return and boost stakeholder engagement for project success.

Learn adaptive, incremental agile planning that prioritizes value delivery through ongoing replanning, product backlog updates, and frequent team and customer demonstrations to handle uncertainty and change.

Deliver value with every product increment by aligning releases with what customers consider valuable. Understand stakeholder value perspectives and show how each increment creates measurable benefits.

Explain value based analysis and decomposition to assess and prioritize business value of work items, design the product box, and articulate the main value statements before agile planning.

Develop an agile charter that mirrors the traditional project charter, a high-level document outlining vision, scope, goals, and the authority to proceed with agile delivery using Scrum.

Master regulatory compliance concepts that laws supersede other directives and guide project decisions. Learn when to stop work to stay within the law and avoid noncompliance.

Focus on people over processes to manage agile projects, and use the constructive cost model to show that people costs dwarf tools and processes.

Explore how the cost of change grows over a product cycle in agile, emphasizing early requirements gathering, minimum viable product releases, and frequent sprint reviews to minimize late changes.

Explore agile financial metrics used to evaluate projects, including ROI, IRR, present value and net present value, and interpret earned value management outputs like CPI, SPI, CV and SV.

Master agile earned value management formulas such as PV, EV, AC, CV, CPI, SPI, SV, and VAC, plus pert three-point estimation and the communications formula.

Explore the minimum viable product concept in agile, delivering usable components quickly to gain customer feedback and guide product direction.

Explain minimum marketable feature as smallest set of functionality that delivers real value and can be released independently, and contrast MVP and MFS in terms of quick feedback versus monetization.

Identify defects as deviations from expected behavior or requirements. Prioritize and fix them in agile by managing them in product and sprint backlogs to prevent costly recalls.

Learn how defects upset customers and become more costly to fix as development progresses, and why early detection through continuous integration, peer programming, and testing reduces expensive post-release repairs.

Explain how task boards, including Kanban boards, act as information radiators by visualizing work in progress, coding, testing, and done, with burn up/down charts, cumulative flow diagrams, and backlogs.

Limit work in progress to prevent overworking your team and reduce stress. Use Little's law to optimize sprint output from the product backlog and minimize risk during coding.

Decompose requirements into user stories in agile, turning the product backlog into a story backlog. Use the as a user format and three Cs to ensure value and shared understanding.

Learn how teams use story points and relative sizing with the Fibonacci sequence to estimate backlog items, assign points, and build agile schedules via velocity.

Collaborate with stakeholders through three games—remember the future, prune the product tree, and speedboat (sailboat)—to clarify success criteria, map features, and identify project risks.

Explore value-based prioritization techniques for agile product backlogs, including must, should, could, and would have, dot voting, 100-point voting, monopoly money, and Keno analysis to create a high-value feature list.

Clarify the difference between lead time and cycle time with practical examples, explain their relation to work in progress, and introduce Little's Law for calculating throughput in agile projects.

Apply little's law to agile kanban work by tracking work in progress, throughput, and cycle time. Use the formula variants to improve predictability and balance.

Learn how key performance indicators (KPIs) track agile project progress against objectives, using metrics like backlog points, rate of progress, remaining work, and cost to determine KPI attainment.

Use a cumulative flow diagram to read agile progress and pinpoint bottlenecks, especially testing, by visualizing ready, development, testing, and deployment flow, guided by the theory of constraints.

Explore burn up and burn down charts to track completed versus remaining work, and velocity charts to forecast iteration capacity using product backlog points in agile projects.

Learn how technical debt accumulates from unclean code and redundant comments, and how refactoring removes dead code and unnecessary elements, reducing cost and making future changes easier before production.

Use time boxes for daily stand-ups, sprints, and retrospectives, and beware Parkinson's law that tasks expand to fill the allotted time, preventing waste.

Explore types of iterations in agile projects, including iteration zero, development iterations, and the hardening sprint, and explain spikes (architectural and risk-based) that test concepts before or during an iteration.

Analyze variances and trends to predict future project outcomes using past data and velocity. Leverage burn up and burn down charts and lagging and leading indicators to adjust sprint plans.

Identify and manage risk across traditional, agile, and hybrid projects as uncertain events with positive opportunities and negative threats, affecting scope, schedule, cost, and quality, tracked in a risk register.

Adopt a standardized risk management process from the PMBoK guide for agile and traditional projects. Identify risks, conduct qualitative and quantitative assessments, plan and implement responses, and continuously monitor risk.

Explore agile risk tools including risk adjusted backlog, risk spike, and risk burndown chart to reprioritize features, test risk responses, and read risk severity over time.

Explore managing agile projects when outsourcing, balancing fixed time with flexible scope through contracts that emphasize customer collaboration and options like change for free and graduated fixed price.

Explore how complex adaptive systems unite organizational agents to output remarkable products through emergence, adaptability, self-organization, and decentralized decision making in agile environments.

Introduce the Cynefin framework to categorize problems as simple, complicated, complex, or chaotic (with disorder in the middle) and choose the appropriate response, guiding agile leaders in decision making.

The Stacey matrix helps decide when to use agile or traditional methods by mapping certainty and agreement, guiding simple, complicated, complex, and chaotic projects.

Apply Kaizen by focusing on the team to deliver continuous, small incremental improvements; train and empower people in a safe, constructive environment to improve products and services.

Learn continuous improvement through the pdca (plan-do-check-act) cycle and value stream maps to identify waste and optimize processes, while agile methods like scrum and kanban enable ongoing product improvements.

Explore project pre-mortems, a proactive meeting to identify risks that could derail a project before planning or execution, such as regulatory changes, payroll gaps, and data porting challenges.

Learn how to run a sprint retrospective with five phases, time-boxed to two hours, and tools like fishbone diagrams, five whys, dot voting, and smart goals to drive continuous improvement.

Explore the PMI-ACP exam content outline and four domains, with tasks and enablers guiding agile exam understanding for the 120-question assessment that includes 20 unscored items.

Experiment early to gather feedback and validate solutions through incremental shells like the shell of the mouse, while encouraging continuous learning and empowering the team to innovate.

Emphasizes the agile mindset by reviewing core values and principles, applying complexity models and risk considerations, and selecting appropriate tools and methods (Scrum, Kanban) for each project scenario.

Promote a collaborative agile team environment by establishing a shared vision and working agreements, building a high-performing cross-functional team, and using retrospectives to drive continuous improvement.

Build transparency in agile projects by making status, progress, risks, and impediments visible to all via information radiators. Use Kanban boards, burn up/down charts, and feedback loops for distributed teams.

Foster psychological safety by promoting a no blame culture, encouraging constructive feedback, and challenging the status quo to drive open dialogue, objective problem solving, and team innovation.

Engage stakeholders from day one to gather feedback and validate ideas using design thinking and lean startup methods; prioritize value and deliver the most valuable features first in short increments.

Embrace change with a growth mindset and continuous learning to improve teams and products. Adapt workflows and encourage cross skills team members to flexibly meet changing customer requirements and feedback.

Empower your team through servant leadership by building trust, enabling transparent, honest communication, and promoting experimentation, coaching, mentoring, and collective ownership to improve project outcomes.

Identify root causes of problems using Ishikawa diagrams or RCA. Collaborate with the team to choose solutions and track issues in an issue log to prevent delays.

Capture and share lessons learned to promote continuous improvement, reuse organizational knowledge assets, and foster retrospectives, communities of practice, and knowledge sharing across projects.

Adopt and advocate the agile mindset across your organization by promoting agile values, prioritizing the product backlog, writing user stories, and enabling continuous improvement through retrospectives and experimentation.

Promote a shared product vision by aligning stakeholders and the team, clarifying goals, using demos or an MVP, and continually communicating to keep everyone aligned.

Identify root causes of conflict, assess its level, and apply conflict management through collaborative, respectful discussion by involving the parties to resolve issues and protect team trust.

Clarify and decompose the product backlog to ensure a shared, detailed understanding for the team, while the product owner prioritizes by value and customer needs.

Promote early, incremental delivery by prioritizing increments by business value and validating each increment against goals through stakeholder feedback.

Apply a low tech, high touch approach by using visual tools like kanban boards and burn up on burndown charts, update data sets, and share information for transparency and alignment.

Define value with stakeholders by clarifying business outcomes and compliance needs, then prioritize backlog to deliver the most valuable features, track measurable results.

Seek early feedback from users to ensure value and satisfaction. Collect input via surveys, MVPs, prototypes, and sprint reviews, then deliver work in small increments to inform the backlog.

Explore how to implement agile metrics, tailor them to stakeholders, visualize performance with dashboards, analyze trends, and use insights to prioritize work and strategic decisions.

Identify impediments and risks continuously, involve the team to brainstorm and select responses, prioritize critical risks, and monitor, reevaluate, and apply lessons learned to prevent recurrence.

Accelerate time to market by eliminating waste through end-to-end value stream mapping, cycle time tracking, and metrics-driven feedback to reduce bottlenecks and rework.

Perform continuous improvement on a project through retrospectives, gathering metrics and feedback, and implementing concrete actions to shorten stand-ups, boost velocity, reduce defects, and improve collaboration.

Actively engage customers by identifying actual users, gathering their needs, validating MVP deliverables against defined acceptance criteria through feedback loops, demos, and co-creation.

Optimize team flow by limiting work in progress, reducing interruptions, and using a Kanban approach, while tracking cycle time and lead time to drive continuous improvement.

Adopt the agile mindset as your exam-ready approach, review the core principles, and apply them to every PMI-ACP exam question.

Practice servant leadership by removing impediments and empowering the team with the right tools, while the product owner alone adds and prioritizes the product backlog.

Delve into agile mindset part 2 by emphasizing low tech, high touch and co-location to boost individuals and interactions through face-to-face or virtual collaboration, whiteboards, and sticky notes.

Explore information radiators in agile teams, including Kanban boards and burn up and burndown charts, and learn to coach teams to solve problems and foster a safe, constructive disagreement environment.

Limit work in progress with Kanban to prevent bottlenecks and reduce risk, while keeping the project vision visible and understanding each team member's motivators to sustain high outputs.

Define success and failure from customer and team perspectives, remember the future, and reinforce an agile mindset through retrospectives, feedback loops, and ethical truthfulness and law.

Explore a full-length PMI-ACP mock exam with detailed explanations for questions 1–20, illustrating how to apply the agile mindset to compliance, backlog integration, risk, stakeholder communication, and prioritization.

Watch video explanations of mock PMI-ACP questions 21–40, covering retrospectives, agile metrics, self-organizing teams, stakeholder collaboration, and value-driven delivery.

Explore PMI-ACP mock questions 41–60 explanations, emphasizing agile principles and dealing with working software over heavy documentation, value stream mapping, backlog refinement, risk management, and stakeholder feedback.

Deliver PMI-ACP exam insights through mock questions, highlighting risk burndown charts, agile charter, definition of done, cross-functional collaboration, and value-driven backlog prioritization.

this mock set of questions explains proactive risk and impediment management, value stream mapping for end-to-end flow, low-fidelity wireframes and personas, and inclusive, transparent agile collaboration and visibility.

Practice agile decision-making through mock PMI-ACP questions on facilitation, sprint planning, daily scrum, backlog grooming, and stakeholders' needs.

Learn how to claim your 28 PDUs and generate the PMI certificate via the bonus lecture, with 30 hours of study including videos, quizzes, and mock exams for PMI audit.