AGILE CERTIFIED PRACTITIONER STUDY GUIDE (PMI-ACP) QUESTIONS ANSWERED CORRECTLY
LATEST UPDATE 2026
Deep - Answers The qualities of a product backlog which include: detailed, estimate-able, emergent,
& prioritized.
Deliverables - Answers A tangible or intangible object delivered to the customer. Ex. Document,
pamphlet, report etc.
Earned Value Management (EVM) - Answers Earned value management, works well at iteration. It is
a method to measure & communicate progress & trends at the current stage of the project.
Adaptive Leadership - Answers A leadership style that helps teams to thrive & overcome challenges
throughout a project.
Disaggregation - Answers To separate epics or large stories into smaller stories.
Affinity Estimation - Answers A method used to quickly place user stories into a comparable sized
group.
Emergent - Answers Stories that grow & change over time as other stories reach completion in the
backlog.
Pareto Principle - Answers Known as the 80/20 rule. For agile projects, it means that 80% of all
development should be spent on the top 20% of the features the customers need.
Quantitative - Answers Numerical data used for analysis.
Command & Control - Answers Decisions created by higher up individuals in the organization &
handed over to the team.
Epic Story - Answers A large story that spans iterations, then is disaggregated into smaller stories.
Dynamic Systems Development Model (DSDM) - Answers A model that provides a comprehensive
foundation for planning, managing, executing, & scaling agile & iterative software development
projects based on 9 principles that involve business needs/value, active user involvement,
empowered teams, frequent delivery, integrated testing, & stakeholder collaboration.
War Room - Answers A space where the team can work & collaborate effectively.
Refactoring - Answers To adjust working code to improve functionality & conservation.
Emotional Intelligence - Answers An individual's skill to lead & relate to other team members.
Agile Manifesto: Self-Organization - Answers A team that knows how to complete tasks effectively,
has dedication to the project, & is expert on the process & project.
Communication - Answers To share smooth & transparent information of needs.
Common Cause - Answers An issue solved through trend analysis because the issue is systematic.
Agile Manifesto: Simplicity - Answers Allows team members to focus on what is necessary to achieve
the requirements needed to create & deliver value to the project & customer.
Done - Answers When work is complete, & meets the following criteria: complies, runs without
errors, & passes predefined acceptance & regression tests.
Agile Manifesto: Collocated Team - Answers To have individuals work together daily on a project to
implement osmotic communication, focus, & receive instant feedback to achieve a common goal.
Intraspectives - Answers To inspect within, during a meeting with the agile team to review practices,
usually when a problem or issue occurs.
Conflict Resolution - Answers An agreement made after a conflict.
Exploratory Testing - Answers To inquire how software works with the use of test subjects using the
software & asking questions about the software.
Participatory Decision Models - Answers To have stakeholder's involvement in decision making with
techniques such as a simple vote.
Last Responsible Moment - Answers To make decisions as late as possible in order to preserve all
possible options.
Requirements Prioritization Model - Answers A model to rate each feature with the calculation of
weighted formula defined by the team.
Requirements Review - Answers To review the requirements so they fulfill the needs & priorities of
stakeholders.
Kanban Board - Answers A chart that shows workflow stages to locate work-in-progress.
Invest - Answers The benefits of good user stories, which include: independent, negotiable, valuable,
estimate-able, small, & testable.
Intrinsic Schedule Flaw - Answers Poor estimation that occurs at the beginning of iteration.
Story Point - Answers A unit of measurement to estimate the difficulty of a user story.
, Story Map - Answers A prioritization tool that backlogged stories made smaller & organized by user
functionality.
Negotiable - Answers Anything open to discussion.
Negotiation - Answers To reach an agreement between 2 or more parties to resolve a conflict.
Collaboration - Answers A method of cooperation among individuals to achieve a common goal.
Time-Boxing - Answers To set a fixed delivery date for a project or release.
Theme - Answers A group of stories, iteration, or release's idea determined by the customer & the
team agrees with the idea.
Pair Programming - Answers When developers work together in XP practice.
Customer - Answers The end-user who determines & emphasizes business values.
Product Backlog - Answers The known features for a project,
WIP Limits - Answers To limit work-in-progress so a team can do the following: maintain focus on
completing work, maintaining quality, & delivering value.
Scope Creep - Answers The uncontrolled changes or growth in a project's scope which goes beyond
the initial agreement.
Cost Performance Index (CPI) - Answers To measure the cost spent on a project & its efficiency.
Earned value/actual cost = CPI
Traditional Management - Answers A top-down approach that consists of long cycles, heavy planning,
& minimal customer involvement.
Scrum - Answers A popular agile methodology.
Product Roadmap - Answers An artifact that displays planned project functionality.
Shu-ha-ri Model - Answers Originated in Japan as a way to understand learning & mastery, Shu -
obeying the rules, Ha - consciously moving away from the rules, and Ri - consciously finding an
individual path.
Transparency - Answers To show everyone's involvement & progress to the entire team.
Wide-Band Delphi Estimating - Answers An estimation technique for user stories. The PO presents
user stories & discuss challenges. Each story's estimates plotted, & then the team comes to an
agreement on the range of points.
Product Vision - Answers A document that describes what the product is, who will use the product,
why the product will be used, & how the product supports the strategy of a company.
Scrum of Scrums - Answers Meetings used to organize large projects with scrum masters from
different teams.
Coordination - Answers To organize work with the goal of higher productivity & teamwork.
Integrative Negotiation - Answers To reach an agreement collaboratively that creates more value for
both parties by a win-win solution.
Product Vision Statement - Answers A statement that defines the purpose & value of the product.
Scrum Master - Answers The leader that helps the team to follow scrum methodology.
Trend Analysis - Answers This analysis provides trends that will occur in the future to help control &
implement continuous improvement.
Standardized Test - Answers A curved test to measure knowledge & understanding, but constructed
so the same test-maker will perform similarly each time.
Osmotic Communication - Answers To communicate by sharing an environment.
Programmer - Answers The role of a team member that writes the code, a role used in XP.
Verification - Answers To ensure the product meets requirements & specifications.
Risk Adjusted Backlog - Answers A product backlog adjusted to help balance the risk & value factors
of product.
Agile Planning - Answers The most important aspect of the agile project. Planning happens at
multiple levels such as strategic, release, iteration, & daily. Planning must happen up-front & can
change throughout the project.
Extreme Persona - Answers A team-manufactured persona that exaggerates to induce requirements
a standard persona may miss.
Virtual Team - Answers A geographically distributed group that does not meet physically.
Risk-Based Spike - Answers This spike helps the team remove major risks, and if the spike fails every
approach possible, the project is defined as "fast failure."
Agile Practices - Answers To make use of the agile principles through activities.
Extreme Programming (XP) - Answers A methodology in agile with one-week iterations & paired
development.
LATEST UPDATE 2026
Deep - Answers The qualities of a product backlog which include: detailed, estimate-able, emergent,
& prioritized.
Deliverables - Answers A tangible or intangible object delivered to the customer. Ex. Document,
pamphlet, report etc.
Earned Value Management (EVM) - Answers Earned value management, works well at iteration. It is
a method to measure & communicate progress & trends at the current stage of the project.
Adaptive Leadership - Answers A leadership style that helps teams to thrive & overcome challenges
throughout a project.
Disaggregation - Answers To separate epics or large stories into smaller stories.
Affinity Estimation - Answers A method used to quickly place user stories into a comparable sized
group.
Emergent - Answers Stories that grow & change over time as other stories reach completion in the
backlog.
Pareto Principle - Answers Known as the 80/20 rule. For agile projects, it means that 80% of all
development should be spent on the top 20% of the features the customers need.
Quantitative - Answers Numerical data used for analysis.
Command & Control - Answers Decisions created by higher up individuals in the organization &
handed over to the team.
Epic Story - Answers A large story that spans iterations, then is disaggregated into smaller stories.
Dynamic Systems Development Model (DSDM) - Answers A model that provides a comprehensive
foundation for planning, managing, executing, & scaling agile & iterative software development
projects based on 9 principles that involve business needs/value, active user involvement,
empowered teams, frequent delivery, integrated testing, & stakeholder collaboration.
War Room - Answers A space where the team can work & collaborate effectively.
Refactoring - Answers To adjust working code to improve functionality & conservation.
Emotional Intelligence - Answers An individual's skill to lead & relate to other team members.
Agile Manifesto: Self-Organization - Answers A team that knows how to complete tasks effectively,
has dedication to the project, & is expert on the process & project.
Communication - Answers To share smooth & transparent information of needs.
Common Cause - Answers An issue solved through trend analysis because the issue is systematic.
Agile Manifesto: Simplicity - Answers Allows team members to focus on what is necessary to achieve
the requirements needed to create & deliver value to the project & customer.
Done - Answers When work is complete, & meets the following criteria: complies, runs without
errors, & passes predefined acceptance & regression tests.
Agile Manifesto: Collocated Team - Answers To have individuals work together daily on a project to
implement osmotic communication, focus, & receive instant feedback to achieve a common goal.
Intraspectives - Answers To inspect within, during a meeting with the agile team to review practices,
usually when a problem or issue occurs.
Conflict Resolution - Answers An agreement made after a conflict.
Exploratory Testing - Answers To inquire how software works with the use of test subjects using the
software & asking questions about the software.
Participatory Decision Models - Answers To have stakeholder's involvement in decision making with
techniques such as a simple vote.
Last Responsible Moment - Answers To make decisions as late as possible in order to preserve all
possible options.
Requirements Prioritization Model - Answers A model to rate each feature with the calculation of
weighted formula defined by the team.
Requirements Review - Answers To review the requirements so they fulfill the needs & priorities of
stakeholders.
Kanban Board - Answers A chart that shows workflow stages to locate work-in-progress.
Invest - Answers The benefits of good user stories, which include: independent, negotiable, valuable,
estimate-able, small, & testable.
Intrinsic Schedule Flaw - Answers Poor estimation that occurs at the beginning of iteration.
Story Point - Answers A unit of measurement to estimate the difficulty of a user story.
, Story Map - Answers A prioritization tool that backlogged stories made smaller & organized by user
functionality.
Negotiable - Answers Anything open to discussion.
Negotiation - Answers To reach an agreement between 2 or more parties to resolve a conflict.
Collaboration - Answers A method of cooperation among individuals to achieve a common goal.
Time-Boxing - Answers To set a fixed delivery date for a project or release.
Theme - Answers A group of stories, iteration, or release's idea determined by the customer & the
team agrees with the idea.
Pair Programming - Answers When developers work together in XP practice.
Customer - Answers The end-user who determines & emphasizes business values.
Product Backlog - Answers The known features for a project,
WIP Limits - Answers To limit work-in-progress so a team can do the following: maintain focus on
completing work, maintaining quality, & delivering value.
Scope Creep - Answers The uncontrolled changes or growth in a project's scope which goes beyond
the initial agreement.
Cost Performance Index (CPI) - Answers To measure the cost spent on a project & its efficiency.
Earned value/actual cost = CPI
Traditional Management - Answers A top-down approach that consists of long cycles, heavy planning,
& minimal customer involvement.
Scrum - Answers A popular agile methodology.
Product Roadmap - Answers An artifact that displays planned project functionality.
Shu-ha-ri Model - Answers Originated in Japan as a way to understand learning & mastery, Shu -
obeying the rules, Ha - consciously moving away from the rules, and Ri - consciously finding an
individual path.
Transparency - Answers To show everyone's involvement & progress to the entire team.
Wide-Band Delphi Estimating - Answers An estimation technique for user stories. The PO presents
user stories & discuss challenges. Each story's estimates plotted, & then the team comes to an
agreement on the range of points.
Product Vision - Answers A document that describes what the product is, who will use the product,
why the product will be used, & how the product supports the strategy of a company.
Scrum of Scrums - Answers Meetings used to organize large projects with scrum masters from
different teams.
Coordination - Answers To organize work with the goal of higher productivity & teamwork.
Integrative Negotiation - Answers To reach an agreement collaboratively that creates more value for
both parties by a win-win solution.
Product Vision Statement - Answers A statement that defines the purpose & value of the product.
Scrum Master - Answers The leader that helps the team to follow scrum methodology.
Trend Analysis - Answers This analysis provides trends that will occur in the future to help control &
implement continuous improvement.
Standardized Test - Answers A curved test to measure knowledge & understanding, but constructed
so the same test-maker will perform similarly each time.
Osmotic Communication - Answers To communicate by sharing an environment.
Programmer - Answers The role of a team member that writes the code, a role used in XP.
Verification - Answers To ensure the product meets requirements & specifications.
Risk Adjusted Backlog - Answers A product backlog adjusted to help balance the risk & value factors
of product.
Agile Planning - Answers The most important aspect of the agile project. Planning happens at
multiple levels such as strategic, release, iteration, & daily. Planning must happen up-front & can
change throughout the project.
Extreme Persona - Answers A team-manufactured persona that exaggerates to induce requirements
a standard persona may miss.
Virtual Team - Answers A geographically distributed group that does not meet physically.
Risk-Based Spike - Answers This spike helps the team remove major risks, and if the spike fails every
approach possible, the project is defined as "fast failure."
Agile Practices - Answers To make use of the agile principles through activities.
Extreme Programming (XP) - Answers A methodology in agile with one-week iterations & paired
development.
