PMI-ACP PMI Agile Certified Practitioner (PMI-ACP) Questions and Answers

Agile promotes maintaining the integrity of the sprint commitment once it begins. According to the PMI Agile Practice Guide (Section 5.4: Sprint Planning and Managing Change), new requirements discovered mid-sprint should be added to the product backlog and reprioritized for a future sprint unless they are critical blockers.

Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 7: Problem Detection and Resolution) explains that backlog management is key to handling emerging work. Agile teams should not reactively shift focus, as it disrupts flow and predictability.

Option B is correct: placing the new requirement in the backlog respects sprint boundaries and ensures proper prioritization.

Option A disrupts sprint scope mid-course.

Option C is unnecessary unless the issue is blocking progress.

Option D violates the principle of sprint focus and planning discipline.

To identify the features that offer the maximum value, the product owner should focus on understanding the needs and priorities of the product ' s end users. By identifying the users and their key activities, the product owner can ensure that the features included in the roadmap directly address the most important user needs and deliver the highest value. This user-centric approach ensures that the product delivers tangible benefits to its intended audience and aligns with their requirements.

The correct answer is D – Reestimate all stories including values for A, B, and C. Agile promotes empirical process control, meaning teams adapt based on what they learn. When significant deviations are found in actual effort vs. story point estimates, the team should revisit and refine their estimation process, including reestimating stories to better align with reality.

From the PMI Agile Practice Guide:

“Estimates are revisited based on experience. Teams inspect and adapt during retrospectives, using data to improve future estimation accuracy.”

(PMI Agile Practice Guide, Section 5.3 – Estimation and Planning)

Mike Griffiths writes:

“When estimates prove inaccurate, teams should reestimate affected stories. Estimating is a collaborative process, and learning from past deviations is a key part of adaptive planning.”

(Mike Griffiths, PMI-ACP Exam Prep, Chapter 5 – Adaptive Planning)

Incorrect options:

A may distort estimation by comparison and not correct the root issue.

B manipulates velocity data and violates agile principles of transparency.

C attempts to “force fit” effort rather than inspect and adapt.

Answer: D

────────────────────────────────────

The project manager should engage in a constructive conversation with the team member to understand the reasons behind the performance dip. Instead of focusing on blame, it’s important to discuss the specifics of the project deliverables and identify any challenges or factors that may be affecting the team member ' s performance. Providing constructive feedback helps the team member understand the areas of improvement while maintaining a supportive environment. This approach encourages open communication, identifies potential solutions, and can lead to a positive outcome for both the team member and the project.

The correct answer is C – Passive-aggressive. When a team delivers work but avoids open discussion or interaction, especially in meetings, it may indicate passive-aggressive behavior. This behavior might reflect unresolved tension, lack of engagement, or unwillingness to collaborate transparently.

From the PMI Agile Practice Guide:

“High-performing agile teams thrive on open communication and collaboration. Passive-aggressive behavior, where communication is avoided despite task completion, can hinder trust and team health.”

(PMI Agile Practice Guide, Section 4.3 – Team Performance and Collaboration)

Mike Griffiths warns:

“Silence or avoidance in agile teams may signal underlying issues. While work might be completed, lack of transparency and communication should be addressed early to maintain team cohesion.”

(Mike Griffiths, PMI-ACP Exam Prep, Chapter 4 – Team Performance)

Incorrect options:

A refers to real-time communication and is unrelated to emotional dynamics.

B is contradicted by the lack of vocal interaction.

D implies disorder or lack of structure, which is not evident here.

Answer: C

────────────────────────────────────

To prevent the prioritization meeting from turning into a brainstorming session, the product owner should ensure that user stories are well-defined before they are added to the backlog. By reviewing the items with the product owner’s teammates (or stakeholders) beforehand, the product owner can clarify the details of the stories and ensure they are properly defined. This allows the team to focus on prioritization during the meeting, rather than spending time clarifying vague requests. This proactive approach improves the efficiency and effectiveness of the prioritization process.

The correct answer is A — Capture risks and make them visible, and use a burndown chart to focus on reducing risks early in the project.

Technical uncertainty is a key area of risk in Agile projects. These risks should be clearly communicated, visualized, and prioritized early in the project to allow timely mitigation. Agile teams are empowered to make decisions and highlight blockers rather than delay work or seek hierarchical intervention.

PMI Agile Practice Guide states:

“Agile teams actively manage risk through transparency and continuous feedback. Risks should be made visible on information radiators and addressed early in the project to prevent impact on value delivery.”

(PMI Agile Practice Guide, Section 7.3 – Risk Management)

Mike Griffiths adds:

“Teams facing uncertainty must surface risks openly and early. Using charts such as risk burndown and dashboards helps keep focus on managing these risks iteratively.”

(PMI-ACP Exam Prep, Chapter 6 – Problem Detection and Resolution)

Incorrect options:

B contradicts the time-boxing principle of sprints.

C raises awareness but lacks proactive risk mitigation.

D introduces a command-and-control dynamic, which is not agile.

Answer: A

—

The correct answer is A – High-risk features can be prioritized to fit into releases with less work in progress. Agile emphasizes risk-driven delivery: high-risk and high-value features should be addressed early to reduce uncertainty. Managing WIP also helps improve focus and throughput.

From PMI Agile Practice Guide:

“Agile teams often deliver the highest risk or highest value items early in the project. This helps reduce uncertainty and allows for faster feedback and adaptation.”

(PMI Agile Practice Guide, Section 3.4 – Value Delivery and Risk)

From Mike Griffiths’ PMI-ACP Exam Prep Book:

“Prioritizing high-risk features early is a proactive risk management strategy. Teams can reduce the likelihood of failure by discovering major issues early and correcting them while time and budget allow.”

(Mike Griffiths, Chapter 5 – Adaptive Planning)

Option B delays addressing risk.

Option C focuses on low-value items and may not satisfy customer concerns.

Option D adjusts WIP but doesn’t directly address prioritizing the risky features.

Answer: A

────────────────────────────────────────────

The correct answer is D – Stop updating the documentation and initiate an analysis to identify its value and act on the findings.

Agile promotes the creation of “just enough” documentation. If a document isn’t being used and adds no value, the team should reflect on whether to discontinue or improve it. Retrospectives are the appropriate venue to identify such inefficiencies and implement continuous improvement.

From the Agile Manifesto (referenced in PMI Agile Practice Guide):

“Working software over comprehensive documentation.”

From the PMI Agile Practice Guide:

“Agile teams minimize non-value-added work. If documentation is not being used or reviewed, teams should examine whether it is necessary, and if not, discontinue or replace it.”

(PMI Agile Practice Guide, Section 7.1 – Continuous Improvement)

Mike Griffiths adds:

“Documentation should serve a purpose. If stakeholders do not find value in it, the team should discontinue or refactor it to meet actual needs.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 7 – Continuous Improvement)

Why the other options fall short:

A prolongs the wasteful practice unnecessarily.

B lacks the analysis needed before eliminating documentation.

C enforces process over value, which contradicts Agile principles.

Answer: D

══════════════════════════════════════════════════

The correct answer is C – The Product Owner, since their vision is the basis for the acceptance criteria.

The Product Owner is responsible for defining the product backlog items, including their acceptance criteria. They represent the customer and stakeholders, and ensure that the backlog items deliver business value. During backlog refinement, the PO provides clarity to the team when questions arise.

From the PMI Agile Practice Guide:

“The product owner defines and prioritizes the product backlog and is responsible for ensuring user stories and acceptance criteria are clear and understood by the team.”

(PMI Agile Practice Guide, Section 5.2 – Backlog Refinement)

Mike Griffiths states:

“The product owner is the central point for decisions related to backlog items. Their role is to ensure that requirements and acceptance criteria reflect the desired outcome and stakeholder expectations.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 3 – Value-Driven Delivery)

Other options are incorrect:

A (Sponsor) is too high-level and not involved in story-level discussions.

B (Scrum Master) facilitates the process, not the requirements.

D (Developer) implements the story but does not define acceptance.

Answer: C

The agile facilitator should focus on keeping the daily coordination meeting (daily stand-up) focused and efficient. If the meeting is becoming unproductive or lengthy, the facilitator needs to actively manage the flow and intervene when team members deviate from the meeting ' s objective, which is to quickly discuss progress, identify blockers, and align on the work for the day. By doing this, the facilitator can help the team maintain the purpose and time-box of the meeting, which is generally 15 minutes.

The ideal way to resolve the conflict is to encourage the team to brainstorm and propose an alternative solution that meets the intent of the architect’s request (error logging) but with a solution that fits within the current release timeline. By implementing error logging at the client level, the team can still address the monitoring and logging needs without significantly delaying the release. This approach fosters collaboration, balances priorities, and focuses on delivering value within the agreed timeline.

In the context of the chatbot ' s post-release complaints about edge cases in query responses, User Acceptance Testing (UAT) is the most critical step to avoid such situations. UAT ensures that the chatbot meets the stakeholder ' s needs and expectations, which would have included verifying its behavior with real users under real-world scenarios. This step would identify any edge case issues and make sure the chatbot is aligned with business goals before going live.

The correct answer is D – Ask the team to estimate the amount of rework needed so that adjustments can be made to both the project and release plan.

Agile planning is adaptive and iterative. New information, including required rework, must be integrated into updated estimates and plans. Agile teams frequently replan based on the realities of work-in-progress.

From the PMI Agile Practice Guide:

══════════════════════════════════════════════════

Velocity is a tool for internal team improvement and forecasting, not external benchmarking. According to the PMI Agile Practice Guide (Section 5.4: Velocity and Estimation) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 3: Team Performance), tracking velocity over time helps teams assess the impact of process changes, refine estimates, and validate their continuous improvement efforts.

Option C is correct: it focuses on team-level improvement.

Option A uses velocity inappropriately for performance review, which goes against agile principles.

Option B promotes unhealthy comparisons across teams.

Option D is partially true, but stakeholder communication is secondary to internal use.

The correct answer is B – Discuss the situation with the functional manager. The Scrum Master serves as a facilitator and servant leader, helping resolve impediments that interfere with the team’s ability to deliver. When conflicting assignments arise, the Scrum Master should facilitate communication with functional managers to clarify priorities and reinforce team commitments.

From the PMI Agile Practice Guide:

“The Scrum Master removes impediments and facilitates collaboration with stakeholders, including functional managers, to ensure the team can focus on sprint goals.”

(PMI Agile Practice Guide, Section 4.2 – Agile Leadership and Stakeholder Collaboration)

Mike Griffiths writes:

“When external interference affects team performance, the Scrum Master should engage in dialogue with stakeholders to clarify roles and commitments, promoting alignment and removing blockers.”

(Mike Griffiths, PMI-ACP Exam Prep, Chapter 4 – Team Performance)

Incorrect options:

A is extreme and not within the Scrum Master ' s authority.

C is unnecessarily escalatory.

D is confrontational and undermines collaboration.

Answer: B

Agile promotes cross-team collaboration and shared understanding of goals, especially when dependencies exist. The PMI Agile Practice Guide (Section 4.3.1: Team Collaboration and Alignment) recommends using vision alignment and shared objectives to reduce silos and improve coordination. A vision-sharing session ensures that all teams understand the business context and mutual interdependencies, helping build accountability and improve collaboration.

Option B is correct: shared vision fosters alignment and commitment.

Option A is punitive and against agile values of collaboration.

Option C disrupts team stability and should not be a first step.

Option D addresses the symptom (delivery delay) but not the root cause (lack of shared vision/accountability).

The daily scrum is the appropriate forum for team members to raise and discuss any impediments or blockers they are facing. By addressing the impediments directly in the daily scrum, the team can collaborate and work together to find solutions in real time. This ensures that issues are identified early and are dealt with in a timely manner. Relying solely on emails for communication can lead to missed opportunities for immediate resolution and may cause frustration, as seen in this case. Encouraging the team member to raise the impediments during the daily scrum will help ensure they are addressed quickly and effectively.

The correct answer is D – Have the Product Owner explain the product vision and review the release plan with the team. One of the Product Owner’s key responsibilities is to communicate the product vision and ensure the team understands how their work aligns with business value. This fosters alignment and motivation.

From the PMI Agile Practice Guide:

“The Product Owner is responsible for communicating the product vision and roadmap. This ensures that the team understands the ‘why’ behind the work and how each piece contributes to overall business goals.”

(PMI Agile Practice Guide, Section 4.2 – Stakeholder Engagement and Product Vision)

Mike Griffiths adds:

“Teams need context for their work. The product owner provides this by clearly sharing the vision and maintaining a transparent roadmap.”

(Mike Griffiths, PMI-ACP Exam Prep, Chapter 3 – Value-Driven Delivery)

Incorrect options:

A is useful but doesn’t address the larger product context.

B may help with story structuring but doesn’t clarify vision.

C delays resolving an immediate misunderstanding.

Answer: D

────────────────────────────────────

By moving to an iterative approach, the organization can focus more on delivering value and benefits incrementally, with each iteration producing a working product or a usable increment. This allows the team to receive feedback from stakeholders more frequently and make adjustments as needed, ensuring that the most valuable features are prioritized and delivered in a timely manner. Unlike a predictive approach, where the focus is often on completing tasks according to a strict plan, an iterative approach allows for flexibility and continuous improvement, ensuring the product better aligns with user needs and business objectives.

In Agile, flexibility and adaptability are key, especially when dealing with uncertain or changing requirements like evolving government regulations. The agile coach should ensure that the team is building the product incrementally, allowing for adjustments as needed. This way, when the regulatory changes occur, the team can adapt quickly without disrupting the entire release process. By focusing on delivering small, workable increments, the team can respond to changes more efficiently.

The purpose of the daily standup (or daily coordination meeting) is to help the development team stay aligned with the sprint goal and actively manage any risks or impediments that may be blocking progress. It allows the team to quickly discuss their progress, share potential issues, and identify dependencies that could affect the sprint ' s success. The focus is on team collaboration and ensuring that everyone is on track.

According to the PMI Agile Practice Guide (Section 7.2: Stakeholder Engagement), managing stakeholder expectations starts with establishing a shared vision and involving stakeholders in key activities like iteration reviews. This ensures transparency, feedback, and alignment on progress and priorities.

Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 4: Stakeholder Engagement) supports the idea that a common vision and shared goals foster trust and improve stakeholder relationships.

Option A is correct: a shared vision and active involvement lead to better stakeholder alignment.

Option B and C are partially right but limit collaboration or dismiss stakeholder input.

Option D is inconsistent with agile’s emphasis on open, continuous communication.

Distributed or remote teams are common in modern agile environments. According to the PMI Agile Practice Guide (Section 4.4 Working with Distributed Teams) and the PMBOK® Guide (6th Edition, Section 10.1), the agile practitioner must enable effective collaboration among all team members regardless of location. The guide recommends using video conferencing, collaborative workspaces, shared boards, and communication tools to simulate the benefits of co-location.

Mike Griffiths, in his PMI-ACP Exam Prep Book (Chapter 3: Team Performance), supports the use of collaboration tools to foster team cohesion and support agile values like communication and transparency, even when teams cannot be physically co-located.

Option A is correct: collaboration tools bridge the gap in distributed environments.

Option B and D promote siloing or team hierarchy, which undermines agile unity.

Option C moves away from agile values by emphasizing documentation over interaction.

The correct answer is D – It helps to quickly resolve issues using the sponsor ' s influence. A sponsor ' s presence in Scrum ceremonies (like sprint reviews or retrospectives) helps escalate and resolve high-level issues, remove organizational blockers, and reinforce alignment between the team and the business.

From the PMI Agile Practice Guide:

“Active sponsor engagement can accelerate issue resolution, remove organizational impediments, and provide vital support to the team. Sponsors are valuable allies in ensuring team success and organizational alignment.”

(PMI Agile Practice Guide, Section 4.2 – Stakeholder Engagement)

Mike Griffiths explains:

“When sponsors are visible and engaged, teams benefit from faster decision-making, quicker escalation of issues, and improved morale. Their influence can break through bureaucratic barriers.”

(Mike Griffiths, PMI-ACP Exam Prep, Chapter 3 – Stakeholder Engagement)

Incorrect options:

A misattributes sprint discipline to sponsor involvement—this is a team responsibility.

B is passive and doesn’t reflect tangible benefits.

C is useful but not the primary advantage of sponsor participation.

Answer: D

────────────────────────────────────

The correct answer is B – A product backlog should be created to list the project requirements from all of the project stakeholders.

In Agile, the product backlog serves as a living document where requirements, user stories, and stakeholder feedback are continuously refined. It is the central mechanism for capturing and prioritizing stakeholder needs and ensuring that business value is delivered incrementally.

From the PMI Agile Practice Guide:

“The product backlog is a prioritized list of work for the development team that is derived from stakeholder input, user stories, and emerging needs. It evolves as the project progresses and stakeholder feedback is incorporated.”

(PMI Agile Practice Guide, Section 5.2 – Product Backlog)

Mike Griffiths writes:

“Product backlogs provide transparency into stakeholder priorities. They enable the team to continuously align work with customer expectations and business needs.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 3 – Stakeholder Engagement)

Why the other options are incorrect:

A refers to the traditional project charter, which is not commonly updated throughout the agile life cycle.

C is a misunderstanding—the Agile Manifesto is a set of principles, not a project-specific document.

D misuses user stories; stories are used for functional requirements, not stakeholder profiles.

Answer: B

══════════════════════════════════════════════════

In Agile, building increments and ensuring early feedback are key to delivering value quickly and meeting tight deadlines. By focusing on delivering a minimum viable product (MVP), the team can provide the customer with a version of the product that delivers essential functionality early, which allows for feedback and adjustments before the final version is released. This approach helps the team stay within the limited budget and timeline while ensuring that they are delivering the most important features first. Additionally, early customer feedback ensures that the team is on track to meet the project goals and allows for the rapid adaptation of the product.

The correct answer is A — Establish and keep an active risk register that includes mitigation strategies and a cost-benefit analysis.

Risk management is essential to identifying and mitigating threats such as natural disasters. While Agile teams do not typically use traditional risk registers extensively, at the enterprise level (especially in regulated or high-risk environments), maintaining a risk register aligned with Agile values is appropriate. It should include mitigation options and their associated cost-benefit to guide decision-making.

PMI Agile Practice Guide states:

“Agile risk management practices include establishing lightweight mechanisms such as risk-adjusted backlog prioritization, risk registers (in high-risk or large programs), and risk mitigation strategies.”

(PMI Agile Practice Guide, Section 7.3 – Managing Risk in Agile Projects)

PMBOK® Guide (6th Edition) supports this:

“The risk register is a critical project artifact that includes identified risks, their analysis, mitigation or response plans, and cost-benefit considerations for managing risks.”

Incorrect options:

B lacks the inclusion of mitigation strategies and full cost analysis.

C refers to surface-level risk visibility, not comprehensive risk planning.

D assumes avoidance is the only mitigation strategy, which is not always feasible or optimal.

Answer: A

—

The correct answer is B because agile approaches prioritize continuous stakeholder engagement, collaboration, and adaptive communication strategies. When stakeholder roles are redefined due to an organizational restructure, the agile team should proactively and directly engage with the newly impacted stakeholders to clarify expectations, responsibilities, and to maintain alignment with evolving needs.

The PMI Agile Practice Guide states:

“Engaging stakeholders directly and frequently fosters a shared understanding of objectives and priorities. Two-way communication, such as conversations and collaboration sessions, is preferred over one-way communication such as reports or status updates.”

(PMI Agile Practice Guide, Section 4.2 – Stakeholder Engagement)

In addition, Mike Griffiths’ PMI-ACP Exam Prep Book supports this approach by highlighting:

“An agile team should regularly revisit and refresh stakeholder analysis. When changes occur in the stakeholder landscape, it ' s essential to revalidate stakeholder needs through open, two-way communication, rather than assuming static roles.”

(Mike Griffiths, Chapter 3 – Value-Driven Delivery / Stakeholder Engagement)

Options A, C, and D fail to incorporate agile’s emphasis on direct engagement and collaboration. Option D, while partially correct, lacks the proactive communication component that agile requires. Option C suggests a passive communication method (email), which is discouraged in agile practices for important stakeholder interactions.

Therefore, the best agile-aligned choice is: B

The correct answer is A – Add a task to the product backlog to allow the team time to investigate and experiment prior to estimating.

When the team lacks experience or clarity around a new feature or technical solution, they should perform a time-boxed research activity, known as a spike. Spikes allow the team to explore unknowns, validate assumptions, and gather information needed to provide accurate estimates.

From the PMI Agile Practice Guide:

“When the team is unable to estimate due to uncertainty, a spike can be added to the backlog. This allows time for research, experimentation, or prototyping to enable informed estimation.”

(PMI Agile Practice Guide, Section 5.3 – Adaptive Planning)

Mike Griffiths also writes:

“Spikes are used to investigate technical or functional elements. A spike helps reduce uncertainty and informs future planning and estimation.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 5 – Adaptive Planning)

Why other options are less effective:

B (Wideband Delphi), C (Planning Poker), and D (Three-point estimation) are techniques for estimation, not suitable when the team lacks enough information to estimate in the first place.

Answer: A

══════════════════════════════════════════════════

Reducing test automation in agile undermines quality and slows down feedback loops, contradicting agile principles. According to the PMI Agile Practice Guide (Section 5.5 Quality Management in Agile Projects) and PMBOK® Guide (6th Edition, Section 8.1), agile projects aim for built-in quality, and test automation is critical in achieving that.

Mike Griffiths (PMI-ACP Exam Prep Book, Chapter 6: Value-Driven Delivery) strongly advocates for test automation to support sustainable development and improve predictability, quality, and speed. Rather than comply blindly with the product owner’s request, the agile practitioner should engage stakeholders and clarify the long-term trade-offs of reducing quality practices.

Option A is correct: consulting stakeholders ensures transparency, alignment, and helps prevent short-sighted compromises that could undermine the product.

The correct answer is D – Communicate the risk of a negative ROI to the stakeholders, and update the release plan. Agile values transparency and collaboration. When the team identifies risks to business outcomes such as ROI, they must promptly inform stakeholders and work collaboratively to reassess scope, value, and strategy.

From the PMI Agile Practice Guide:

“Agile teams provide ongoing visibility to stakeholders. If delivery metrics reveal financial concerns, the product owner and stakeholders evaluate whether to pivot, persevere, or stop.”

(PMI Agile Practice Guide, Section 3.4 – Value-Driven Delivery and Transparency)

Mike Griffiths adds:

“Agile planning is value-based. If ROI is unlikely to be achieved, stakeholders must be informed early so informed decisions can be made.”

(Mike Griffiths, PMI-ACP Exam Prep, Chapter 3 – Value-Driven Delivery)

Incorrect options:

A assumes trimming scope is sufficient without stakeholder input.

B contradicts team stability and morale principles.

C helps identify inefficiencies but doesn’t replace transparency.

Answer: D

The agile lead should evaluate the team ' s capacity and help them select user stories that align with around 80% of their available capacity for the iteration. This approach takes into account potential issues or interruptions and helps ensure the team is not overcommitting. By selecting user stories based on a realistic understanding of the team’s capacity, the team is more likely to meet their commitments and avoid incomplete work. This method promotes sustainable work practices and helps the team maintain a predictable velocity over time.

Pull communication is most effective for a distributed team working across multiple locations, especially when task-oriented communications and discussion boards are involved. With pull communication, team members can access information when needed, such as through shared documents, wikis, or discussion boards. This ensures that communication is effective and available asynchronously, allowing the team to collaborate and stay informed without needing to be online at the same time. This method is particularly useful when managing a geographically dispersed team.

The correct answer is C — Ask the team member to update daily progress on the information radiators.

In Agile, transparency and self-organization are key. Information radiators (e.g., task boards, digital dashboards) allow all team members and stakeholders to see the current state of work at any time. If a team member cannot attend stand-ups, they should still update their tasks on the board so that others are informed.

PMI Agile Practice Guide:

“Information radiators ensure transparent communication of progress, risks, and blockers to all team members and stakeholders. These should be updated in real-time or daily by those responsible.”

(PMI Agile Practice Guide, Section 5.6 – Information Radiators)

Mike Griffiths:

“Task boards and progress charts allow anyone to see project status without waiting for meetings. Team members must take responsibility for keeping them current.”

(PMI-ACP Exam Prep, Chapter 5 – Adaptive Planning)

Incorrect options:

A punishes the team for one member’s lack of participation and doesn’t solve the communication issue.

B reintroduces a command-and-control model, reducing team ownership.

D is dishonest and violates agile principles of transparency.

Answer: C

—

Step 1: Identify Remaining MVP Story Points

The backlog lists the MVP-related stories that are not yet started:

Accessibility – color blind → 4 story points

Increase security → 21 story points

Add AI chatbot → 5 story points

Total remaining MVP story points = 4 + 21 + 5 = 30

Step 2: Consider Velocity and Sprint Progress

The risk register mentions a reduction of 1 story point per sprint from sprints 4 through 6 due to the holiday schedule.

If we assume the team ' s normal velocity is 10 story points per sprint (hypothetically), it would drop to 9 story points per sprint for sprints 4-6.

Step 3: Calculate Completion Sprint

If the team normally completes 10 story points per sprint, they would require approximately 3 sprints (Sprint 7, Sprint 8, and Sprint 9) to complete the remaining 30 story points.

The principles of Extreme Programming (XP) focus on improving software quality and responsiveness to changing customer requirements. The key principles include:

Rapid feedback: Getting feedback quickly from customers or stakeholders to ensure that the development process is on track.

Assume simplicity: Focusing on simplicity in the design and code to avoid overengineering and to ensure the software is easy to understand and modify.

Incremental change: Delivering software in small, manageable increments that can be easily adjusted based on feedback.

Embrace change: Being flexible and adaptable, especially in response to new requirements or changes in technology or business needs.

Quality work: Ensuring high-quality software by emphasizing practices such as automated testing, continuous integration, and refactoring.

The correct answer is C – Show the stakeholder the progress radiators for the project.

Progress radiators, such as task boards, burndown charts, and Kanban boards, visually communicate the status of work in progress, completed items, and remaining scope. They are effective tools for quickly bringing stakeholders up to speed without interrupting the team or requiring extensive reporting.

From the PMI Agile Practice Guide:

“Progress is tracked and made visible using information radiators such as burndown charts, task boards, and velocity charts. These tools allow stakeholders to monitor project health in real time.”

(PMI Agile Practice Guide, Section 3.5 – Information Radiators)

Mike Griffiths emphasizes:

“Transparency and visibility are essential in agile. Information radiators keep stakeholders informed and promote collaboration without relying on status reports.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 5 – Agile Monitoring and Control)

Other options explained:

A and D offer limited insights or are inappropriate for immediate understanding.

B is valuable but time-limited; radiators provide continuous insight.

Answer: C

══════════════════════════════════════════════════

Agile fosters a safe-to-fail environment where experimentation is encouraged. According to the PMI Agile Practice Guide (Section 5.6: Retrospectives and Process Improvement) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 7: Continuous Improvement), teams should be empowered to test new ideas and learn from outcomes, regardless of whether those experiments succeed or fail.

Option D is correct: promoting experimentation supports learning and innovation.

Option A discourages risk-taking and limits growth.

Option B creates fear and undermines psychological safety.

Option C mixes accountability with experimentation, which can discourage honest learning.

The correct answer is D because organizational transformation to agile requires more than process changes—it requires a shift in mindset. Training teams on agile values and principles builds a shared foundation and helps foster commitment to agile ways of working.

From PMI Agile Practice Guide:

“Agile transformation requires attention to both practices and mindset. Leaders must help teams embrace agile values, empower decision-making, and promote an agile culture through education and active support.”

(PMI Agile Practice Guide, Section 2.1 – Organizational Change and Transformation)

From PMBOK® Guide – 7th Edition:

“Successful transformation begins with people understanding the why and how of agile. Change cannot happen effectively without adequate training and communication.”

(PMBOK Guide 7th Ed., Principle 1 – Be a Diligent, Respectful, and Caring Steward)

From Mike Griffiths’ PMI-ACP Exam Prep Book:

“Agile success is rooted in the team’s understanding of core principles. Agile leaders must invest in developing a strong foundational mindset, as well as practices. Education is a critical enabler of sustainable agile adoption.”

(Mike Griffiths, Chapter 1 – Agile Principles and Mindset)

Option A is a partial strategy but doesn’t ensure cultural transformation.

Option B is necessary but not sufficient—buy-in alone won’t change behavior.

Option C is tactical and useful but doesn’t address team-wide mindset change.

Answer: D

The best answer is B because agile teams should use frequent feedback, customer data, and learning to adapt priorities. The problem is that teams are continuing to invest in low-adoption features because feedback is reviewed too late. Integrating usage analytics into prioritization creates a shorter feedback loop and supports value-based decision-making.

Option A improves review frequency but still keeps decisions at an executive review level rather than embedding feedback into the team’s prioritization process. Option C shifts decision-making to regional managers, but agile prioritization should still consider product value, customer outcomes, and team learning. Option D focuses on output rather than outcome; delivering more features does not necessarily reduce churn or improve value.

PMI-ACP topics emphasize maximizing value, adapting to feedback, engaging stakeholders early, and using empirical information to improve future increments.

=========

The correct answer is B – Lack of shared knowledge of user stories.

Distributed teams face challenges in collaboration, knowledge sharing, and communication. Without regular interaction, team members may not fully understand user stories, acceptance criteria, or customer needs. This leads to misalignment and potentially lower-quality outputs.

From the PMI Agile Practice Guide:

“Distributed teams face barriers to communication and knowledge sharing. Agile teams must use collaboration tools and practices to ensure that all members share an understanding of the user stories and priorities.”

(PMI Agile Practice Guide, Section 2.3 – Agile Team Communication)

Mike Griffiths explains:

“Remote Agile teams must work harder to ensure clarity in user stories and maintain shared understanding. Without this, misunderstandings increase.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 4 – Team Performance)

Other options:

A (frequent integration) is a benefit, not a risk.

C is irrelevant to Agile effectiveness.

D is less common with Agile roles clearly defined (PO, SM, Dev Team).

Answer: B

═════════

The best answer is D because the project lead should foster psychological safety. In agile teams, people need to feel safe to share opinions, challenge ideas, raise concerns, and provide feedback without fear of blame, embarrassment, or punishment. This is especially important in international or cross-cultural teams where communication styles may differ.

Option A may help with meeting structure, but emphasizing rules does not necessarily make people feel safe. Option B is passive and may allow silence to continue. Option C may help in some cases, but separate meetings do not solve the root issue in team discussions. Option D directly addresses the problem by improving the team environment.

PMI-ACP explicitly includes fostering psychological safety, encouraging dialogue, soliciting constructive feedback, and promoting a collaborative team environment.

=========

The team lead should work to resolve the conflict by negotiating with the project director. Since the lead developer cannot complete their work due to the request for a detailed testing plan, the team lead should seek to limit the scope of the documentation request. By negotiating for fewer details or a reduced scope of testing documentation, the team can continue their work on the iteration while still meeting the project director ' s needs. This approach balances the need to progress with development and address the request without causing significant delays.

The correct answer is B – Discuss the issue with the team in the daily stand-up meetings. Agile emphasizes transparency, collaboration, and self-organization. The daily stand-up is an appropriate forum to raise and discuss workload distribution so the team can adjust and support each other.

From the PMI Agile Practice Guide:

“Daily stand-ups are a tool for fostering open communication, uncovering impediments, and adjusting the plan for the day. It enables the team to help each other balance workloads and remove bottlenecks.”

(PMI Agile Practice Guide, Section 5.2 – Daily Stand-Ups)

Mike Griffiths explains:

“Team members should use stand-ups to discuss challenges. If someone is overloaded, the team can identify ways to redistribute work to maintain balance and avoid burnout.”

(Mike Griffiths, PMI-ACP Exam Prep, Chapter 4 – Team Performance)

Incorrect options:

A escalates the issue unnecessarily and bypasses team self-management.

C is too narrow and private for a team-based issue.

D adds administrative burden without solving the underlying problem.

Answer: B

────────────────────────────────────

The correct answer is A – Jointly meet with the team and product owner to discuss options and determine the end date. Agile promotes collaborative decision-making. When significant changes in performance arise, discussions should occur between the team and product owner to assess impact, explore value delivery, and make informed decisions.

From the PMI Agile Practice Guide:

“Agile teams regularly review performance trends. Changes in velocity should prompt discussions between the team and product owner to evaluate implications and opportunities.”

(PMI Agile Practice Guide, Section 5.4 – Release Planning)

Mike Griffiths states:

“Forecasting must remain collaborative. Teams and product owners work together to determine whether to ship early, expand scope, or adjust timelines.”

(Mike Griffiths, PMI-ACP Exam Prep, Chapter 5 – Adaptive Planning)

Incorrect options:

B skips stakeholder collaboration.

C assumes backlog expansion without value validation.

D contradicts agile principles of delivering value early.

Answer: A

────────────────────────────────────

The correct answer is B — Organize training and development workshops to help all stakeholders form a shared understanding of agile practices.

Agile transformation requires not only role assignment but a cultural shift and shared mindset. Providing training and development for all stakeholders—including team members, managers, and leadership—builds a common understanding of agile principles, frameworks, and expectations.

PMI Agile Practice Guide:

“Agile adoption requires training, mentoring, and coaching. It is critical that all team members and stakeholders share an understanding of agile principles and practices to foster alignment and collaboration.”

(PMI Agile Practice Guide, Section 6.5 – Organizational Change and Culture)

Mike Griffiths:

“Effective adoption of agile requires both technical and cultural onboarding. Training everyone—not just technical team members—is essential for creating a cohesive, aligned agile environment.”

(PMI-ACP Exam Prep, Chapter 1 – Agile Principles and Mindset)

Incorrect options:

A focuses only on assigning roles, which is insufficient without foundational understanding.

C is a good long-term step but doesn’t directly support the immediate team-level transition.

D limits agile adoption and fails to support holistic team capability-building.

Answer: B

—

When the team is uncertain about a technical solution, a spike—a timeboxed research task—is used to explore possible approaches. The PMI Agile Practice Guide (Section 5.2: Spikes) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning) recommend spikes as a formal way to explore unknowns and reduce risk in the backlog.

Option B is correct: spikes provide structure for resolving uncertainty.

Option A ignores the technical risk.

Option C disrupts team structure and ownership.

Option D defers the problem without seeking resolution.

One of the pillars of agile is early and continuous customer feedback to ensure that the product being delivered meets stakeholder expectations. According to the PMI Agile Practice Guide (Section 5.3: Reviews and Feedback Loops) and Mike Griffiths ' PMI-ACP Exam Prep Book (Chapter 4: Stakeholder Engagement), frequent customer reviews (e.g., sprint reviews) ensure alignment and early identification of quality or value issues.

Option D is correct: regular customer engagement during reviews ensures delivery effectiveness and customer satisfaction.

Option A is inappropriate—daily stand-ups are for internal team coordination.

Option B reflects a waterfall approach.

Option C misplaces the responsibility—requirements evolve and are refined throughout, not fixed up front.

In Agile, it ' s important to maintain focus on the current sprint ' s goals and scope. Since the sprint deadline is approaching, adding additional features may compromise the team ' s ability to deliver the planned work on time. The best approach is to explain to the client that the new features can be considered for the next sprint, ensuring that the team can finish the current work and deliver value on time. This also allows the team to properly plan for the new features in the next iteration without overloading the current sprint.

Upon joining a team, a Scrum Master should focus on facilitating team collaboration, removing impediments, and creating a psychologically safe space. The PMI Agile Practice Guide (Section 3.3: Scrum Master Role) and Mike Griffiths (Chapter 3: Team Performance) stress that early efforts should center on servant leadership, helping the team identify and solve their own challenges.

Option C is correct: supporting the team through facilitation reflects the core role of a Scrum Master.

Option A is prescriptive and not aligned with cross-functional team philosophy.

Option B may be necessary later, but first, trust and team dynamics must be established.

Option D falls under the Product Owner’s responsibility, not the Scrum Master’s.

The correct answer is A — Stakeholders should have regularly been engaged to obtain feedback and reduce the functionality risk.

In Agile, stakeholder engagement and iterative feedback loops ensure that the solution being built is aligned with business value. Simply meeting documented requirements is insufficient. Agile practices such as demos and user feedback sessions minimize the risk of building features that fail to deliver value.

PMI Agile Practice Guide:

“Agile emphasizes ongoing stakeholder engagement. Demonstrating working software at the end of each iteration and gathering feedback ensures that the product is delivering business value.”

(PMI Agile Practice Guide, Section 4.2 – Stakeholder Engagement)

Mike Griffiths states:

“Value-driven delivery is achieved not just by delivering what was asked for, but by ensuring it actually meets customer needs. Regular feedback from stakeholders is critical to avoid building low-value features.”

(PMI-ACP Exam Prep, Chapter 3 – Value-Driven Delivery)

Incorrect options:

B refers to the lean principle of “decide as late as possible,” but feedback, not delay, would have addressed the issue.

C is unrelated to this context.

D lacks the collaborative engagement approach emphasized in Agile.

Answer: A

—

Analyzing the burndown chart, we see:

Points Planned (gray squares): decreasing steadily from 50 to 0 over 10 days (ideal burn).

Points Completed (gray triangles): plateau between days 3–6, lagging significantly behind planned completion.

This indicates that the team is behind schedule, and unless they accelerate, they may fail to complete all committed work.

According to the PMI Agile Practice Guide (Section 5.4: Burndown Charts) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 6: Monitoring Progress), such divergence between the ideal and actual burn lines indicates that the iteration is at risk.

Option A is correct: the iteration is in jeopardy due to lack of progress mid-sprint.

Option B is incorrect—scope removal would show a downward shift in planned points.

Option C is false—the team is behind, not ahead.

Option D is misleading—velocity appears inconsistent (e.g., plateau from day 3–6).

The correct answer is A – Reduced or improper customer collaboration.

One of the core principles of Agile is continuous collaboration with the customer. If multiple feature changes are only identified during a late-stage review, it typically indicates that the customer was not involved sufficiently throughout the development process.

From the Agile Manifesto (cited in the PMI Agile Practice Guide):

“Customer collaboration over contract negotiation.”

“Working software is delivered frequently… with a preference to the shorter timescale.”

And from the PMI Agile Practice Guide:

“Ongoing engagement with the customer helps align product features with actual needs and reduce surprises during late-stage reviews.”

(PMI Agile Practice Guide, Section 4.2 – Stakeholder Engagement)

Mike Griffiths also emphasizes:

“When customers are involved in iteration reviews and backlog grooming, their evolving needs are captured in real time. Surprises during release reviews usually reflect a failure of ongoing communication.”

(Mike Griffiths, Chapter 3 – Value-Driven Delivery)

Other options don’t directly address the root cause:

B may contribute, but customer collaboration is the key differentiator in agile.

C and D are traditional causes of waterfall-style failure, not typically root causes in agile.

Answer: A

‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾

Gold-plating—adding extra features not requested or prioritized—is an anti-pattern in agile. Agile emphasizes delivering the highest-priority features first, and product changes should always go through the Product Owner for prioritization and validation.

According to the PMI Agile Practice Guide (Section 5.1: Backlog and Value Delivery) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 6: Value-Driven Delivery), when capacity is available, the team should pull more stories from the prioritized backlog, ensuring that all work aligns with stakeholder-defined value.

Option D is correct: confirm backlog priority and use time to deliver customer-prioritized value.

Option A supports scope creep.

Option B is partially correct but doesn’t optimize the time to deliver value.

Option C perpetuates gold-plating and undermines value alignment.

The correct answer is A – Conduct regular one-on-one meetings to review development features and trace them back to the product roadmap. Close collaboration between the agile leader (e.g., Scrum Master or Project Lead) and the Product Owner ensures alignment between the product strategy and development execution.

From the PMI Agile Practice Guide:

“Frequent and open collaboration between the Product Owner and agile project leader helps maintain alignment between delivery and business objectives. These discussions link work to roadmap-level planning.”

(PMI Agile Practice Guide, Section 4.2 – Stakeholder Engagement)

Mike Griffiths states:

“Agile leadership includes partnering with the Product Owner to ensure that work being done contributes to overall product goals. Roadmap alignment is critical.”

(Mike Griffiths, PMI-ACP Exam Prep, Chapter 3 – Stakeholder Engagement)

Incorrect options:

B is more appropriate for the Product Owner, not the project leader.

C implies waterfall-style communication.

D oversteps the Product Owner’s authority in setting feature priorities.

Answer: A

────────────────────────────────────

The correct answer is B – Break the story up and focus on the most valuable parts. Agile promotes progressive elaboration, and large or complex stories (epics) should be broken down into smaller, testable user stories. This practice enables clarity, faster feedback, and more accurate planning.

From the PMI Agile Practice Guide:

“Large stories (epics) should be split into smaller user stories to enable understanding, estimation, and incremental delivery. Stories should be small enough to be completed within an iteration.”

(PMI Agile Practice Guide, Section 5.3 – User Stories and Story Splitting)

Mike Griffiths states:

“When a user story is too large or unclear, the team should break it down into smaller pieces, focusing on the most valuable parts first. Story splitting is a key agile practice.”

(Mike Griffiths, PMI-ACP Exam Prep, Chapter 5 – Adaptive Planning)

Incorrect options:

A discourages collaboration and learning.

C delays the resolution unnecessarily.

D avoids solving the actual problem and abandons valuable work.

Answer: B

────────────────────────────────────

In an Agile environment, fostering a culture of collaboration and effective communication is key to success, especially when working with a diverse team. By creating a shared vision, the project manager aligns the team towards common goals, which helps reduce misunderstandings. Using techniques to increase empathy and positive interaction ensures that team members understand and respect each other ' s different perspectives. This approach promotes a collaborative environment where diverse ideas can be valued and conflicts can be addressed constructively.

The correct answer is D — Facilitate a team retrospective.

A drop in team morale and performance signals the need for a structured conversation where the team can reflect, diagnose root causes, and propose changes. Retrospectives are the Agile mechanism for identifying and addressing performance issues in a collaborative, non-blaming environment.

PMI Agile Practice Guide:

“Retrospectives allow teams to reflect on their performance, discuss what ' s working or not, and commit to improvement actions. This is the key mechanism for continuous team development.”

(PMI Agile Practice Guide, Section 5.8 – Retrospectives)

Mike Griffiths affirms:

“Team disengagement often stems from unresolved issues or lack of empowerment. Retrospectives are critical for rebuilding engagement, trust, and improving team dynamics.”

(PMI-ACP Exam Prep, Chapter 4 – Team Performance)

Incorrect options:

A skips team-level resolution and risks undermining trust.

B manipulates metrics without solving the root problem.

C is useful for daily progress updates but not for deep reflection.

Answer: D

—

—

In an adaptive approach to project management, particularly in agile, empowering team leads to manage their teams’ issues and impediments is a key practice. This allows for more autonomy within the teams, ensures that obstacles are handled promptly, and promotes frequent communication among team leads. By giving the leads the authority to resolve issues, they can ensure smooth collaboration across cross-functional teams and maintain alignment with the overall project goals.

To ensure that the service will benefit the customer and meet their requirements, the product owner should build a prototype. Prototypes allow the team to create an early, low-fidelity version of the product that can be used to gather direct feedback from the targeted customer segment. This helps to validate whether the service aligns with the customer ' s needs and expectations before investing heavily in full development.

Servant leadership is about supporting the team, empowering them, and ensuring they have what they need to succeed. The team leader should focus on removing impediments that block the team ' s progress. By doing so, the leader enables the team to work more efficiently and effectively, without being obstructed by recurring issues. This aligns with the servant leadership mindset of putting the team ' s needs first and helping them reach their goals.

The correct answer is C – Facilitate a conversation about the user story between the development team and the product owner. In Agile, collaboration, self-organization, and face-to-face conversation are foundational principles for resolving disagreements and achieving a shared understanding.

According to the PMI Agile Practice Guide:

“The agile practitioner facilitates healthy communication and constructive dialogue between the product owner and the development team to align understanding and priorities. Agile coaches and Scrum Masters serve the team by removing obstacles to collaboration, not by acting as decision-makers.”

(PMI Agile Practice Guide, Section 6.3 – Facilitating Agile Practices)

Further, the guide emphasizes:

“Effective teams discuss issues collaboratively. When disagreements arise, the agile leader’s role is to facilitate communication and resolution through shared understanding, not to dictate decisions.”

(PMI Agile Practice Guide, Section 4.1 – Agile Mindset and Behaviors)

Mike Griffiths’ PMI-ACP Exam Prep Book also states:

“Agile encourages close collaboration between business and technical teams. When conflicts arise regarding a user story, the agile practitioner’s role is to facilitate meaningful discussions to ensure mutual understanding and team-driven resolution.”

(Mike Griffiths, Chapter 4 – Team Performance)

Why the other options are incorrect:

A undermines team self-organization and implies a command-and-control model.

B is confrontational and goes against agile values of respect and collaboration.

D contradicts the facilitative role of the agile practitioner, who should not act as an authoritative decision-maker.

Thus, the most agile-consistent approach is to enable conversation and clarity between roles.

Answer: C

When a team reports that user stories are unclear or lack sufficient detail, the correct agile response is to foster collaborative refinement and shared understanding. A user story workshop is a well-recognized practice that involves the team and product owner collaborating to write, clarify, and refine stories. This is supported by the PMI Agile Practice Guide (Section 5.2: User Stories and Backlog Refinement), which recommends story-writing workshops as a proactive way to clarify requirements.

Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning) notes that good agile teams collaboratively refine stories in grooming sessions or workshops to ensure shared clarity and alignment.

Option C is correct: a workshop enables both the team and product owner to collaborate in improving story clarity.

Option A oversimplifies the solution—acceptance criteria alone don’t fully define a story.

Option B misuses the retrospective, which is for process improvement, not story editing.

Option D escalates prematurely and undermines team ownership and collaboration.

The correct answer is D — Identify this as a risk, decide on the response, and prioritize spike to determine the solution on the product backlog.

A spike is a time-boxed research activity used in Agile to explore potential solutions to uncertainty. The architectural concern is a technical risk, and it ' s best addressed by formally identifying it, analyzing potential responses, and scheduling a spike as a backlog item to investigate solutions.

PMI Agile Practice Guide:

“Spikes are stories used for time-boxed research and exploration when the team needs more information to understand technical or functional uncertainty.”

(PMI Agile Practice Guide, Section 5.2 – Types of Backlog Items)

Mike Griffiths:

“Agile risk management integrates spikes and prioritization. When risk is detected, the team should identify it transparently and explore mitigation or investigation through a spike.”

(PMI-ACP Exam Prep, Chapter 6 – Problem Detection and Resolution)

Incorrect options:

A skips backlog prioritization and team alignment.

B deflects the issue without analysis.

C ignores risk and blindly follows the existing priority.

Answer: D

—

The correct answer is A – Be transparent with all the stakeholders and make them aware of the issues encountered and the current project ' s status.

Agile encourages transparency and regular stakeholder engagement to ensure alignment and avoid surprises. Even if a stakeholder prefers minimal involvement, it is the team’s responsibility to raise issues that could impact delivery, especially if they introduce risk or require input.

From the PMI Agile Practice Guide:

“Agile promotes transparency and ongoing stakeholder engagement. Teams should proactively communicate risks and emerging issues to build trust and enable timely decision-making.”

(PMI Agile Practice Guide, Section 4.2 – Stakeholder Engagement)

Mike Griffiths notes:

“Transparency is one of the pillars of Agile. Teams must keep stakeholders informed—even those who prefer limited involvement—to ensure that value is continuously delivered.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 3 – Stakeholder Engagement)

Other options explained:

B is a secondary action; transparency should come first.

C risks late discovery and undermines agile values.

D removes responsibility from the team, which contradicts self-management.

Answer: A

═════════════

Based on the velocity chart, the team has completed 43, 42, 44, and 46 story points in previous sprints. The average number of completed story points is 43.75, and committing to 44 story points for the upcoming sprint aligns closely with this average. It offers a realistic target that takes into account the team ' s capacity while providing a reasonable chance of completing the planned work within the sprint.

When transitioning to an iterative development lifecycle, it’s crucial to ensure that user stories are written with clear, testable acceptance criteria that define the desired outcomes. The agile lead should explain to the project sponsor that the subject matter expert (SME) needs to collaborate with the team, including developers, testers, and the product owner, to ensure everyone has a shared understanding of the requirements and the solution. This collaboration is essential for defining and refining the user stories to ensure that they deliver value and meet the needs of the stakeholders.

The correct answer is C – Determine who is best qualified to address the challenges. Agile teams are self-organizing and empowered to make technical decisions. When challenges arise, the team collaboratively identifies who is best suited to resolve issues, rather than relying on external direction or top-down task assignment.

From the PMI Agile Practice Guide:

“Agile teams are self-organizing. When challenges or new work arises, the team decides how to proceed, including task allocation based on skills and availability.”

(PMI Agile Practice Guide, Section 4.3 – Self-Organization)

Mike Griffiths also notes:

“Team members decide how work is divided and who tackles what. When technical complexity is involved, those with relevant expertise are encouraged to step in, with support from the rest of the team.”

(Mike Griffiths, PMI-ACP Exam Prep, Chapter 4 – Team Performance)

Incorrect options:

A violates the principle of team autonomy.

B delays delivery rather than solving the problem.

D incorrectly places the Product Owner in a team management role.

Answer: C

According to the PMI Agile Practice Guide (Section 7.1 Communication) and PMBOK® Guide (6th Edition, Section 13.3 Manage Stakeholder Engagement), transparency with stakeholders is fundamental in agile environments. Delays or deviations from expected outcomes must be promptly communicated to affected stakeholders to adjust expectations and plans.

Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 4: Stakeholder Engagement) emphasizes that one of the key values in agile is responding to change over following a plan, and that includes openly discussing risks and delays with impacted parties.

Thus, Option D is correct: the agile coach should proactively engage marketing stakeholders to inform them about the delay and support revised planning.

The correct answer is C — During the retrospective, discuss the issue and create an action plan to avoid it in the future.

When teams misestimate or experience incomplete work, it’s important to reflect during the retrospective and create action items. This is a fundamental aspect of agile: continuous inspection, adaptation, and team-driven improvement.

PMI Agile Practice Guide:

“Retrospectives help identify opportunities for improvement. The team reviews its estimation accuracy and adjusts processes or practices based on patterns observed.”

(PMI Agile Practice Guide, Section 5.8 — Retrospectives)

Mike Griffiths elaborates:

“Estimating complexity is an area for ongoing learning. Teams use retrospectives to improve their sizing, identify knowledge gaps, and refine their planning techniques.”

(PMI-ACP Exam Prep, Chapter 5 — Adaptive Planning)

Other options:

A unnecessarily involves a project manager (non-agile).

B assumes one-size-fits-all rules, which limits team agility.

D ignores the structured opportunity the retrospective provides for team learning.

Answer: C

—

The correct answer is A – Use an information radiator to help increase the transparency of work for key stakeholders.

Information radiators (such as Kanban boards, burndown charts, and story maps) make work status visible to the entire team and stakeholders in real-time, improving communication without additional meetings or reporting overhead.

From the PMI Agile Practice Guide:

“Agile teams use information radiators to promote transparency, show progress, and increase stakeholder engagement without adding administrative burden.”

(PMI Agile Practice Guide, Section 3.5 – Information Radiators)

Mike Griffiths confirms:

“Effective agile environments display work status where everyone can see it. Visual indicators allow stakeholders and team members to remain informed without direct queries.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 5 – Agile Monitoring and Control)

Other options explained:

B creates unnecessary manual effort.

C may disrupt team rhythm; daily stand-ups are sufficient in Scrum.

D encourages siloed behavior and contradicts collaboration.

Answer: A

══════════════════════════════════════════════════

The daily standup is focused on ensuring the team stays synchronized on their commitments for the sprint, and it is meant to be a short meeting where team members quickly discuss what they did the previous day, what they plan to do today, and any blockers they are facing. It is not a forum for external stakeholders to ask detailed questions about the sprint backlog or delivery timelines, as this can disrupt the team ' s focus and hinder the meeting ' s efficiency.

By explaining that the standup is about synchronizing commitments, the project manager helps the business partners understand the purpose of the meeting and suggests an appropriate time and place for discussing more detailed or strategic topics.

Agile relies on regular retrospectives to reflect, adapt, and implement improvements. According to the PMI Agile Practice Guide (Section 5.6 Retrospectives), teams should continuously inspect their process and collectively own the changes needed to improve. This supports a culture of learning and accountability.

Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 7: Continuous Improvement) encourages frequent retrospectives that include open discussion and shared responsibility for change implementation.

Option A is correct: holding retrospectives and collaborating on actions promotes ownership and progress.

Option B neglects process change.

Option C limits transparency and team collaboration.

Option D addresses trust but not the recurring problems.

According to the PMI Agile Practice Guide (Section 7.2.1), the Scrum Master’s role includes removing impediments and shielding the team from outside interference. A team member being pulled into work on a different project is a classic example of an impediment. Recording the issue in a risk register is appropriate, but more importantly, the Scrum Master must communicate and resolve the issue.

Mike Griffiths in his PMI-ACP Exam Prep Book (Chapter 3: Team Performance) emphasizes that agile teams require full dedication and protection from context switching, as multitasking reduces productivity and increases error rates. Merely documenting the issue is not enough—the Scrum Master must take steps to escalate and resolve the interference, potentially by negotiating with the former supervisor or re-clarifying role boundaries.

Therefore, Option C is correct as it involves actively addressing the threat rather than passively monitoring or adjusting around it.

The correct answer is A – Prioritize the stakeholder feedback, considering the impact on strategic objectives and current workload, and discuss these priorities with the team in the next sprint planning meeting to collaboratively decide on the next steps.

Agile promotes adaptive planning and continuous stakeholder engagement. While feedback is highly valuable, especially from a sprint review, changes to the product backlog must be carefully prioritized and collaboratively discussed with the team. The product owner’s responsibility is to maintain and refine the backlog, ensuring alignment with stakeholder needs while also preserving team focus and avoiding unnecessary disruption during an ongoing sprint.

From the PMI Agile Practice Guide:

“Product backlog refinement is an ongoing process in which the product owner and the team collaborate on the details of backlog items. This includes analyzing, estimating, and prioritizing items to reflect the latest feedback and business needs.”

(PMI Agile Practice Guide, Section 5.2 – Product Backlog Refinement)

“Agile teams embrace change, especially when it delivers value. However, they also maintain sustainable pace and focus by avoiding mid-sprint scope changes unless absolutely necessary. Backlog items are reviewed and reprioritized before the next sprint begins.”

(PMI Agile Practice Guide, Section 3.4 – Value-Driven Delivery)

From Mike Griffiths’ PMI-ACP Exam Prep Book:

“While agile encourages responding to change, disrupting sprint commitments can erode team trust and productivity. Sprint planning is the correct forum to reprioritize work based on new stakeholder insights.”

(Mike Griffiths, Chapter 5 – Adaptive Planning)

Why the other options are incorrect:

B introduces mid-sprint disruption and disregards agile best practices for maintaining sprint integrity and team focus.

C eliminates team collaboration and risks breakdowns in communication, violating agile’s emphasis on transparency and teamwork.

D disregards valuable feedback and delays addressing important stakeholder needs, which could compromise customer satisfaction and strategic alignment.

Answer: A

──────

The correct answer is A – Speak to the agile lead about the concerns.

Agile encourages transparency, collaboration, and open communication across all levels of the team. If a team member identifies a risk or concern, the most agile-aligned approach is to raise it directly and constructively with the agile lead or Scrum Master, who is responsible for protecting the team and facilitating problem-solving.

From the PMI Agile Practice Guide:

“Agile teams promote a culture of openness where team members are encouraged to speak up and raise concerns. Effective leadership listens and collaborates to resolve issues.”

(PMI Agile Practice Guide, Section 4.1 – Agile Mindset)

Mike Griffiths further adds:

“Team members should be empowered to express concerns and challenge assumptions respectfully. Continuous communication and feedback improve project outcomes.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 4 – Team Performance)

Why the other options are not ideal:

B promotes blind compliance, which is contrary to agile empowerment.

C suggests overwork, which contradicts sustainable pace.

D may escalate unnecessarily without first engaging the proper leadership channel.

Answer: A

══════════════════════════════════════════════════

The correct answer is C – Conduct retrospectives at the end of every sprint.

According to the Agile framework, regular retrospectives are a key practice to inspect and adapt the process. If team members have concerns about the Scrum Master ' s processes, the appropriate time and space to bring up and resolve such issues is the Sprint Retrospective.

From the PMI Agile Practice Guide:

“Retrospectives are a time-boxed event that enables the team to inspect itself and create a plan for improvements to be enacted during the next iteration. It provides a structured opportunity for feedback and reflection.”

(PMI Agile Practice Guide, Section 3.5, Iteration Retrospectives)

Mike Griffiths further adds:

“Teams must take ownership of their process. The role of the agile leader, such as a Scrum Master, is to facilitate improvement via mechanisms like retrospectives. They are not responsible for enforcing process, but for enabling continuous improvement.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 4 – Team Performance)

Why the other options are incorrect:

A may undermine the team ' s self-organization and brings hierarchy into team-level process adjustments.

B may address some confusion, but doesn’t actively involve the team in process improvement.

D is inappropriate—sprint planning is for work planning, not process feedback.

Therefore, the most agile-appropriate and validated solution is: C

‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾

A developer is unable to work on their tasks within an iteration, because senior management is constantly pulling them into production incident analyses.

This is a blocker because the developer is unable to work on tasks within the iteration due to external interruptions (senior management pulling them into production incident analyses), preventing the team from progressing.

The offshore testing team is pulled away at the last minute from a high-profile initiative and testing cannot be resumed until a new testing team is assigned.

This is also a blocker because the offshore testing team has been pulled away at the last minute, causing a halt in testing until a new team is assigned. This delay impedes progress and prevents the team from moving forward with their work.

In Agile, one of the key principles is to provide continuous feedback and integration throughout the development process, ensuring that components are tested, integrated, and iterated upon regularly. By separating the work into three teams that work independently and only integrate at the end, the strategy risks delaying feedback and potentially causing integration problems. This approach could lead to significant issues when the components are eventually integrated, as they may not work together as expected due to lack of ongoing collaboration and integration. Therefore, working in parallel with proper continuous feedback and integration is crucial in Agile to minimize risks and ensure smooth delivery.

In this case, the risk description for " Incomplete requirements specification " has been identified as a high likelihood and high impact risk. To mitigate this, the most appropriate strategy would be to conduct thorough requirements analysis and validation. This ensures that the integration of the new tool with the customer relationship management system aligns with the business objectives and avoids misunderstandings or gaps in the product requirements, which could cause delays or rework later in the project. This step addresses the core challenge of ensuring the product meets the business needs and integrates smoothly with existing systems.

Kanban is a visual management tool that helps teams improve workflow efficiency. One of its key principles is the use of a pull system, where work is pulled into the process when capacity allows, rather than being pushed into the system. This contrasts with a push system, where work is assigned or forced into the workflow regardless of capacity. This approach helps avoid bottlenecks and ensures work is handled efficiently.

The correct answer is B – Ensured the early engagement of key stakeholders. Agile emphasizes early and continuous stakeholder involvement. In this case, engaging enterprise architects and standards stakeholders early in the design process would have helped detect conflicts before sprint execution.

From the PMI Agile Practice Guide:

“Key stakeholders should be engaged early in the development cycle to ensure alignment with organizational policies, standards, and expectations.”

(PMI Agile Practice Guide, Section 4.2 – Stakeholder Engagement)

Mike Griffiths notes:

“Involving stakeholders early helps mitigate the risk of late surprises and rework. Enterprise architects should be consulted during backlog grooming or prior to sprint planning.”

(Mike Griffiths, PMI-ACP Exam Prep, Chapter 3 – Stakeholder Engagement)

Incorrect options:

A is reactive and escalatory.

C presumes the standards are flawed without analysis.

D ignores necessary compliance and does not solve the issue proactively.

Answer: B

────────────────────────────────────

To ensure high code quality, especially for critical products, agile teams employ technical practices like pair programming and peer code reviews. The PMI Agile Practice Guide (Section 5.5: Technical Practices and Quality) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 5: Quality and Technical Excellence) support these practices as part of built-in quality—ensuring that issues are caught early in the development cycle.

Option A is correct: pair programming and peer reviews increase code quality and reduce defects early.

Option B is essential but a feedback tool—not a direct quality assurance practice.

Option C implies waterfall-style handoffs.

Option D is inefficient and risky without integrated testing or validation.

The correct answer is D – Facilitate a product development roadmap workshop. Engaging stakeholders early through a roadmap workshop helps align expectations, prioritize outcomes, and build shared understanding around value delivery.

From the PMI Agile Practice Guide:

“Product roadmaps provide a high-level view of deliverables and timing. Facilitating roadmap workshops ensures that all stakeholders contribute to and align with the vision.”

(PMI Agile Practice Guide, Section 5.4 – Product Roadmap and Planning)

Mike Griffiths further explains:

“Roadmap workshops allow stakeholders to discuss release priorities and business goals, ensuring engagement in the planning process and continuous alignment throughout the project.”

(Mike Griffiths, PMI-ACP Exam Prep, Chapter 5 – Adaptive Planning)

Incorrect options:

A reflects a waterfall mindset.

B involves team-level planning, not broad stakeholder engagement.

C is informative but not collaborative or sufficient for planning.

Answer: D

────────────────────────────────────

The correct answer is C – Identify and monitor issues through a risk burndown chart.

Risk burndown charts track how risk exposure is increasing or decreasing over time. This agile artifact is used to communicate risk trends and drive conversations around risk mitigation. It’s especially useful when risks threaten iteration goals or release timelines.

From the PMI Agile Practice Guide:

“Risk burndown charts are visual tools that track remaining project risk. They help identify whether risks are increasing or decreasing and enable proactive management.”

(PMI Agile Practice Guide, Section 3.5 – Risk Management in Agile)

Mike Griffiths explains:

“Tracking risks visually, such as in a risk burndown chart, helps stakeholders understand exposure levels and fosters risk-mitigation behavior across the team.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 6 – Risk Management)

Why the other options fall short:

A delays action and does not help real-time monitoring.

B tracks tasks, not risk.

D (issue log) may help but lacks the proactive visual trend tracking provided by a burndown chart.

Answer: C

In this situation, the scrum master has already escalated the issue to upper management without resolution, so it ' s important to collect empirical data to further demonstrate the impact of the external dependency. This data can be used to show the consequences of the dependency on the project’s progress, helping upper management understand the severity of the issue. By influencing management and making them accountable for ensuring the external team delivers, the scrum master helps ensure the problem is addressed at a higher level, which is critical for long-term resolution.

To assess process efficiency, agile teams use value stream mapping to identify waste, delays, and non-value-adding steps. According to the PMI Agile Practice Guide (Section 5.5 Process Analysis and Value Stream Mapping), value stream analysis helps determine how efficiently a process converts inputs into valuable outputs, making it ideal for supporting customer inquiries on operational performance.

Mike Griffiths (PMI-ACP Exam Prep Book, Chapter 7: Continuous Improvement) reinforces the value of using value stream mapping for both software development processes and operational workflows to increase transparency and drive improvements.

Option B is correct: reviewing the value stream provides a structured way to evaluate efficiency.

Option A and D are important for team improvement and performance but don’t focus on process activity efficiency.

Option C relates to value prioritization, not operational efficiency.

The storming phase (from Tuckman’s model: Forming–Storming–Norming–Performing) is marked by conflict and role negotiation. The agile coach or Scrum Master plays a critical role in guiding teams through this phase with structured facilitation and conflict-resolution techniques.

According to the PMI Agile Practice Guide (Section 4.3.2: Team Development Stages) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 3: Team Performance), the agile coach must provide support, guidance, and tools to help the team evolve toward self-organization and maturity.

Option B is correct: effective facilitation helps the team progress toward high performance.

Option A promotes dysfunction.

Option C risks escalating unresolved conflict.

Option D is overly individual-focused and not team-centric.

The correct answer is C — The team should have conducted more demonstrations with the product owner during the iteration.

Continuous feedback is essential in Agile. Regular product demos or interim check-ins during the sprint (not just at the end) allow the product owner to validate progress and course-correct early. This ensures that expectations are aligned and surprises are avoided at the sprint review.

PMI Agile Practice Guide:

“Stakeholder feedback should be gathered continuously throughout the sprint. Regular engagement and interim demos reduce the risk of misalignment at iteration end.”

(PMI Agile Practice Guide, Section 5.7 – Reviews and Demos)

Mike Griffiths:

“Waiting until the sprint review to validate features with the product owner increases risk. Frequent collaboration and demonstrations ensure the work remains on target.”

(PMI-ACP Exam Prep, Chapter 3 – Value-Driven Delivery)

Incorrect options:

A is helpful but doesn ' t guarantee alignment.

B is testing-focused and misses early collaboration.

D places all responsibility on the product owner, ignoring shared ownership.

Answer: C

The role of a servant leader focuses on serving the team by removing obstacles, providing support, and ensuring that the team has what it needs to be successful. The agile coach is advising the project manager to adopt this mindset, which is central to Agile leadership. In this role, the project manager focuses on enabling the team’s success rather than taking a directive or authoritative approach.

The correct answer is A – Educate the QA manager that in agile, quality is integrated from the beginning to the end of the project. Agile emphasizes “built-in” quality through test-first approaches, continuous integration, and Definition of Done. Addressing resistance through education helps clarify that quality is a core part of Agile—not an afterthought.

From the PMI Agile Practice Guide:

“Agile does not remove quality controls; rather, it integrates them throughout the development process. Quality is everyone’s responsibility and is embedded through practices such as TDD, automated testing, and continuous feedback.”

(PMI Agile Practice Guide, Section 3.5 – Quality and Agile)

Mike Griffiths adds:

“In Agile, quality is not sacrificed. It is a fundamental principle. Teams ensure quality by defining acceptance criteria, using continuous integration, and practicing test-first development.”

(Mike Griffiths, PMI-ACP Exam Prep, Chapter 3 – Value-Driven Delivery)

Incorrect options:

B may be helpful tactically, but doesn’t address the underlying concern.

C misrepresents technical debt.

D places too much QA responsibility on the product owner.

Answer: A

────────────────────────────────────

The best answer is C because agile backlog prioritization should be collaborative and value-driven. Stakeholder input is essential, but prioritization should also consider technical feasibility, dependencies, risks, team capacity, product goals, and value delivery. The agile team, product ownership role, and stakeholders should work together to maintain alignment.

Option A is incorrect because the change management team should not own backlog prioritization. Option B gives stakeholders too much unilateral control and ignores team insight. Option D ignores stakeholder priorities, which is not agile. Agile requires transparency, collaboration, and continuous alignment with business and customer value.

PMI-ACP topics emphasize engaging stakeholders, aligning work with organizational priorities, promoting shared vision and purpose, and ensuring the product remains aligned to organizational goals.

To estimate the project ' s conclusion using velocity, we use the formula:

Given:

Velocity = 40 story points per sprint

Remaining Work = 240 story points

Sprint Duration = 2 weeks

Since each sprint is 2 weeks, the total duration will be:

6 × 2 weeks = 12 weeks = 3 months

The correct answer is D – Make use of a Kanban board so that the team will have a clear view of the work in progress (WIP) for the release.

Agile teams use information radiators like Kanban boards to visualize work, improve flow, identify bottlenecks, and maintain team focus. Visibility of work enhances self-organization and accountability while reducing ambiguity and delays.

From the PMI Agile Practice Guide:

“Kanban boards provide visibility into the work in progress. They support collaboration, improve team focus, and are effective in both Scrum and Kanban approaches.”

(PMI Agile Practice Guide, Section 5.1 – Visual Controls)

Mike Griffiths writes:

“Visual tools such as task boards and Kanban boards allow the team to manage their flow and workload. This enables collaboration and transparency without micromanagement.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 5 – Adaptive Planning)

Why the other options fall short:

A introduces unnecessary meetings, potentially disrupting flow.

B may lead to micromanagement and undermine team ownership.

C implies a command-and-control style, which is contrary to Agile principles.

Answer: D

The product owner is responsible for maintaining and prioritizing the product backlog based on stakeholder input. According to the PMI Agile Practice Guide (Section 5.1: Product Backlog and Prioritization) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 4: Stakeholder Engagement), when a sponsor is dissatisfied, the product owner should confirm that their needs are clearly prioritized and represented in the backlog.

Option B is correct: ensuring priorities are accurately captured aligns delivery with stakeholder expectations.

Option A is reactive and not productive.

Option C presumes funding is the issue without confirming alignment.

Option D undermines the product owner’s role.

Continuous delivery is a key practice in DevOps, ensuring that code is always in a deployable state. This practice allows for faster, more reliable releases, promoting automation and consistent feedback loops in the development process. It helps teams to iterate quickly and deploy changes frequently, which is a hallmark of DevOps.

Agile encourages team collaboration and self-organization. If a team member feels underutilized, the team should be encouraged to engage that person more fully, leveraging their skills across tasks. According to the PMI Agile Practice Guide (Section 4.3: Team Performance) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 3: Team Development), the agile practitioner supports healthy team dynamics and facilitates inclusive participation.

Option C is correct: promoting team-level inclusion helps resolve underutilization and fosters engagement.

Option A is a last resort and undermines team stability.

Option B reframes the issue as a performance problem when it may not be.

Option D unnecessarily escalates what should be resolved within the team.

The correct answer is A — Provide feedback for completed user stories.

Stakeholder involvement in Agile is ongoing. Their primary role is to give timely and actionable feedback on delivered product increments to ensure alignment with their expectations and business value goals. This feedback is then used to refine the product backlog and guide future iterations.

PMI Agile Practice Guide:

“Stakeholders should engage regularly to inspect product increments and provide feedback to guide value delivery.”

(PMI Agile Practice Guide, Section 4.2 – Stakeholder Engagement)

Mike Griffiths:

“In agile projects, stakeholders ensure their needs are met by actively reviewing completed work and providing feedback to influence upcoming work.”

(PMI-ACP Exam Prep, Chapter 3 – Value-Driven Delivery)

Incorrect options:

B is the team ' s responsibility; stakeholders should focus on the “what,” not the “how.”

C is the product owner ' s responsibility.

D is a collaborative task but not solely a stakeholder responsibility.

Answer: A

—

When a feature is too large to fit into a sprint, agile recommends decomposing it into smaller user stories or increments. According to the PMI Agile Practice Guide (Section 5.2: User Stories and MVPs) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning), teams should break down epics or large stories into Minimum Viable Product (MVP) segments and deliver value incrementally.

Option A is correct: this enables the team to deliver value sooner and iteratively build on it.

Option B delays addressing customer concerns.

Option C sacrifices overall product balance.

Option D violates time-boxing principles in Scrum and agile.

The correct answer is D – Increase the opportunities to confirm common understanding with the client.

The rise in defects and change requests indicates a disconnect between what the team is delivering and what the customer expects. Agile emphasizes constant feedback and collaboration. Ensuring shared understanding through frequent interaction and validation reduces misunderstandings and rework.

From the PMI Agile Practice Guide:

“Frequent interactions with customers and stakeholders help teams build a shared understanding and reduce the risk of misaligned expectations and defects.”

(PMI Agile Practice Guide, Section 4.2 – Stakeholder Engagement)

Mike Griffiths explains:

“A high defect rate often results from unclear requirements. Teams should improve communication loops with stakeholders to confirm understanding before development begins.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 6 – Problem Detection and Resolution)

Why the other options are suboptimal:

A doesn’t address the root cause: misalignment with the client.

B is reactive and temporary, not a sustainable solution.

C may help but should be preceded by improving collaboration and understanding.

Answer: D

══════════════════════════════════════════════════

The correct answer is D — The team should reevaluate time and cost estimates to reflect the latest understanding of the work effort.

Agile supports progressive elaboration and adaptive planning. When actual effort consistently exceeds estimates, it signals a need to recalibrate estimation practices. The team should revisit their velocity, estimation techniques, and potentially re-estimate upcoming work with improved understanding.

PMI Agile Practice Guide:

“Agile uses adaptive planning, where teams update estimates based on new information. This supports better forecasting and risk management.”

(PMI Agile Practice Guide, Section 5.3 – Estimation and Velocity)

Mike Griffiths:

“Estimation accuracy improves over time. Agile teams regularly inspect estimation practices and adjust based on historical data and team maturity.”

(PMI-ACP Exam Prep, Chapter 5 – Adaptive Planning)

—

Kanban is an approach that focuses on visualizing and managing work in process (WIP) to ensure that there is minimal waste and that teams only work on what they can handle at any given time. It provides a flexible framework for continuous improvement, without the overhead of time-boxed iterations like in Scrum. Kanban allows teams to focus on limiting work in process, streamlining workflows, and improving efficiency while avoiding waste. This approach aligns with the organization ' s desire to minimize overhead and control WIP to maximize flow and productivity.

A value stream map is an effective tool for identifying and visualizing the flow of work and the associated delays or handoffs in a process. By mapping out the entire value stream, the team can identify inefficiencies, waste, and bottlenecks, which helps them target areas for improvement. This allows the team to optimize the workflow by reducing unnecessary handovers and delays, which is in line with their goal of improving efficiency.

The correct answer is A – Hold a meeting with the team and the Product Owner to develop the team charter, working agreement, guiding principles, and product vision. This collaborative approach fosters shared understanding, ownership, and alignment early in the project.

From the PMI Agile Practice Guide:

“The team chartering process includes developing working agreements, clarifying the product vision, defining team norms, and establishing the team ' s mission. Early alignment builds trust and commitment.”

(PMI Agile Practice Guide, Section 4.3 – Team Charter and Working Agreements)

Mike Griffiths elaborates:

“A strong start includes co-creating team values, the product vision, and working agreements. Doing this together builds a strong foundation for delivery.”

(Mike Griffiths, PMI-ACP Exam Prep, Chapter 2 – Agile Principles and Chapter 4 – Team Formation)

Incorrect options:

B separates the Product Owner from the team early on.

C reverses the roles—vision should be owned by the Product Owner.

D is helpful, but not a prerequisite for team alignment and success.

Answer: A

The correct answer is A – Refocus the sprint review meetings to demonstrate working software and seek feedback on the product.

Sprint reviews are designed to showcase the completed product increment to stakeholders and receive feedback. The primary goal is to validate that the work delivered provides value to the customer—not to present technical details. Demonstrating working software is one of the core tenets of Agile.

From the PMI Agile Practice Guide:

“Sprint reviews are working sessions designed to elicit feedback and foster collaboration. Teams demonstrate completed work and adjust the backlog based on stakeholder input.”

(PMI Agile Practice Guide, Section 5.3 – Value Delivery)

Mike Griffiths confirms:

“The output of every iteration should be potentially shippable product. The sprint review is for stakeholders to see that output and provide feedback to inform future development.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 2 – Value-Driven Delivery)

Other options explained:

B may be helpful, but it doesn’t solve the immediate issue of misaligned sprint reviews.

C misunderstands the purpose of the sprint review—it’s not about architecture.

D changes the audience instead of correcting the approach.

Answer: A

══════════

To kick off the project, especially when the idea is not yet clear, the agile lead should focus on understanding the needs and challenges of the end users—HR in this case. By applying the empathy map technique, the team can gather insights into the users ' experiences, needs, and pain points. This helps in building a more focused and user-centered approach to solving the problem, which is the foundation for developing a product backlog. Engaging stakeholders early and understanding the problem space will clarify the project direction and lay the groundwork for creating meaningful user stories.

The scrum master should emphasize the core principles of agile, which are centered around collaboration, delivering value incrementally, and fostering a shared mindset among the team. In an agile environment, success is not only about following processes but about the team working together towards a common goal, adapting to change, and continuously delivering value to customers. These principles are the foundation of agile methodologies and essential for teams that are new to agile to understand.

The best approach to resolving this conflict is collaborating, as it encourages open communication and active participation from all team members. In this case, the graphic designer’s non-participation is causing frustration within the team. The Scrum Master should facilitate a discussion where the designer can express their concerns, and the team can share why their attendance in meetings is important. By collaborating, the Scrum Master can help find a solution that addresses both the designer’s needs and the team ' s expectations, ensuring better teamwork and alignment moving forward. This approach encourages mutual respect and fosters a cooperative environment.

Stakeholder participation, especially during sprint reviews, is critical to agile success. The PMI Agile Practice Guide (Section 7.2: Stakeholder Engagement) emphasizes the importance of actively engaging stakeholders throughout the project lifecycle, particularly during key ceremonies like sprint reviews, where feedback shapes the product.

Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 4: Stakeholder Engagement) states that stakeholders need to understand the value of their input and how it influences product direction. The agile practitioner or Scrum Master should educate and influence stakeholders by demonstrating the tangible impact of their participation.

Option D is correct: aligning stakeholders with the benefits of engagement fosters participation.

Option A, B, and C are passive substitutes and don’t address the root issue of stakeholder disengagement.

The correct answer is C – Explain that the Kanban board enables the team to complete the work and increases transparency on work that is not done.

Agile values transparency, visibility, and collaboration. Kanban boards are a form of information radiator—tools that openly display the team’s workflow, work-in-progress (WIP), and progress toward goals. Their visibility helps stakeholders and the team remain aligned and encourages accountability.

From the PMI Agile Practice Guide:

“Agile teams use information radiators such as Kanban boards to provide transparency and make status, bottlenecks, and priorities visible to all. This fosters trust, communication, and quick decision-making.”

(PMI Agile Practice Guide, Section 3.5 – Information Radiators)

Mike Griffiths adds:

“Visibility into progress and issues enhances communication and alignment across stakeholders. Information radiators like task boards or Kanban boards are vital tools for agile success.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 5 – Agile Tools and Techniques)

Other options are inappropriate:

A and D compromise transparency and contradict agile values.

B misstates the purpose of the Kanban board—it’s not about assigning work post-completion.

Answer: C

══════════════════════════════════════════════════

The correct answer is D – Encourage self-organization by communicating the importance of a collaborative approach in decision making about the requirements.

Agile teams thrive on collaboration and shared ownership. When conflicts arise between stakeholders and team members, the project manager (or Scrum Master) acts as a facilitator to encourage respectful discussion and team-driven decisions. Agile emphasizes self-organization, transparency, and frequent collaboration between customers and teams.

From the PMI Agile Practice Guide:

“Agile encourages ongoing stakeholder engagement and collaborative decision making. The Agile leader helps teams self-organize and resolve issues through direct communication and mutual respect.”

(PMI Agile Practice Guide, Section 4.2 – Stakeholder Engagement)

Mike Griffiths explains:

“Agile promotes co-creation. The project manager’s role is to facilitate dialogue, not dictate requirements. The best outcomes come from collective decisions aligned with value.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 3 – Stakeholder Engagement)

Other options explained:

A contradicts Agile principles of team and stakeholder collaboration.

B gives unilateral authority to the customer, which can disrupt team ownership.

C excludes the team from the conversation, weakening transparency.

Answer: D

══════════════════════════════════════════════════

The root cause of the issue seems to be a focus on process and planning meetings, which may be impacting the team ' s ability to deliver effectively. Implementing Kanban, which emphasizes a pull system and focuses on continuous delivery without overwhelming the team with unnecessary meetings, allows for smoother workflow and can address bottlenecks. It helps the team focus more on value delivery rather than rigid planning and process constraints, thus potentially improving the quality and reducing unnecessary delays.

Managing technical debt is crucial for the long-term health of the project. The most effective approach is to include technical debt tasks in every sprint, ensuring that the debt is addressed incrementally without disrupting the flow of new feature development. By treating technical debt as a priority alongside new features, the team can reduce the impact of technical debt over time, maintain product quality, and align with stakeholder expectations. Continuous review of the impact ensures that the team is making informed decisions and balancing both short-term delivery and long-term maintainability. This approach also allows the team to meet performance expectations and customer satisfaction more consistently.

A clear, shared vision statement is essential for alignment, motivation, and guidance. According to the PMI Agile Practice Guide (Section 2.3.1: Product Vision Statement), a strong vision statement enables team members and stakeholders to stay focused on what matters most, even as requirements evolve.

Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 2: Agile Principles and Mindset) stresses the importance of a shared understanding and active participation when forming the vision.

Option A is correct: it reinforces the value of shared vision and encourages stakeholder engagement.

Option B is helpful but doesn ' t ensure shared understanding across the team.

Option C risks misinterpretation and omits team collaboration.

Option D dismisses a core agile practice—vision clarity is crucial, even in a change-friendly environment.

The sponsor is looking at the product roadmap, which is a visual representation of the product ' s planned features and their expected delivery timelines across multiple releases. It typically shows the major milestones, planned releases, and features grouped by their respective release numbers. This aligns with the sponsor ' s inquiry about when a specific feature will be ready, as the roadmap provides a high-level view of the product ' s development and release schedule.

The correct answer is B – Retrospective meeting.

The retrospective is a key Agile ceremony dedicated to continuous improvement. It provides a safe space for the team to reflect on what went well, what didn’t, and how to improve. When morale is low or conflicts arise, retrospectives help surface issues and co-create solutions.

From the PMI Agile Practice Guide:

“Retrospectives are a vital part of continuous improvement. They are used to inspect team processes, relationships, and interactions to find ways to work more effectively.”

(PMI Agile Practice Guide, Section 3.7 – Continuous Improvement)

Mike Griffiths emphasizes:

“The retrospective is the heartbeat of improvement. It is where the team reflects, adjusts, and grows. Conflict and low morale are ideal triggers for a meaningful retrospective.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 7 – Continuous Improvement)

Other options explained:

A (Standup) is for daily coordination, not reflection.

C (Demo) is customer-facing and not a morale tool.

D (Offsite) may help later, but is not a formal Agile method for resolving internal team issues.

Answer: B

When there is uncertainty about how certain product features should work, creating a prototype is an effective way to reduce that uncertainty. Prototyping allows the product owner to test ideas, gather feedback from users early in the process, and make adjustments based on real-world input. This approach helps clarify the product ' s functionality and ensure that the team is building something that meets user needs, all while maintaining flexibility and adaptability in the Agile environment.

The correct answer is C – Encourage the product owner and team to analyze the impact of the changes and prioritize the backlog.

Agile embraces change, even late in the development cycle, but it must be managed through value-driven prioritization. Instead of blindly accepting all changes or overrunning the budget, the product owner collaborates with the team and stakeholders to evaluate the impact, adjust priorities, and ensure high-value items are delivered within constraints.

From the PMI Agile Practice Guide:

“Agile teams welcome change but balance it with value delivery by continuously prioritizing the product backlog. When scope increases, the team and product owner must evaluate trade-offs and adjust delivery accordingly.”

(PMI Agile Practice Guide, Section 3.4 – Value-Based Prioritization)

Mike Griffiths affirms:

“Backlog grooming is a key mechanism to handle change. Product owners collaborate with stakeholders and the team to evaluate new requests, weigh impacts, and reprioritize as necessary.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 3 – Value-Driven Delivery)

Other options are incorrect:

A may be true in some organizations but is not an Agile principle.

B contradicts Agile’s emphasis on sustainable pace.

D may help clarify budgets but doesn’t resolve the issue collaboratively.

Answer: C

══════════════════════════════════════════════════

When a security issue is revealed mid-sprint, the project manager should consult with both the product owner and the project team. The product owner is responsible for prioritizing the backlog and ensuring that the most valuable features are worked on, while the team will help assess the technical implications of addressing the security issue.

The product owner needs to understand the impact of the security issue on the product ' s value and determine if it needs to be prioritized over other work in the sprint.

The project team should help evaluate the effort required to address the issue and ensure that the solution is feasible within the sprint’s capacity.

By collaborating with both the product owner and the team, the project manager can make an informed decision on whether to adjust the sprint plan, reprioritize the backlog, or take necessary actions to address the vulnerability. This ensures that the security issue is resolved without jeopardizing the overall sprint goals.

In the scenario described, the team is discussing the root causes of the technical problems that led to delayed deliverables, which indicates they are being proactive. One of the agile principles is to deliver working software frequently and adapt to change, and this situation shows the team is reflecting on their issues to improve future performance by identifying ways to balance the demands placed on the team (workload, deadlines, etc.) with their available capacity and necessary competencies.

The correct answer is B — They most likely discussed the best approach for this project with the team and will adapt and tailor the approach periodically by reviewing and verifying the scope with the customer.

In Agile, tailoring and adaptiveness are key. Agile projects are not " one-size-fits-all " — teams assess the context and collaboratively select and continuously tailor the best-fit practices. Agile also emphasizes engaging stakeholders frequently and iteratively refining scope.

PMI Agile Practice Guide:

“Agile teams tailor their processes and continually adapt to changing needs. The decision to use agile practices should be based on the nature of the work and team collaboration.”

(PMI Agile Practice Guide, Section 2.1 – Tailoring Agile)

Mike Griffiths:

“Agile promotes adaptive planning and continuous stakeholder engagement to ensure alignment and responsiveness to change.”

(PMI-ACP Exam Prep, Chapter 1 – Agile Principles and Mindset)

—

The team ' s primary role is to estimate and define the work items in the product backlog. In an Agile environment, the team collaborates with the product owner to break down user stories into manageable tasks, providing effort estimates (such as story points) to help guide future iterations. The team also works with the product owner to refine and clarify requirements when needed, ensuring that the work is well understood and ready for execution.

If a story is not completed, it is not counted toward the current sprint velocity. When carrying the story forward to the next sprint, teams should re-evaluate the story size, especially if part of the work is already done. According to the PMI Agile Practice Guide (Section 5.4: Velocity and Estimation) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning), agile teams are encouraged to re-estimate such items based on remaining work.

Option D is correct: incomplete stories should be re-estimated based on new size or effort.

Option A violates velocity principles—only fully completed stories count.

Option B undermines the fixed-length timebox principle of sprints.

Option C is not directly relevant unless the story’s complexity necessitates research, which is not stated here.

The correct answer is D – Fishbone diagram. Also known as an Ishikawa or cause-and-effect diagram, this analysis tool helps teams identify root causes of delays or inefficiencies. In this scenario, the team needs to understand the causes of delayed release cycles to make process improvements.

From the PMI Agile Practice Guide:

“Root cause analysis tools such as fishbone diagrams can help teams identify underlying causes of inefficiencies or failures, supporting continuous improvement.”

(PMI Agile Practice Guide, Section 6.5 – Problem Detection and Resolution)

Mike Griffiths also writes:

“A fishbone diagram helps the team brainstorm and categorize the potential causes of a problem, enabling a structured investigation into delays or bottlenecks.”

(Mike Griffiths, PMI-ACP Exam Prep, Chapter 6 – Problem Resolution)

Incorrect options:

A is for identifying and managing risks, not diagnosing root causes.

B analyzes progress metrics but doesn’t provide root cause insights.

C is for understanding customer satisfaction, not operational delays.

Answer: D

────────────────────────────────────

Given the global distribution of the stakeholders and their high interest in the project (as indicated in the stakeholder power/interest grid), a dynamic feedback platform is the most effective way to ensure consistent engagement. By leveraging collaboration tools that allow asynchronous feedback, the team can accommodate stakeholders in different time zones, reducing the delay in obtaining feedback and helping to speed up the decision-making process. This approach ensures that all stakeholders can contribute when it’s convenient for them, without the need for synchronized meetings, thus improving overall engagement and decision-making efficiency.

The correct answer is D — Iteration Burndown Chart.

An iteration burndown chart provides daily updates about the team’s progress during an iteration (or sprint). It tracks the remaining work in the sprint backlog and helps both the team and stakeholders assess if the sprint goal is likely to be met. This visualization helps communicate real-time progress to key stakeholders and supports adaptive planning.

PMI Agile Practice Guide states:

“Burndown charts display work remaining in a timebox and are updated daily. They are effective for communicating iteration progress to the team and stakeholders.”

(PMI Agile Practice Guide, Section 5.6, Information Radiators)

PMBOK® Guide (6th Edition) and Mike Griffiths both emphasize using task boards and burndown charts as “information radiators” for transparency.

Mike Griffiths’ PMI-ACP Exam Prep Book elaborates:

“Iteration burndown charts are the most widely used artifact to track sprint progress. They offer insight into how much work remains and signal whether the team is on track to meet its sprint goal.”

Options A and B are long-term planning tools. Option C (velocity) is a forecasting metric and not updated daily.

Answer: D

=================================

The correct answer is A – To participate in establishing a shared vision as a member of the team.

Stakeholder engagement ensures alignment between the team and business needs. Early and continuous involvement helps define product vision, clarify priorities, and ensure that the delivered product meets customer expectations.

From the PMI Agile Practice Guide:

“Engaging stakeholders early and often increases transparency, encourages shared ownership, and ensures that the product being developed aligns with business value.”

(PMI Agile Practice Guide, Section 4.2 – Stakeholder Engagement)

Mike Griffiths reinforces:

“Projects are more successful when stakeholders co-create the product vision and maintain involvement. Agile teams encourage active participation to ensure delivery of value.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 3 – Stakeholder Engagement)

Why other options fall short:

B (acceptance criteria) is mainly defined by the Product Owner, not all stakeholders.

C is typically owned by the development team.

D is not a core stakeholder responsibility in Agile.

Answer: A

══════════════════════════════════════════════════

When the team is facing difficulties in estimating the scope of work due to unclear or ambiguous requirements, the product owner should collaborate closely with the client to ensure that the requirements are clear and well-defined. By refining the product backlog with more detailed and clarified requirements, the product owner can help the team generate more accurate estimates and better understand the scope of work. This is a fundamental step in ensuring the team can properly plan and execute the project on time.

The correct answer is C — Use retrospective techniques such as silent writing, clustering, and dot voting to field feedback prior to discussion by the team.

Agile retrospectives should foster psychological safety and equal participation. Techniques such as silent brainstorming or writing on sticky notes (physical or digital), followed by clustering similar themes and dot voting, help balance group dynamics and encourage input from all team members—including those who are less vocal.

PMI Agile Practice Guide explains:

“Effective retrospectives use facilitation techniques such as silent brainstorming, dot voting, and clustering to gather inputs from all participants. These techniques level the playing field, reduce groupthink, and support diverse communication styles.”

(PMI Agile Practice Guide, Section 5.8 – Retrospectives)

Mike Griffiths also emphasizes:

“Using structured techniques allows quieter team members to contribute equally, and minimizes the dominance of more outspoken participants. The Scrum Master plays a key role in facilitating inclusive discussions.”

(PMI-ACP Exam Prep, Chapter 4 – Team Performance)

Incorrect options:

A and D are passive methods that reduce the collaborative and iterative nature of retrospectives.

B may help, but does not address dominant voices or structure participation equitably.

Answer: C

—

The correct answer is B – Evaluate the impact of the change request and let the team and Product Owner decide and reprioritize based on value. Agile allows for mid-iteration changes only in exceptional cases where business value is at risk. Such changes must be evaluated collaboratively.

From the PMI Agile Practice Guide:

“Agile teams may allow scope changes mid-iteration if the benefit clearly outweighs the cost. In such cases, the Product Owner and team collaboratively assess and decide whether to accommodate the change.”

(PMI Agile Practice Guide, Section 5.2 – Iteration Planning and Scope Flexibility)

Mike Griffiths also explains:

“While mid-iteration changes are discouraged, if the change is critical to business value, the team and Product Owner may replan collaboratively. Agile encourages flexibility with customer-focused decision-making.”

(Mike Griffiths, PMI-ACP Exam Prep, Chapter 3 – Value-Driven Delivery)

Incorrect options:

A and D bypass collaborative evaluation.

C is too extreme for a small but valuable change.

Answer: B

────────────────────────────────────

The correct answer is A – Work with the team to improve collaboration by fostering group decision-making and conflict resolution techniques.

One of the core principles of Agile is self-organizing teams. Teams must learn to make decisions collaboratively. If they are struggling, the Scrum Master or Agile Coach should facilitate improved team dynamics, encouraging consensus-building and effective conflict resolution techniques such as consensus, dot voting, or facilitation.

From the PMI Agile Practice Guide:

“Agile teams are empowered to make decisions. Coaches support this by teaching group decision-making techniques and fostering a culture of psychological safety and collaboration.”

(PMI Agile Practice Guide, Section 6.2 – Coaching the Agile Team)

Mike Griffiths highlights:

“When teams hesitate to make decisions, the coach’s role is to facilitate better team dynamics—not to make decisions for them. Group decision-making leads to greater commitment and alignment.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 4 – Team Performance)

Why other options fall short:

B gives decision-making power to the Product Owner inappropriately for technical matters.

C fragments accountability and may cause misalignment.

D may help in leadership development but doesn’t guarantee collaborative decision-making.

Answer: A

A key agile principle is that user stories should include clear acceptance criteria, which must be reviewed and accepted by the product owner. According to the PMI Agile Practice Guide (Section 5.2: User Stories and Acceptance Criteria) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 6: Value-Driven Delivery), acceptance criteria ensure that the team and product owner share a clear understanding of what constitutes “done.”

Option A is correct: having the product owner validate acceptance criteria ensures alignment.

Option B addresses technical quality but not stakeholder dissatisfaction.

Option C unfairly shifts blame without addressing communication.

Option D goes against agile’s iterative and flexible nature.

When overwhelmed by support tickets, the agile approach is to prioritize systemic problem-solving over reactive work. According to the PMI Agile Practice Guide (Section 5.5: Quality and Continuous Improvement) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 7: Problem Detection and Resolution), agile teams should identify root causes rather than just addressing symptoms. By analyzing the backlog, the team can spot patterns and address systemic issues, reducing incoming ticket volume in the long run.

Option C is correct: addressing the root cause improves sustainability and overall efficiency.

Option A leads to burnout and is unsustainable.

Option B ignores prioritization or value.

Option D is not a strategic response—it increases cost without solving the core issue.

The most effective way to address and correct defects while maintaining predictability and capacity is by working with the team to establish clear coding and quality standards, as well as comprehensive testing policies. By setting these explicit rules, the team will have a shared understanding of the quality expectations and testing requirements, which will help prevent defects from escaping into production. This approach focuses on building quality into the process, rather than reacting to defects after they occur, and supports the long-term goal of improving software quality and predictability without overburdening the team.

Agile emphasizes just enough detail to start work and adapt through ongoing conversation. According to the PMI Agile Practice Guide (Section 5.2 Requirements and User Stories), stories should be clear enough for estimation and discussion, but not over-specified. The INVEST model (Independent, Negotiable, Valuable, Estimable, Small, Testable) supports this.

Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning) reiterates that stories should not contain exhaustive detail up front; rather, they evolve through collaborative dialogue with the product owner.

Option C is correct because it supports collaboration and adaptive planning.

Option A and B lead to over-specification and undermine agility.

Option D addresses testing but doesn’t resolve confusion about appropriate story detail.

Agile promotes transparency through information radiators, such as task boards, burndown charts, and Kanban boards. These tools are designed to make real-time progress visible to all stakeholders. According to the PMI Agile Practice Guide (Section 7.1: Communications) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 4: Stakeholder Engagement), stakeholders should be directed to these real-time, transparent sources of truth.

Option B is correct: using an information radiator promotes transparency and reduces dependency on individuals.

Option A is inappropriate—standups are for the team.

Option C and D are manual approaches that reduce transparency and don ' t scale.

The correct answer is C – Refer to the remaining prioritized backlog items. Agile planning is iterative and based on the product backlog’s prioritization. During iteration planning, once the team has identified most story points to be delivered, it should refer back to the product backlog and select the next highest-priority user stories to fill in the remaining capacity, considering the team’s historical velocity.

From the PMI Agile Practice Guide:

“Iteration planning begins with the team reviewing the prioritized backlog items. Based on their velocity, they determine how many stories can be completed. Teams select stories from the top of the backlog and stop when they reach their capacity.”

(PMI Agile Practice Guide, Section 5.2 – Iteration Planning)

Mike Griffiths also emphasizes:

“Agile teams rely on a prioritized backlog maintained by the product owner. Iteration planning involves pulling the highest-priority stories into the sprint until the team reaches its forecasted velocity.”

(Mike Griffiths, PMI-ACP Exam Prep, Chapter 5 – Adaptive Planning)

Other options are incorrect:

A is counter to adaptive planning and proactive engagement.

B focuses on technical feasibility, not business priority.

D ignores prioritization and may add low-value work.

Answer: C