PMI-ACP Explained: Pass PMI-ACP Exam 2025 + 300 Questions

Explore the agile manifesto and its 12 principles to understand the ideas behind agile practices, and access a detailed explanation linked to the PMI-ACP curriculum.

Explore how the agile manifesto emerged in 2001, defining four values and twelve principles that prioritize individuals, working software, customer collaboration, and responding to change.

Explain the four agile manifesto values: individuals and interactions, working software, customer collaboration, and responding to change, emphasizing people, collaboration, and flexible delivery.

Explore the agile manifesto and its twelve principles, focusing on early and continuous delivery of valuable software, customer satisfaction, and frequent feedback through iterations and collaboration.

Explore agile values and principles, including working software as the primary measure, sustainable pace, technical excellence, simplicity, self-organizing teams, and regular retrospectives.

Master agile foundations by studying the four values of the Agile Manifesto: individuals and interactions, working software, customer collaboration, and responding to change, and the 12 principles.

Explore how agile manifesto and principles guide various methodologies, and how practitioners tailor agile concepts to their circumstances.

Learn how agile applies to real projects through Scrum, including sprints, potentially shippable increments, definition of done, product backlog, user stories, and the Scrum team roles and events.

Discover extreme programming (xp), Kent Beck's lightweight agile method with short iterations yielding shippable increments, guided by simplicity, communication, feedback, respect, and courage.

Explore lean software development, its seven core concepts, and how lean aligns with agile to maximize value, amplify learning, and deliver quality software quickly.

Kanban visualizes the workflow with cards on a board, limits work in progress, and promotes incremental change and Kaizen, helping teams reveal bottlenecks and improve flow.

Explore the dynamic systems development method (dsdm), a constraint-driven agile approach that fixes cost, time, and quality while adjusting scope, emphasizing business needs, collaboration, and incremental delivery.

Explore feature driven development (FDD), a lightweight agile method prioritizing client-valued features expressed as action, result, and object, from modeling to iterative feature delivery with domain object modeling.

Discover the crystal family of agile methods, color-coded to suit project size and criticality. Learn core crystal principles like frequent delivery, osmotic communication, and automated tests for rapid, tailored results.

Learn agile methodologies and the manifesto values, explore Scrum with sprints, product backlog, roles, and events, and compare XP, Lean, Kanban, FDD, DSDM, and Crystal.

Learn how to justify an agile project during initiation by assessing costs and benefits, prioritizing high-value work, and selecting the best project before kickoff.

Analyze project financial assessment methods, including ROI, payback period, PV, NPV, and IRR, to evaluate value, regulatory compliance, and agile-versus-traditional project choices.

Discover agile project chartering, contrast agile and traditional charters, and craft a lightweight one-page charter focused on vision, benefits, done criteria, and collaboration through elevator statements.

Explore agile project initiation, justify ROI with payback, PV, NPV, and IRR, and craft lightweight contracts and agile charters to align purpose and value.

In agile projects with fixed cost and schedule, prioritize by business value and reprioritize to deliver value; high/medium/low scales may misalign with customer priorities, prompting alternative prioritization techniques.

Prioritize the product backlog by customer value, from highest to lowest, and collaborate with the customer to groom and update it for each time box, delivering the highest value items.

Explore the MoSCoW prioritization technique, defining must-have, should-have, could-have, and won’t-have requirements, with mobile phone examples and guidance on prioritizing to reduce project risk.

Explore Kano analysis to prioritize features by customer value, mapping preferences into dissatisfiers, satisfiers, delighters, and indifferent to drive product satisfaction.

Explore various prioritization techniques for agile projects, including monopoly money, 100-point method, dot voting, and buy-a-feature, and learn how stakeholders allocate budget to prioritize requirements.

Explain MMF, MVP, and MMP, showing how to deliver value with minimal features, test learning, and accelerate time-to-market.

Identify and prioritize work items by business value and ROI to deliver early customer value, balancing cost, dependencies, and risk through a continuous, risk-adjusted backlog.

Rank features by value to deliver the minimal marketable product within cost and time constraints. Use a virtual cutoff to drop lower-value items and adjust the backlog accordingly.

Prioritize agile requirements by business value, given fixed cost and time and flexible scope, using MOSCOW and Kano analysis to rank backlog items and cover MVP, MMF, and MMP concepts.

Learn how user stories replace faulty, ambiguous requirements by enabling open user discussion, boosting agile developers' creativity, and guiding design, implementation, testing, and estimation for delivery.

Learn how user stories fuel agile backlogs, define acceptance criteria, and drive value through card-conversation-confirmation, using INVEST and collaboration with product owners.

Discover the requirements hierarchy from epics to tasks, including themes and features, and how large placeholders decompose into user stories in the product backlog.

The product backlog holds epics, features, stories, defects, risks, and technical tasks, prioritized by customer value; the Product Owner and team continuously groom items, refine estimates, and adjust priorities.

Learn how story maps visualize the end-to-end user experience, using a backbone and walking skeleton to drive a product roadmap and MMP in agile releases.

Discover how user stories capture value from the user, define acceptance criteria, and guide backlog grooming, estimation, and the journey from story map to product roadmap.

Engage in collaborative agile discovery to continually define the right product and the highest-value backlog through product owner and customer collaboration, evolving requirements, and iterative learning.

Progressive elaboration drives agile life cycles by continuously refining the project plan as information accumulates, enabling backlog refinement, rolling wave planning, and just-in-time estimates with frequent stakeholder feedback.

Adopt the learning cycle by applying the plan-do-check-act loop to agile work, learn from mistakes, and improve through knowledge sharing and 2-4 week learning cycles.

Explore agile discovery, progressive elaboration, and backlog refinement that guide evolving requirements and value-driven planning. Apply rolling wave planning and the plan-do-check-act learning cycle to learn and adapt.

Explore why agile estimation differs from traditional bottom-up methods and how upfront requirements fail in knowledge work with high uncertainty; learn best practices for agile project estimation.

Learn agile sizing and estimation through top-down, rolling wave planning, refining estimates in ranges as information unfolds, with the agile team owning estimation to support ROI and project decisions.

Explore how agile uses relative sizing and story points to estimate work by comparing tasks to a baseline, reducing subjectivity and focusing on complexities, risks, and efforts involved.

Master the agile estimation technique of t-shirt sizing, a non-numerical, relative method using XS to XXL for initial project estimates, with teams sizing stories through progressive elaboration.

Master planning poker, or scrum poker, to minimize influence and improve estimates using a fibonacci-based deck, simultaneous card reveals, and structured discussions that lead to consensus.

Explore wideband delphi, a consensus-based estimation method using anonymous rounds and collaborative input from team members, SMEs, the product owner, and stakeholders to improve estimates.

Explore affinity estimating, a quick grouping method for user stories by size and complexity to ensure consistent estimates, using S, M, L or Fibonacci scales and collaborative discussion.

Explore ideal time as a simple agile estimation method, distinguish it from elapsed time, and learn how interruptions and personal variances affect delivery estimates using past sprint heuristics.

Compare story points and ideal days as estimation units, weighing advantages, disadvantages, and collaboration to guide agile project estimation decisions.

Learn to estimate with all activities accounted for, keep consistent story point units, and let the team define the base point to plan confidently while considering risk and complexity.

Explore how agile estimation handles uncertainty with top-down ranges and iterative refinement. Compare story points, ideal time, and sizing methods like t-shirt sizing, planning poker, and wideband Delphi.

Explore how agile planning occurs across product vision, product planning, release and iteration levels, and learn velocity and definition of done to guide releases.

Learn how agile planning uses adaptive planning and prototypes to refine uncertain requirements through iterative cycles, backlog refinement, and release and iteration planning.

Deliver value early by creating successive increments that add functionality, test and review to reduce risk and cost of change, and adapt to changing requirements.

Measure velocity to gauge a team's capacity for work per iteration using points, and communicate completed user stories, expected deliverables, and project completion timelines.

Define the definition of done (DoD) as a checklist ensuring acceptance criteria and tests are met from user stories to release, using agile charters to establish a shared vision.

Plan releases and iterations early, refine the product backlog into smaller user stories, and prioritize work to deliver valuable increments within a release timeframe.

Plan iteratively by focusing on the next sprint's subset of the release backlog, with a self-organizing team selecting stories, estimating work, and defining acceptance tests to achieve the iteration goal.

Discover timeboxed iteration types, usually 1-4 weeks, beyond development sprints, including iteration 0 for preparation and iteration H for hardening and release, with optional timing.

Explore agile project accounting principles, contrasting them with traditional methods, and learn how ROI-focused delivery, micro deliverables contracts, and capitalization of development costs shape agile finance.

Explore architectural spikes as timeboxed experiments that model and prototype options to determine feasibility and the best approach before building, addressing a single clear question to guide design decisions.

Timeboxing curbs Parkinson’s law and student syndrome by using short, fixed time boxes for prioritized work, applying to sprints, stand-ups, planning, and reviews to reduce uncertainty and boost value.

Explore agile planning that emphasizes adaptability, incremental delivery, and prototyping to align with stakeholders, and learn about delivering minimum marketable product first, iterations, releases, timeboxing, velocity, DoD, and agile accounting.

Master agile requirements analysis by ensuring requirements are complete, clear, concise, and testable, and by using agile tools and techniques to validate customer needs.

Adopt low-tech-high-touch tools like task boards, flip charts, and user story stickies to maximize visibility and engage all stakeholders in agile projects.

Learn agile modeling as a lightweight, barely sufficient approach to capture essential requirements with simplicity. Use personas, wireframes, user stories, and workshops to align stakeholders and foster collaboration.

Collaborative and innovation games in agile projects elicit and prioritize requirements, identify risks, and build stakeholder consensus using Remember the future, prune the product tree, and speedboat.

Explore agile requirements analysis through low-tech-high-touch tools, lightweight agile modeling, and collaborative workshops using user stories, personas, wireframes, and collaboration games to obtain rapid feedback from stakeholders.