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

When issues recur across multiple iterations, it’s a strong indication that the root cause has not been addressed. The PMI Agile Practice Guide (Section 5.6 Retrospectives) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 7: Continuous Improvement) recommend performing root cause analysis techniques (e.g., 5 Whys, Fishbone diagram) to ensure that the true source of recurring problems is uncovered and resolved.

Option B is correct: identifying root causes is essential to sustainable improvements.

Option A may help but doesn’t address the underlying team-level process.

Option C is useful after a solution is implemented but not the priority when the cause is unknown.

Option D is helpful for tracking, but again, ineffective if the root cause is unidentified.

The correct answer is B — Communicate this to the product owner, and offer to help facilitate discussions with the team.

Agile promotes collaboration, transparency, and continuous improvement. The agile practitioner (e.g., Scrum Master) should first address challenges at the team level. Facilitating better communication and helping the product owner articulate requirements clearly is part of fostering a high-performing team environment.

PMI Agile Practice Guide states:

“Agile practitioners serve the team by removing impediments and improving communication. When conflicts or misunderstandings occur, the practitioner should engage with team members to resolve issues collaboratively before escalating externally.”

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

Mike Griffiths further explains:

“Scrum Masters or Agile Coaches are servant-leaders. Their role includes helping product owners improve interactions and serve the development team more effectively.”

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

Other options:

A and D involve escalation without first attempting resolution.

C avoids direct action and leaves responsibility to someone else.

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

Step 1: Identifying Remaining MVP Story Points

From the backlog, the MVP-related stories that are not started include:

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: Projected Sprint Completion

MVP Completion: The risk register mentions a burn reduction for sprints 4-6 due to holiday schedules.

If the burn rate is consistent after sprint 6, the MVP will be completed by sprint 9.

The entire backlog is projected to complete by sprint 16 assuming no further deviations.

The act of sharing iteration charts and progress metrics reflects a core agile value: transparency. According to the PMI Agile Practice Guide (Section 7.1: Communication and Transparency) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 4: Stakeholder Engagement), transparency enables stakeholders to participate constructively in decision-making and promotes trust and visibility.

Option A is correct: sharing charts builds openness and visibility on the project ' s progress.

Option B may occur, but it’s not the primary practice described.

Option C focuses on delivery method, not transparency.

Option D is part of agile, but the emphasis here is on project health visibility.

The correct answer is C — Ask management to ensure that the resource is available to only one project at a time.

Agile promotes dedicated, stable teams over multitasking. Task-switching reduces productivity and leads to context-switching overhead. If a key resource is overburdened and switching between multiple projects, the best solution is to secure focused commitment by escalating to management for support.

PMI Agile Practice Guide:

“Agile teams should be dedicated and work on one project at a time. Splitting attention across multiple efforts reduces velocity and quality due to context switching.”

(PMI Agile Practice Guide, Section 6.1 – Team Composition)

Mike Griffiths highlights:

“Effective agile teams are stable, long-lived, and dedicated. Shared resources create bottlenecks, undermine predictability, and impair team dynamics.”

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

Incorrect options:

A may solve bandwidth issues but not focus or ownership.

B addresses symptoms, not the core issue of divided focus.

D tolerates a harmful practice that contradicts agile team stability.

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.

According to the PMI Agile Practice Guide (Section 7.2.2), one of the key responsibilities of the agile practitioner is to actively engage stakeholders throughout the development cycle—not just during review meetings. Agile frameworks promote continuous collaboration and frequent feedback. Merely attending sprint reviews is passive participation and may lead to missed alignment on expectations.

Mike Griffiths also emphasizes in his PMI-ACP Exam Prep Book (Chapter 4: Stakeholder Engagement) that stakeholder satisfaction requires more than periodic visibility—it requires ongoing interaction and inclusion in decision-making and backlog refinement sessions. This deepens shared understanding and reduces the risk of late-stage surprises.

Hence, answer B is correct because proactive stakeholder engagement with the product owner fosters mutual understanding, timely feedback, and course correction—ensuring the product aligns with expectations.

The correct answer is D – Ask QA team members experienced with the new automation framework to cross-train the other QA members. Agile emphasizes shared ownership, continuous learning, and eliminating skill silos. Cross-training is an effective way to improve team capability and reduce dependencies.

From the PMI Agile Practice Guide:

“Agile encourages cross-functional teams and skills sharing. When skill gaps are discovered, team members with the knowledge are encouraged to cross-train others to increase the team’s flexibility and productivity.”

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

Mike Griffiths adds:

“Cross-training improves team resilience and reduces bottlenecks. When expertise is limited to a few people, risks increase. Agile teams overcome this by mentoring and shared learning.”

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

Incorrect options:

A and C are reactive and delay resolution.

B encourages overwork and can lead to burnout.

Answer: D

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

The presence of a single point of knowledge is a significant risk in agile teams. According to the PMI Agile Practice Guide (Section 4.3.3: Team Structure and Cross-functionality) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 3: Team Performance), agile teams should avoid role silos and promote knowledge sharing. Adding another database administrator helps with both workload distribution and knowledge retention through pairing or mentoring.

Option C is correct: it ensures redundancy and knowledge spread, reducing project risk.

Option A does not address knowledge transfer or team development.

Option B removes the knowledge resource, worsening the risk.

Option D limits knowledge-sharing and still creates a bottleneck.

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.

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 correct answer is C – Meet with the team to discuss the issue and identify specific actions to reduce or eliminate the issue. Agile coaches facilitate team self-management, guide reflection, and encourage the team to solve performance issues collaboratively. Open discussion fosters ownership and accountability.

From the PMI Agile Practice Guide:

“Agile coaches guide teams through self-reflection and help them identify root causes of issues. Coaches support team-driven resolutions to behavioral and performance problems.”

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

Mike Griffiths adds:

“Effective agile leadership involves enabling the team to identify and resolve their own challenges. Top-down directives may harm morale and self-organization.”

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

Incorrect options:

A and B bring in external control, undermining team autonomy.

D is punitive and contradicts agile principles of empowerment and trust.

Answer: C

The correct answer is B – Review possible options and make an informed decision to cut losses based on delivered business value. In agile, decisions are continuously evaluated based on value delivery, inspect-and-adapt principles, and business justification.

From the PMI Agile Practice Guide:

“Agile projects emphasize delivering the highest value features early and frequently. When new information emerges—such as the high risk of failure of a critical feature—the product owner must evaluate the cost-benefit, assess remaining value, and make a business-based decision.”

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

“The agile mindset embraces failure as a learning opportunity but also encourages continuous evaluation of whether a project should continue. It is better to stop a project early based on value delivery assessments than to continue wasteful efforts.”

(PMI Agile Practice Guide, Section 2.3 – Fail Fast to Learn Quickly)

Mike Griffiths’ PMI-ACP Exam Prep Book notes:

“Agile teams reassess business value frequently. If remaining features do not justify additional investment due to technical, market, or cost concerns, the product owner may decide to stop the project and preserve resources. This decision should always be informed by the value already delivered versus expected benefits.”

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

Why the other options are incorrect:

A is a possible outcome, but prematurely terminating without analyzing value delivery is hasty.

C (bringing in experts) may increase costs and still not solve the fundamental issue of failing value.

D ignores the significance of the critical feature and assumes it can be deferred without impact—this may not be viable.

Answer: B

The correct answer is D – Features should be prioritized and then teams should be organized around those priorities. In agile scaling and reorganization, forming feature teams allows for the creation of cross-functional, end-to-end value delivery units. This reduces dependencies and promotes customer-focused outcomes.

From the PMI Agile Practice Guide:

“Teams are best organized around delivering customer value. When scaling or merging efforts, restructuring around features or customer priorities improves flow, minimizes handoffs, and supports agility at scale.”

(PMI Agile Practice Guide, Section 5.5 – Agile Scaling Considerations)

Mike Griffiths notes:

“Agile scaling favors organizing teams around features and capabilities rather than components. Feature teams are cross-functional and able to deliver end-to-end slices of functionality with minimal dependencies.”

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

Incorrect options:

A can lead to chaos without structure.

B reinforces siloed, component-based teams which increase integration risk.

C recreates functional silos rather than cross-functional teams.

Answer: D

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

The correct answer is D — Get the product owner and team to meet to prioritize the work.

Agile teams prioritize collaboratively with the product owner, who represents the business value perspective. Technical tasks (sometimes called “chores”) may not deliver immediate business functionality but are important for sustaining delivery capacity. It’s essential to balance technical work with feature delivery through backlog prioritization.

PMI Agile Practice Guide:

“Agile teams work with the product owner to prioritize backlog items, including technical debt or tasks that improve efficiency. Prioritization is a shared activity.”

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

Mike Griffiths:

“Product owners collaborate with teams to ensure technical tasks that improve delivery capacity are balanced with business features.”

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

Incorrect options:

A dismisses tasks that could improve long-term velocity.

B ignores team ownership.

C escalates prematurely rather than promoting collaboration.

Answer: D

—

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.

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.

The Scrum retrospective is the appropriate place for the team to reflect on what went well and what didn’t, including the missed sprint goals. The Scrum master should facilitate an open and constructive discussion about the impediments faced during the sprint, such as the unavailability of the specialist, and help the team find ways to avoid or mitigate similar issues in future sprints. This helps the team continuously improve and ensures that they are better prepared for future challenges.

The correct answer is B – Discuss the value of the change for the project with the customer.

Agile encourages ongoing collaboration with the customer, even if changes occur late in development. The contractor should not immediately reject or escalate the request. Instead, the first step is to assess the value of the requested change, collaborate on its importance, and then determine the best path forward—whether through backlog reprioritization or contractual adjustment.

From the PMI Agile Practice Guide:

“Agile welcomes changes in requirements, even late in development. Collaborate with the customer to explore the value of the change and its impact on schedule, cost, and scope.”

(PMI Agile Practice Guide, Section 3.4 – Delivering Value Frequently)

Mike Griffiths emphasizes:

“Before resorting to contract changes or governance processes, teams should talk with the customer to understand the reason behind the change and its value.”

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

Why the other options are suboptimal:

A assumes the change must go through legal channels without exploring its business value.

C may be necessary later but not as a first step.

D passively ignores the change and risks stakeholder dissatisfaction.

Answer: B

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

The correct answer is C – Invite the new release manager to the sprint demo and ask for help. Agile encourages stakeholder collaboration and visibility. Sprint reviews (also known as demos) are key opportunities for stakeholders, including release managers, to engage directly with the team and provide feedback. Since the issue is related to environmental instability and the new release manager is a key stakeholder, involving them in the sprint review enables mutual understanding and sets the stage for collaboration.

From PMI Agile Practice Guide:

“Agile teams use the sprint review to present completed work to stakeholders and receive direct feedback. It is also an opportunity to engage stakeholders who can influence the delivery environment.”

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

From Mike Griffiths’ PMI-ACP Exam Prep Book:

“Agile encourages frequent stakeholder collaboration. Sprint reviews should include key stakeholders who are responsible for operational and release matters to ensure alignment.”

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

Options A and D are passive approaches and may not lead to effective communication. Option B (attending daily standups) may be helpful but is not the best opportunity for strategic involvement compared to a sprint demo.

Answer: C

=========

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

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

In Scrum, the product owner is the primary point of contact between stakeholders and the development team. According to the PMI Agile Practice Guide (Section 3.3: Roles and Responsibilities), the Scrum Master ensures that communications flow properly and protects the team from distractions.

Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 4: Stakeholder Engagement) emphasizes the importance of having a single point of contact for stakeholder feedback to avoid miscommunication and overload.

Option A is correct: redirecting communication through the product owner keeps the team focused and the backlog structured.

Option B is unprofessional and discourages stakeholder engagement.

Option C bypasses review and prioritization—backlog management should be intentional.

Option D could blur roles and bypass proper channels.

The correct answer is A – Send the member to training. Agile encourages cross-functional teams and continuous improvement. When a team member identifies a skill gap that affects delivery, addressing it promptly through training or mentoring increases team capability and autonomy.

From the PMI Agile Practice Guide:

“Agile teams strive for cross-functionality. When skill gaps hinder progress, organizations support learning to reduce dependencies and improve throughput.”

(PMI Agile Practice Guide, Section 4.3 – Continuous Learning and Team Development)

Mike Griffiths adds:

“Empowering team members through skill development enhances flexibility and velocity. Encouraging proactive learning improves team performance.”

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

Incorrect options:

B defers ownership of the solution.

C unnecessarily delays action.

D delays learning due to unnecessary constraints.

Answer: A

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

Agile empowers teams to be self-organizing and self-managing. According to the PMI Agile Practice Guide (Section 5.6) and Mike Griffiths ' PMI-ACP Exam Prep Book (Chapter 7: Problem Detection and Resolution), the agile coach or Scrum Master facilitates the process but should encourage the team to resolve internal issues themselves. This develops ownership, team maturity, and accountability.

The team coach’s role is to support, not solve. Escalating issues unnecessarily or bypassing the team undermines agile principles. Therefore, Option C is correct: the coach should encourage the team to address and resolve the issue internally, stepping in only if the team cannot resolve it themselves.

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)

—

The sprint retrospective is a key Scrum ceremony where the team reflects on the sprint, identifies what went well, what didn’t, and discusses ways to improve their processes. The focus is on continuous improvement, and the team makes plans to implement those improvements in future sprints. Stakeholders are typically not involved in the retrospective, but it’s important for them to understand that the meeting is about helping the team improve their collaboration, efficiency, and performance.

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 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

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.

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.

=========

A well-defined, mature Definition of Done (DoD) ensures that all aspects of a user story are completed, tested, reviewed, and integrated into the codebase. This sequence includes all necessary steps:

Unit testing ensures the code works as expected.

Meeting the acceptance criteria ensures that the business needs are met.

Business testing and functional testing confirm the product works from both the business and technical perspectives.

Code merging ensures that the feature is integrated into the main branch.

Updating documentation ensures that the product is well-documented for future reference and use.

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.

To promote transparency in an agile environment, the scrum master should ensure that key information about the team ' s work, progress, and velocity is easily accessible and visible to everyone. Radiating information in a common area, such as a team room or workspace, fosters openness and ensures that all team members and stakeholders can quickly understand the status of the project. This encourages shared understanding and promotes collaborative problem-solving.

The correct answer is A – Plan activities that will require the team to work collaboratively on a regular basis.

Agile teams thrive on collaboration, shared ownership, and collective problem solving. While individual performance may meet goals short-term, long-term value and quality come from integrated teamwork. An agile practitioner should help foster collaboration through team-building activities or practices like pair programming, collective backlog grooming, and swarming.

From the PMI Agile Practice Guide:

“Agile teams are self-organizing and collaborative. Encouraging collaborative practices builds trust, increases quality, and improves alignment.”

(PMI Agile Practice Guide, Section 4.1 – Building Agile Teams)

Mike Griffiths states:

“Collaboration does not happen automatically—it must be supported. Facilitating shared work and group problem-solving leads to stronger team dynamics and better outcomes.”

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

Why the other options are less effective:

B introduces rigid evaluation that contradicts agile values.

C bypasses coaching and assumes the current team can’t improve.

D ignores the growing problem of misalignment and disengagement.

Answer: A

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

The correct answer is C – The team realized that some stories were underestimated relative to other stories and reestimated as needed.

According to the data in the chart:

Backlog started at 500 points.

Points steadily decreased by 25 points per iteration for the first 3 iterations, reflecting normal velocity.

At the end of iteration 4, the backlog increased from 425 to 450 points (a 25-point jump), which indicates an increase in estimated remaining work.

In Agile, backlog point totals can increase when work is reestimated—typically because items were originally underestimated or new complexity is discovered. Reestimation reflects the evolving understanding of requirements and is a core principle of adaptive planning.

From the PMI Agile Practice Guide:

“Estimates may change as the team learns more. Agile teams inspect and adapt their understanding of the work during iteration planning and refinement. Story reestimation is normal and may result in backlog point increases.”

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

Mike Griffiths writes:

“Backlogs are dynamic. Teams may reestimate stories during grooming or retrospectives if they find that original estimates were off. This helps maintain planning accuracy and backlog integrity.”

(Mike Griffiths, PMI-ACP Exam Prep, Chapter 5 – Estimation and Backlog Refinement)

Incorrect options:

A refers to external factors not reflected in the backlog points.

B would be better handled by new backlog items, not inflating prior estimates.

D suggests increased scope/output, which would add stories but not necessarily reestimate existing ones.

Answer: C

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

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

A quick mock-up (or prototype) is a highly effective way to visually represent the product ' s features and functionality to stakeholders. This allows stakeholders to get a tangible sense of what the product will look like and how it will work. By iterating on this mock-up and adjusting it based on feedback, the team can build consensus and gain stakeholder approval more effectively. This approach encourages active collaboration and ensures that the product aligns with stakeholder expectations early in the development process.

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 correct answer is D – Set up a meeting with the stakeholder to modify the working agreement and ensure future engagement.

Agile values regular collaboration with stakeholders. When a stakeholder becomes disengaged, the first step is to address it through open communication and mutual agreement. Revisiting or modifying the working agreement helps reset expectations and reestablish commitment in a collaborative and respectful way.

From the PMI Agile Practice Guide:

“Agile teams work closely with stakeholders and set expectations through working agreements that are revisited and refined as necessary. These agreements include communication preferences and participation expectations.”

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

Mike Griffiths reinforces this:

“Creating and maintaining stakeholder engagement requires ongoing alignment of goals and expectations. When participation drops, revisit agreements and reset expectations collaboratively.”

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

Why the other options fall short:

A may help short-term but doesn’t address the root issue of misalignment or expectation gaps.

B comes across as directive rather than collaborative.

C escalates prematurely without attempting resolution directly with the stakeholder.

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.

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.

The first step for the Scrum Master should be to identify the key stakeholders as early as possible. Understanding who the key stakeholders are, such as internal or external individuals or groups that have an interest in the project, allows the team to prioritize communication and engagement with them from the outset. Identifying stakeholders early ensures that their needs and expectations can be taken into account when planning and executing the project. This helps avoid misunderstandings or misaligned goals later in the project.

The correct answer is D – Present the idea at the next ceremony attended by stakeholders to obtain their input. Agile emphasizes transparency and collaboration with stakeholders. Since the organization values security highly, decisions that impact quality or policy must be discussed openly with stakeholders who have the authority to weigh cost-benefit trade-offs.

From the PMI Agile Practice Guide:

“Agile teams embrace customer collaboration and transparency. When decisions have business or organizational implications—such as security or compliance—stakeholders must be involved in evaluating trade-offs.”

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

Mike Griffiths states:

“When teams face decisions that could impact non-functional requirements like security, these should be escalated transparently to stakeholders for evaluation.”

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

Incorrect options:

A and C could result in bias or lack of organizational alignment.

B is too late and internal-only for a business-critical concern.

Answer: D

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

The correct answer is D — Help establish the next sprint ' s goal.

The sprint goal provides a shared objective and guides the selection and execution of user stories. It is established collaboratively between the product owner and the development team at the start of sprint planning and precedes task decomposition or estimation.

PMI Agile Practice Guide:

“The team collaborates with the product owner during sprint planning to define a sprint goal. The sprint goal gives the team clarity and focus on what it intends to achieve during the sprint.”

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

Mike Griffiths reinforces:

“Effective planning starts with understanding the desired outcome of the sprint. The sprint goal aligns the team and informs prioritization and task breakdown.”

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

Incorrect options:

A prematurely assigns tasks, which goes against Agile’s collaborative ethos.

B and C happen later in the sprint planning process after defining the sprint goal.

Answer: D

—

The correct answer is C – Initiate an estimation session because agile planning is iterative and collaborative. When delivery timing is in question, especially during a release planning session, the team must first estimate the size of the work (epics and user stories). Once estimates are made (often using story points or relative sizing techniques), velocity can be used to forecast delivery timelines.

From the PMI Agile Practice Guide:

“Estimation is typically performed at the beginning of a release or iteration planning session to determine how much work can be completed. Teams use estimation to size items and then apply their known or projected velocity to forecast completion.”

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

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

“Before making any delivery commitments, teams should first engage in collaborative estimation to understand the scope and effort of the work. These estimates then inform velocity-based forecasting.”

(Mike Griffiths, Chapter 5 – Adaptive Planning)

Why the other options are incorrect:

A – Scrum Masters do not estimate work; estimation is a team activity.

B – You cannot determine deliverables based on velocity until the work has been estimated.

D – Historical data can support forecasting but must be preceded by proper estimation of current backlog items.

Answer: C

The retrospective is the agile ceremony designed for teams to inspect and adapt their process based on actual performance. According to the PMI Agile Practice Guide (Section 5.6: Retrospectives), discussing velocity issues and delivery concerns during retrospectives allows the team to collaboratively identify improvement actions.

Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning) also notes that retrospectives are the best setting to discuss variations in velocity and refine estimation or planning practices based on empirical evidence.

Option C is correct: the retrospective is where the team adapts based on reality.

Option A may come later but doesn’t address the root issue.

Option B goes against agile principles of stable teams and empirical planning.

Option D is reactive and may mask underlying process issues.

After the product vision is communicated, the product owner should ensure that the product backlog is prioritized so the team can focus on delivering the most valuable features first. According to the PMI Agile Practice Guide (Section 5.1 Product Backlog and Vision Alignment), prioritizing the backlog helps teams understand the product roadmap and plan their efforts accordingly.

Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning) reinforces that the product owner’s key responsibility is backlog prioritization, not task management or detailed design.

Option C is correct: prioritizing the backlog enables the team to understand and plan the roadmap.

Option A and B are too detailed for the product owner and move into the team ' s domain.

Option D is a team responsibility, not the product owner’s.

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.

The correct answer is D – Use the team ' s historical velocity to calculate a range of features that can be delivered. Agile emphasizes forecasting over commitment, and this is achieved through empirical data such as velocity. Providing a range based on historical velocity allows for realistic planning while acknowledging uncertainty.

From the PMI Agile Practice Guide:

“Agile forecasting is based on empirical data. Teams use their past velocity to forecast how much work they can complete in a given time frame. This forecast is typically expressed as a range to account for variability.”

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

Mike Griffiths supports this:

“Rather than commit to fixed scope, agile teams use historical velocity and prioritized backlogs to forecast delivery. Forecasts are probabilistic, not promises.”

(Mike Griffiths, PMI-ACP Exam Prep, Chapter 5 – Estimation and Forecasting)

Incorrect options:

A violates agile’s core value of responding to change over following a fixed plan.

B delays valuable forecasting data.

C implies commitment rather than forecast.

Answer: D

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

The first step for a new Scrum Master is to gain context and alignment. According to the PMI Agile Practice Guide (Section 2.3: Agile Mindset), agile leaders must understand the product vision and goals to provide proper support to the team and align delivery efforts with organizational objectives.

Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 2: Agile Principles and Mindset) emphasizes that new leaders should start by understanding stakeholder expectations, enterprise context, and business drivers before making operational decisions like backlog setup or sprint planning.

Option B is correct: understanding the project vision provides critical context.

Option A is premature without first understanding the broader organizational objectives.

Option C (sprint 0) can be useful but should follow alignment on vision and context.

Option D skips necessary discovery and planning.

The correct answer is A — To better listen, serve, and help the team grow their strengths individually and as a team.

An agile coach is a servant-leader whose role is to guide the team by modeling agile values, being present, actively listening, and helping teams grow. Coaching in agile is about enabling—not controlling—the team. A coach’s mindfulness, authenticity, and presence inspire the same behaviors in the team.

PMI Agile Practice Guide notes:

“The agile coach models the agile mindset, including being present, self-aware, and aligned with agile principles. This helps the team build trust, foster collaboration, and grow capabilities organically.”

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

Mike Griffiths emphasizes:

“Effective coaches guide by example. By modeling agile values and demonstrating presence, emotional intelligence, and listening, coaches help teams unlock their full potential.”

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

Incorrect options:

B suggests control rather than collaboration.

C is anti-agile and contrary to the servant-leader model.

D is valid but lacks the depth of A, which captures the coach’s mindset and actions.

Answer: A

—

Agile teams operate on the principle of inspect and adapt. According to the PMI Agile Practice Guide (Section 5.6 Retrospectives) and PMBOK® Guide 6th Edition (Section 3.7), retrospectives are designed for experimentation and safe failure. Teams should be encouraged to try new process improvements and assess their impact. If the result is not positive, it’s an opportunity for collective learning—not for blame.

Mike Griffiths states in his PMI-ACP Exam Prep Book (Chapter 7: Continuous Improvement) that leaders should foster a culture of experimentation, where teams are praised for trying new approaches, even if they fail. This maintains psychological safety and continuous learning.

Thus, Option A is correct: Commending the attempt and facilitating a team discussion to explore alternatives is consistent with agile values and promotes team maturity.

The correct answer is A – Perform value stream analysis to eliminate the processes with wastage. Value stream mapping is a lean and agile technique used to identify and eliminate non-value-adding activities, optimize flow, and increase delivery efficiency—especially crucial when facing tight deadlines.

From PMI Agile Practice Guide:

“Value stream mapping is used to analyze the flow of materials and information required to bring a product or service to a consumer. It helps teams eliminate waste and improve speed and quality.”

(PMI Agile Practice Guide, Section 6.4 – Continuous Improvement and Feedback Loops)

From Mike Griffiths’ PMI-ACP Exam Prep Book:

“Value stream analysis is a lean technique that helps agile teams identify delays, bottlenecks, and handoffs that waste time. When velocity lags behind expectations, understanding the end-to-end process is essential to improvement.”

(Mike Griffiths, Chapter 7 – Continuous Improvement)

Option B (removing high-risk stories) may introduce more long-term risk and undermine value.

Option C suggests manipulating metrics instead of addressing root causes.

Option D may help identify risks early, but it doesn’t address why velocity is low.

Answer: A

The correct answer is C — Call an onsite meeting where ground rules will be discussed and agreed upon.

When multiple distributed teams begin working together, the first priority is to establish common ground rules, expectations, and working agreements. This sets the foundation for effective communication and collaboration. An initial face-to-face (or virtual face-to-face) meeting is often critical for forming trust and shared norms.

PMI Agile Practice Guide:

“Teams should establish working agreements early in the project. These define expectations for communication, decision-making, and collaboration—especially critical for distributed or cross-functional teams.”

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

Mike Griffiths:

“Setting ground rules helps build team cohesion, especially in distributed teams. It ensures that all members agree on protocols for meetings, updates, and decision-making.”

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

Incorrect options:

A is important but typically follows after agreements are in place.

B is routine communication—not the first foundational step.

D supports cohesion but does not establish operational alignment.

Answer: C

—

Agile teams evaluate new tools or technologies through spikes—time-boxed research or experimentation tasks. According to the PMI Agile Practice Guide (Section 5.2: Spikes and Exploration) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning), the appropriate way to introduce new technology is to engage the team in the decision and create a backlog item for a spike to evaluate its viability.

Option C is correct: it follows agile collaboration and backlog grooming practices.

Option A skips team consensus and formal prioritization.

Option B contradicts self-organizing team principles.

Option D may delay necessary action and is better suited for process discussions, not technical trials.

The correct answer is D — Ensure that planning and prioritizing includes consideration of security requirements.

Non-functional requirements (such as security, performance, or compliance) must be included in backlog prioritization and planning sessions. Agile teams must incorporate these concerns into their definition of done and acceptance criteria to ensure continuous compliance and product integrity.

PMI Agile Practice Guide emphasizes:

“Non-functional requirements (NFRs) must be prioritized and planned for alongside functional user stories. They are not optional, and failure to include them early often leads to system failure or technical debt.”

(PMI Agile Practice Guide, Section 5.3 — Planning Considerations)

Mike Griffiths writes:

“Agile teams should treat NFRs as constraints that are baked into every sprint. Rather than isolating them, they should be considered in backlog refinement and story definition.”

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

Other options:

A may help, but meeting agendas alone are not sufficient for managing NFRs.

B may assist with knowledge, but it doesn’t guarantee prioritization.

C implies treating the NFR as a risk rather than a core requirement.

Answer: D

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.

Before the workshop, the team members should read and identify relevant user stories from the product backlog that directly contribute to the goal of developing the feature for receiving and resolving customer complaints. This ensures that the stories being worked on are well-understood and aligned with the release goal.

The team should also consider the possible risks associated with each selected user story, such as technical challenges or dependencies. Additionally, they should evaluate the value each story adds to the final user (customer), ensuring that the team focuses on delivering maximum value in the release.

Velocity is a measure of the amount of work a team can handle during a sprint, typically measured in story points. While it can fluctuate slightly from sprint to sprint, the goal is to have velocity stabilize over time, as this helps in forecasting future sprints and planning. An increase in velocity from 27 to 35 could indicate an improvement in the team ' s capacity to deliver, which should be celebrated if it aligns with the team ' s capabilities. However, a stable velocity over time is what typically matters for predictability and planning.

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).

When the team determines that the highest-priority item will take longer than expected in the current sprint, it is essential to engage the product owner. The product owner is responsible for maintaining the product backlog and defining the priority of work items. By scheduling a meeting with the product owner, the team can collaboratively reassess the priorities and make adjustments based on the evolving understanding of the work required.

The product owner can help determine if the current high-priority item should be moved to the next sprint or if other adjustments to the backlog are needed. This ensures that the team is always focused on delivering the most valuable work within the given sprint time frame. Engaging with the product owner fosters collaboration and ensures alignment between the team and stakeholders, maintaining flexibility and focus on delivering customer value.

Velocity is a team-specific, relative measure of work done in a sprint and should not be used to compare teams. The PMI Agile Practice Guide (Section 5.4: Estimation and Velocity) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning) highlight that a consistent and predictable velocity is more valuable than simply trying to exceed estimates, which can lead to overcommitment or burnout.

Option C is correct: predictability and consistency are hallmarks of agile maturity.

Option A and B falsely equate velocity across teams.

Option D values overperformance, which may undermine sustainable pace.

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

In a newly formed team, especially in a regulated environment like pharmaceuticals, guiding the team to collaborate effectively and share knowledge is essential. As the team lacks subject matter expertise, fostering an environment of continuous learning and collaboration will help them quickly build knowledge and improve their performance.

It is crucial to organize a meeting to clarify roles and responsibilities. This ensures everyone understands their individual contributions and how they relate to the team’s goals. Clear role definitions are particularly important in a cross-functional team to avoid confusion and ensure smooth collaboration.

The correct answer is D — Explain to the team the importance of reducing team size by reducing specializations and bottlenecks and that every team member plays an equal part.

Agile promotes cross-functional, self-organizing teams where all members are responsible for delivering a working product increment. Avoiding specialized silos reduces bottlenecks and improves overall flow. Everyone contributes based on team needs, not personal preferences or status.

PMI Agile Practice Guide:

“Agile teams minimize individual silos by encouraging cross-functional collaboration. Everyone contributes to the team goal, even if the task is outside their core skillset.”

(PMI Agile Practice Guide, Section 6.1 – Team Composition)

Mike Griffiths:

“Specialization often becomes a bottleneck in agile teams. Agile promotes generalizing specialists—team members who are willing to stretch outside their expertise to help the team meet its goals.”

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

Incorrect options:

A promotes a command-and-control model—contrary to Agile servant leadership.

B reinforces silos and inefficiency.

C contradicts Agile’s emphasis on team ownership.

Answer: D

—

The correct answer is A — A formalized agile approach offers controlled flexibility in dealing with unknown variables in a manner that adds business value.

Agile is designed to operate effectively under conditions of high uncertainty. It allows for controlled experimentation, feedback loops, and adaptive changes, all while maintaining a focus on delivering business value. This makes it ideal for environments reliant on data analytics and frequent changes.

PMI Agile Practice Guide:

“Agile approaches provide the flexibility to respond to changing conditions and unknowns while ensuring that value delivery remains aligned with stakeholder needs.”

(PMI Agile Practice Guide, Section 2.2 – Agile Principles)

Mike Griffiths:

“Agile’s incremental delivery model enables teams to validate assumptions and adapt based on feedback and data—making it a natural fit for data-driven organizations.”

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

Incorrect options:

B is factually incorrect and overly simplistic.

C misrepresents agile as a formal change-control process.

D is an opinion, not a principle.

The correct answer is A – Use the DISC framework with each team member.

The DISC model (Dominance, Influence, Steadiness, and Conscientiousness) is a well-established behavioral assessment tool used to understand communication preferences, motivators, and individual work styles. Agile leaders may use tools like DISC to foster emotional intelligence, improve collaboration, and re-engage disengaged team members.

From the PMI Agile Practice Guide:

“Effective agile leaders understand individual team members ' communication styles and motivations. Tools such as DISC or MBTI can help assess personality preferences and enable better coaching.”

(PMI Agile Practice Guide, Section 6.2 – Coaching Agile Teams)

Mike Griffiths notes:

“Behavioral models such as DISC support the development of emotionally intelligent teams. They help leaders tailor their coaching and communication approaches to individual needs.”

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

Why other options are incorrect:

B (MoSCoW) is a prioritization technique, not a tool for personal engagement.

C (Hiring a SAFe coach) is overkill and not the most direct or relevant response.

D (BDUF – Big Design Up Front) is a traditional approach unrelated to team dynamics or motivation.

Answer: A

In Agile, changes are expected and are part of the iterative process. The product owner should take the opportunity to coach the stakeholder on agile principles, explaining how continuous feedback, flexibility, and adaptability are core to delivering value in an Agile project. Instead of pushing back on changes, the product owner can help the stakeholder understand that responding to change helps improve the product and better meet user needs. This helps align the stakeholder ' s expectations with Agile practices and fosters better collaboration throughout the project.

A cumulative flow diagram (CFD) is a powerful tool to visualize the flow of work across different stages of the process and identify where bottlenecks are occurring. By using a CFD, the team can see the buildup of work in specific columns, such as the " Ready to be tested " queue, and determine where delays are happening. Identifying bottlenecks is the first step in improving flow and addressing the slower delivery. Once the bottleneck is identified, the team can make adjustments to improve speed, such as optimizing the testing process or redistributing workload.

The correct answer is C – Invest in technology-collaboration tools to enable effective communication and ensure a common understanding of the scope, issues, and solutions.

Agile encourages high-bandwidth communication, preferably face-to-face. However, when working with distributed teams, modern collaboration tools serve as essential enablers of shared understanding and timely feedback, reducing the risk of miscommunication and rework.

From the PMI Agile Practice Guide:

“While agile prefers face-to-face communication, geographically dispersed teams must rely on tools to mimic these interactions as closely as possible. These include video conferencing, online whiteboards, and real-time collaboration platforms to create a shared understanding.”

(PMI Agile Practice Guide, Section 2.3 – Communication and Collaboration)

Mike Griffiths supports this as well:

“Remote teams need strong communication enablers. Collaboration tools help mitigate the challenges of distributed work by enabling transparency, synchronous discussions, and shared visibility of the work.”

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

Why the other options are less appropriate:

A assumes majority rule over inclusive engagement.

B is often impractical and does not reflect Agile’s adaptability.

D is vague and lacks actionable commitment.

Answer: C

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

Step 1: Identify Total Story Points in the Backlog

From the backlog table:

Total story points = 6 + 4 + 8 + 4 + 21 + 7 + 5 + 9 + 3 + 5 = 72

Step 2: Determine the Team ' s Velocity

The risk register mentions a burn reduction of 1 story point per sprint from sprint 4 to sprint 6 due to a holiday schedule. However, assuming a normal velocity of 5 story points per sprint, we can estimate sprint completion.

Normal sprint velocity: 5 story points per sprint

Reduced velocity for sprints 4-6: 4 story points per sprint

Step 3: Calculate Total Sprints Needed

First 3 sprints: 5 points per sprint → 5 × 3 = 15 story points completed

Sprints 4-6: 4 points per sprint → 4 × 3 = 12 story points completed

Remaining story points after sprint 6: 72 - (15 + 12) = 45 story points

Remaining sprints needed at normal velocity (5 story points per sprint): 45 ÷ 5 = 9 sprints

Total Sprints Required

Sprints 1-6: Already planned.

Additional 9 sprints needed.

Total sprints to complete the backlog: 6 + 9 = 15 sprints.

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 Definition of Done (DoD) is a crucial agile practice that outlines the agreed-upon criteria for when a deliverable is considered complete and ready for release. It ensures that all aspects of the deliverable meet the necessary standards and requirements before it is finalized. Additionally, the team should demonstrate the deliverable, typically during a sprint review or other appropriate meeting, to confirm that it meets stakeholder expectations and aligns with the project goals. This practice helps ensure that the deliverables are truly complete and ready for release, avoiding rework and maintaining a high level of quality.

The in-person demonstration meeting is crucial because it allows the team to directly engage with the product owner, ask clarifying questions, and immediately address any feedback or concerns. This fosters better communication, understanding, and collaboration between the team and the product owner. Being able to have a real-time conversation helps the team ensure they are building the right product, and it allows the product owner to provide nuanced feedback that might not be as clear through asynchronous communication (like sending a link).

The face-to-face interaction provides an opportunity for both parties to align more effectively on the product vision, avoid misunderstandings, and prevent misalignment on priorities, ultimately ensuring that the product being developed meets expectations.

The agile lead is emphasizing the importance of creating a safe environment for disagreement, which encourages constructive conflict. In Agile, this is crucial because it allows team members to openly express differing opinions and perspectives. Such discussions often lead to better decision-making by surfacing various viewpoints and potential solutions. When teams feel safe to disagree, it fosters creativity, innovation, and problem-solving without fear of retribution. This aligns with Agile principles of collaboration, transparency, and continuous improvement.

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.

The correct answer is A – Kaizen. Kaizen is a Japanese term meaning " continuous improvement. " In Agile, Kaizen refers to the practice of regularly reflecting on processes and results, then making incremental improvements. By tracking impediments and resolving them transparently, the team engages in Kaizen behavior.

From the PMI Agile Practice Guide:

“Agile teams embrace a mindset of continuous improvement (Kaizen), regularly inspecting their work and processes and adapting them for better outcomes.”

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

Mike Griffiths writes:

“Agile is rooted in lean thinking, including Kaizen. Teams reflect on what went well and what needs to change, often using tools like Kanban boards to visualize and track improvements.”

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

Incorrect options:

B refers to goal-setting, not process improvement.

C are metrics, not an outcome of experimentation.

D (Muda) refers to waste, which Kaizen seeks to reduce.

Answer: A

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

The correct answer is A – Conduct frequent demos and obtain feedback from users throughout the development of the next release. Agile is feedback-driven. Regular demonstrations (e.g., sprint reviews) help gather customer input to continuously enhance the product and optimize value.

From the PMI Agile Practice Guide:

“Frequent demonstrations and validation with stakeholders ensure that teams deliver value continuously and adapt the product based on real-time feedback.”

(PMI Agile Practice Guide, Section 5.2 – Feedback and Product Review)

Mike Griffiths notes:

“Customer feedback loops are vital to agile. Demos provide a mechanism for validating delivered functionality, identifying improvement opportunities, and maximizing product value.”

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

Incorrect options:

B contradicts continuous delivery and customer collaboration.

C may help with scale, but doesn’t directly address value improvement.

D is more about process quality than business value.

Answer: A

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

Agile teams embrace change and collaborate with customers to deliver value. The PMI Agile Practice Guide (Section 2.1: Agile Mindset) supports responding to change—even late in the development cycle—if it results in business value. The team should accept the new goal, replan with the product owner, and adjust scope or priority if needed, rather than resist or escalate.

Option A is correct: it reflects the agile value of responding to change and delivering early value.

Option B is too rigid and contrary to agile principles.

Option C implies a punitive model that does not align with collaborative agile contracts.

Option D introduces unnecessary cost and overhead without first trying to replan collaboratively.

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.

As a scrum master, the goal is to foster a collaborative and self-organizing environment. When conflicts arise, it is essential to guide the team in resolving the issue on their own rather than making unilateral decisions. The scrum master should:

Coach the team individually to understand the root causes of the conflict and ensure each team member feels heard.

Then, bring the team together in a more structured environment, such as the Sprint review, to discuss the disagreement openly and constructively. This helps the team resolve conflicts and learn how to handle similar situations in the future.

In agile, work is considered “done” only when it meets the agreed-upon Definition of Done (DoD), which includes all aspects like coding, review, testing, and documentation. If there ' s disagreement about completion, the PMI Agile Practice Guide (Section 5.3 Sprint Review and Acceptance) recommends revisiting and aligning the DoD between the team and product owner.

Mike Griffiths in his PMI-ACP Exam Prep Book (Chapter 6: Value-Driven Delivery) explains that without a clear and shared Definition of Done, misunderstandings about completion status can occur, especially with quality-related tasks like testing.

Option A is correct because aligning on the DoD resolves current and future misunderstandings.

Option B introduces unnecessary escalation.

Option C postpones resolution and does not solve the core issue.

Option D incorrectly assumes testing isn’t part of the story’s completion criteria.

As a servant leader, one of the key responsibilities is to protect the team from external distractions and interruptions that could affect their ability to focus and deliver value. This allows the team to work in a productive environment and maintain their focus on the important tasks, such as delivering the minimum viable product (MVP). By removing impediments and guarding against distractions, the servant leader enables the team to be more effective and efficient.

The correct answer is B – Create a team norms document to set participation guidelines. Establishing team norms improves psychological safety, trust, and collaborative behavior. It provides a structured way to handle differences of opinion and ensure equal contribution.

From the PMI Agile Practice Guide:

“Team norms or working agreements are guidelines created by the team to set expectations for behavior, participation, and communication. These norms are agreed upon early and revisited as needed to support healthy collaboration.”

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

Mike Griffiths elaborates:

“High-performing agile teams create shared agreements that clarify roles, expectations, and behavior. When team conflict or disconnects arise, practitioners should guide the team to revisit or develop such norms.”

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

Incorrect options:

A lacks structure and may not address the root issue.

C delays resolution and misuses the stand-up’s purpose.

D waits too long to act; issues should be addressed immediately, not deferred.

Answer: B

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

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

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

In agile environments, planning should be flexible and adaptable to changing circumstances. Just-in-time (JIT) refinement refers to the practice of refining the backlog and details of the product features as they become more relevant, rather than attempting to plan everything upfront. This allows the team to respond to changes and new information as they emerge, which aligns with agile principles of iterative development and adaptability.

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 C – Low-risk and low-value. Agile teams prioritize features that deliver the highest value earliest while also addressing risk. Features with low business value and low risk can be deferred as they contribute the least to business objectives and present no urgency.

From the PMI Agile Practice Guide:

“Agile teams maximize value by focusing on delivering high-value and high-risk features early. Low-value, low-risk items are often deferred or dropped entirely if they don’t contribute meaningfully to customer outcomes.”

(PMI Agile Practice Guide, Section 3.4 – Prioritization Techniques)

Mike Griffiths supports this:

“Features should be prioritized by value and risk. Items with low value and low risk are the lowest priority. Delivering high-value features quickly enables feedback and learning.”

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

Incorrect options:

A should be prioritized early to mitigate risk and deliver value.

B are non-critical and risky—often avoided or discarded.

D delivers value, and therefore should be prioritized above low-value items.

Answer: C

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

The correct answer is B — The stakeholder who can prevent the project from achieving its goals.

Stakeholder prioritization is based on power and influence. Those who can significantly impact or block project success (positively or negatively) should be prioritized. This ensures their concerns are addressed and their support is cultivated early.

PMI Agile Practice Guide:

“Stakeholder engagement is critical in agile. The team must identify those who have the most influence over project outcomes and ensure early and frequent communication.”

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

PMBOK® Guide:

“Stakeholder prioritization involves assessing who has the greatest influence on project success.”

—

The correct answer is B — Hold regular retrospectives and have team members commit to specific actions.

Regular retrospectives enable the team to continuously reflect and adapt their processes and product based on new challenges or insights. Commitment to specific action items ensures accountability and fosters a culture of learning and responsiveness.

PMI Agile Practice Guide:

“Teams should hold regular retrospectives to identify areas for improvement and define concrete actions. These actions are tracked and reviewed in subsequent iterations.”

(PMI Agile Practice Guide, Section 5.8 – Retrospectives)

Mike Griffiths:

“Continuous improvement is a core agile value. Retrospectives allow teams to evaluate their performance and commit to actionable improvements.”

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

Incorrect options:

A is a waterfall mindset.

C lacks structured reflection and accountability.

D is a poor coding practice and anti-pattern.

Answer: B

—

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.

Velocity is a measure of how much work a team completes in a given sprint, typically measured in story points or other units of effort. While velocity can be useful for tracking progress and forecasting future work, it has some limitations when it comes to accurate capacity planning.

Velocity can vary from sprint to sprint due to multiple factors, such as the complexity of the tasks, interruptions, or even external influences. This variability can make it difficult to predict how much work a team can handle in future sprints, leading to inaccurate capacity planning.

To understand the needs of different user types, agile teams use personas and extreme characters to represent a range of users, including edge cases. According to the PMI Agile Practice Guide (Section 5.2: Requirements and Personas) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning), personas help teams build empathy and ensure that stories reflect actual user roles—not just generic assumptions.

Option D is correct: personas and extreme characters ensure inclusive and realistic story coverage.

Option A and B focus on communication and sequencing but not user diversity.

Option C (process flows) is more technical and doesn’t solve the misalignment with user perspectives.

Velocity is a team-specific metric and cannot be reliably estimated until the team has worked together for several sprints. According to the PMI Agile Practice Guide (Section 5.4 Sprint Planning and Velocity Tracking), velocity should be measured empirically, not predicted based on assumptions or external input.

Mike Griffiths (PMI-ACP Exam Prep Book, Chapter 6: Adaptive Planning) emphasizes that new teams need to run a few sprints to establish a reliable velocity through real performance data, not estimation.

Option D is correct: actual performance determines true velocity.

Option A and B rely on speculation.

Option C incorrectly uses sponsor input for team planning, which goes against agile principles.

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.

The correct answer is D — Engaged key stakeholders periodically to collect requirements.

Agile is based on frequent stakeholder collaboration. Continuous engagement ensures evolving needs are captured and prevents misalignment. Waiting for planning meetings or demos is too late to catch missing input.

PMI Agile Practice Guide:

“Agile teams ensure stakeholder engagement is ongoing throughout the project. This helps validate requirements and prevent surprises during reviews.”

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

Mike Griffiths:

“Stakeholders should be consulted early and often. Relying on static requirements leads to gaps. Agile teams maintain constant feedback loops.”

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

Incorrect options:

A is too early and one-time.

B may help but is reactive.

C is a predictive approach inconsistent with agile.

Answer: D

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.

The information radiator is a key tool in Agile that provides a real-time, visual display of the project ' s current status, including progress, completed tasks, blockers, and upcoming work. This is typically made accessible to all stakeholders and is updated regularly to ensure transparency and communication. Instead of relying on emails or meeting invites, the Scrum Master should direct the customer representative to the information radiator, as it provides the most up-to-date and easily accessible information about the project’s progress. This encourages transparency and aligns with Agile principles of open communication and visibility.

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 A — Teach the team the appropriate agile principle, obtain consensus, and drive adoption.

Agile values “working software over comprehensive documentation.” However, this does not mean eliminating all documentation, but rather focusing on documentation that delivers value.

PMI Agile Practice Guide states:

“Agile teams should regularly question whether the work being done adds value, including documentation. If documentation does not serve a current need or stakeholder, it should be minimized or eliminated.”

(PMI Agile Practice Guide, Section 2.2 — Agile Manifesto)

Mike Griffiths further supports this in his exam prep book:

“Agile team members are encouraged to surface inefficiencies and suggest improvements. This is an example of continuous improvement and shared responsibility.”

Option A aligns with both the Agile Manifesto and the principle of team empowerment. Options B, C, and D either avoid accountability or introduce hierarchy that agile teams seek to minimize.

Answer: A

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

The correct answer is A – The Agile team should engage stakeholders regarding the proposed designs and ensure that sufficient engagement occurs throughout the project in an adaptive way.

Agile thrives on continuous stakeholder engagement. Ignoring feedback or rigidly sticking to past decisions defeats Agile ' s principle of responding to change over following a plan. Even if designs have been created, collaboration must continue.

From the PMI Agile Practice Guide:

“Engaging stakeholders early and often helps ensure alignment and mitigates late surprises. Adaptive planning allows for feedback and refinement throughout the lifecycle.”

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

Mike Griffiths emphasizes:

“Stakeholder collaboration and frequent inspection are cornerstones of Agile. Late feedback is better than no feedback. Teams must adapt.”

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

Other options:

B discourages collaboration.

C emphasizes documentation over interaction.

D is drastic and unnecessary.

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 B — Set the velocity to the delivered story points of the last sprint.

Agile velocity is a historical measure, not a target. It represents the amount of work a team actually completed in a previous sprint and should be used to help guide future sprint planning. Teams should not inflate, manipulate, or " game " their velocity; instead, they should use it as a basis for realistic planning.

PMI Agile Practice Guide states:

“Velocity is calculated by totaling the points for all fully completed stories. It is a measure of what the team can complete—not what it hopes to complete—and should be used as an empirical baseline for planning.”

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

Mike Griffiths further explains:

“Velocity should be based on historical data from previous sprints. Teams should not artificially inflate velocity by changing estimation practices or slicing stories merely to appear more productive.”

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

Incorrect options:

A promotes splitting for manipulation, not for clarity.

C suggests altering estimation practices for the sake of metrics.

D implies gaming the system to falsely increase velocity.

Answer: B

—

The correct answer is C — Ask probing questions to other team members to encourage dissenting viewpoints.

Agile coaches foster team collaboration and help surface diverse opinions. When one member dominates, the coach should use facilitation techniques to ensure equal voice. Encouraging quieter team members to contribute through thoughtful questions promotes balanced participation and trust.

PMI Agile Practice Guide:

“Agile coaches foster an environment of trust and collaboration. When team dynamics are unbalanced, the coach helps ensure psychological safety and equal participation.”

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

Mike Griffiths:

“Coaches use powerful questions to draw out quieter team members and help build a culture where everyone feels heard and valued.”

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

Incorrect choices:

A is extreme and non-collaborative.

B ignores the coach’s facilitative responsibilities.

D is reactive and too late.

—

The correct answer is C – The users can help the team understand if the feature adds value, avoiding the risk of building the wrong product.

Prototyping in agile serves as a lightweight modeling technique that supports discovery and stakeholder validation. It helps clarify uncertain requirements, encourages collaboration, and ensures that the solution being developed meets user needs and delivers value.

From the PMI Agile Practice Guide:

“Prototypes allow teams to explore solutions before committing to full development. They support value delivery by engaging users early to verify what is needed.”

(PMI Agile Practice Guide, Section 5.2 – Exploring and Confirming Requirements)

Also:

“Engaging stakeholders in early solution validation through techniques such as wireframes or mockups reduces the risk of developing the wrong product.”

(PMI Agile Practice Guide, Section 3.4 – Delivering Value Frequently)

Mike Griffiths reinforces this approach:

“Prototyping enhances discovery. It supports feedback loops that validate whether a feature adds value before it ' s built—especially useful when requirements are unclear.”

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

Why other options are less correct:

A is a secondary benefit but not the primary goal of prototyping.

B is speculative and does not reflect the sponsor ' s actual recommendation.

D misrepresents the purpose of prototyping, which is for discovery, not accelerated deployment.

Answer: C

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

A team charter with clearly defined norms, rules, and agreements is a critical tool for promoting trust and collaboration, especially in a globally distributed team. It establishes a shared understanding of how the team will work together, addresses potential communication challenges, and helps create a collaborative and respectful environment. By having these norms in place, team members from different cultures and time zones can align their expectations and behaviors, which is essential for overcoming challenges and preventing conflicts. This approach helps to foster a positive and productive team dynamic.

The correct answer is C — Conducted an end-of-phase demonstration.

Agile emphasizes continuous feedback. Regular demonstrations (e.g., sprint reviews or product demos) allow stakeholders, including the customer, to inspect the product increment and provide real-time feedback. Had the team demoed the product, they might have discovered the deficiencies before release.

PMI Agile Practice Guide states:

“A demo or review allows stakeholders to inspect the product increment and provide feedback. Demonstrations reduce the risk of unmet expectations and confirm that the team is building the right product.”

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

Mike Griffiths writes:

“Agile avoids large, end-of-phase validations. Instead, customer feedback is solicited at the end of every iteration through structured demos. This allows for early course correction and alignment with expectations.”

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

Other options:

A is a waterfall artifact and not aligned with agile workflows.

B is analysis-heavy and doesn’t ensure real stakeholder feedback.

D (retrospective) improves process, not product validation.

Answer: C

The Scrum Master should help ensure that stakeholders understand Agile principles and terms correctly to facilitate smooth decision-making. Organizing training sessions is an effective way to address misunderstandings and create awareness around Agile values. By ensuring all stakeholders are on the same page, the team can move forward with a shared understanding, which is critical for successfully implementing Agile methodologies. This approach promotes long-term buy-in and alignment, rather than simply pushing for a decision without proper education or consensus.

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

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

As a servant leader, the agile coach’s role is to support and empower the team, helping them overcome obstacles that hinder their progress. In this case, the coach should focus on identifying and removing any impediments that are slowing down the work, whether they are technical, process-related, or communication-based. This approach enables the team to work more efficiently, enhances their ability to self-organize, and ensures they can deliver high-quality results. Simply adjusting the work plan or assigning more resources may not address the underlying issues, and a command-and-control approach is counterproductive in an Agile environment.

The correct answer is B – Suggest the Product Owner prioritize the work items by feature to maximize value.

In Agile, the Product Owner is responsible for backlog prioritization. When multiple stakeholders have differing priorities, it is the Product Owner’s job to evaluate business value and ROI to determine which features deliver the most value and should be addressed first.

From the PMI Agile Practice Guide:

“The Product Owner works closely with stakeholders to ensure that the most valuable work is prioritized in the backlog. When multiple stakeholders have competing interests, the Product Owner helps mediate and prioritize based on value delivery.”

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

Mike Griffiths adds:

“Agile avoids trying to define all requirements up front. Instead, the backlog is groomed regularly, and the Product Owner ensures that the team is working on the highest value features.”

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

Other options are less effective:

A contradicts Agile principles by suggesting complete upfront requirement definition.

C puts responsibility on the customer instead of the empowered Product Owner.

D implies a waterfall approach by requiring clarity before starting.

Answer: B

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

The correct answer is D – Write tests that will be used to know when a story has been correctly developed. This practice aligns with Test-Driven Development (TDD) and Acceptance Test-Driven Development (ATDD), which are common in agile environments. Agile promotes defining “done” through clear acceptance criteria and tests before coding begins.

From PMI Agile Practice Guide:

“Agile teams use test-first practices, such as TDD or ATDD, where acceptance tests are written before development begins. This ensures that functionality is built to meet agreed expectations.”

(PMI Agile Practice Guide, Section 5.5 – Agile Testing and Quality Strategies)

From Mike Griffiths’ PMI-ACP Exam Prep Book:

“Defining acceptance criteria or tests before development is a core agile practice. It ensures the team understands what success looks like and builds quality in from the start.”

(Mike Griffiths, Chapter 6 – Problem Detection and Resolution)

Option A may be useful but is unrelated to the new requirements.

Option B is not standard—customers help define acceptance criteria but rarely write tests.

Option C skips an important quality control step and doesn’t align with test-first practices.

Answer: D

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

The correct answer is C – Ensure the team captures the technical dependencies as issues within the backlog and prioritize based on value optimization. In Agile, technical considerations are factored into backlog refinement and sprint planning. Dependencies should be visualized and managed as part of adaptive planning while still striving to deliver maximum value.

From the PMI Agile Practice Guide:

“Backlog items with technical dependencies should be identified and addressed collaboratively. Agile teams balance value with feasibility and technical constraints to optimize delivery.”

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

Mike Griffiths explains:

“While business value drives prioritization, technical constraints influence the ordering of stories. Agile planning is adaptive; dependencies and delivery risks are identified early and managed through backlog reordering.”

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

Incorrect options:

A may discard valuable features unnecessarily.

B risks accumulating technical debt and incomplete work.

D shifts responsibility away from the team and PO unnecessarily.

Answer: C

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

The burndown chart displayed shows two lines:

A diagonal guideline (ideal trend line) representing the expected or planned burndown rate.

A line with plotted black squares representing the actual progress of work completed during the iteration (typically in story points or hours).

The actual progress line (with black squares) stays consistently above the ideal line throughout the iteration.

This indicates that less work was completed than planned at each point in time.

Toward the end of the iteration (around the 30th or 31st), the chart shows that the total remaining work does not reach zero—implying incomplete work by the iteration’s end.

Analysis of the Chart:Interpretation According to Agile Standards:According to the PMI Agile Practice Guide (Section 5.4: Tracking Iteration Progress) and Mike Griffiths ' PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning):

A burndown chart that remains above the ideal line and does not reach the baseline (zero) by the end of the iteration reflects that the team is behind schedule and did not complete all planned work.

The burndown chart is a primary information radiator for evaluating scope completion versus time and is a critical tool for monitoring iteration performance.

Therefore:

Option C is correct:

" It trended behind schedule and did not complete everything on time. "

Option A is incorrect — the chart clearly shows a lag behind schedule.

Option B is incorrect — there is no indication that the iteration time box was extended.

Option D is incorrect — the team did not finish early or complete all tasks.

The correct answer is C – Encourage all feedback then work with the customer to prioritize work for future sprints. Agile welcomes continuous feedback and values customer collaboration. All feedback should be collected and considered, but the product backlog is reprioritized to align with capacity and business goals.

From the PMI Agile Practice Guide:

“Agile promotes constant feedback to refine product direction. Feedback is incorporated into the backlog, prioritized based on value, and delivered incrementally according to capacity.”

(PMI Agile Practice Guide, Section 3.4 – Value-Driven Delivery and Continuous Customer Collaboration)

Mike Griffiths adds:

“Stakeholder feedback is essential in agile. Not all feedback can be implemented immediately, but it should be welcomed, evaluated, and prioritized transparently in collaboration with the product owner and stakeholders.”

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

Incorrect options:

A implies a heavy process not aligned with agile.

B prematurely limits feedback before collaborative prioritization.

D ignores the product owner’s prioritization role.

Answer: C

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

In Scrum, responsibilities are distributed among the product owner, scrum master, and development team to ensure clear accountability and efficient value delivery.

The product owner manages the product backlog, ensures alignment with business goals, and defines the priorities for the team.

The scrum master facilitates the Scrum process, removes impediments, and ensures adherence to Agile principles.

The development team owns the sprint backlog and is responsible for incremental delivery toward the sprint goal.

This division of responsibilities ensures that each role focuses on their core areas, fostering transparency, collaboration, and value-driven development.

In agile, information radiators—such as visual boards placed in common areas—are used to make project data accessible, transparent, and real-time. According to the PMI Agile Practice Guide (Section 7.1 Communication), visibility improves coordination across interdependent teams.

Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 4: Stakeholder Engagement) recommends that agile teams use visible, shared artifacts such as task boards, burn charts, or Kanban walls to improve cross-team communication and reduce friction.

Option B is correct: a physical or virtual board offers transparency and encourages informal communication.

Option A is useful but not as effective for rapid visibility.

Option C is one-way and doesn’t support real-time updates.

Option D is reactive and could cause delays or misalignment.

The correct answer is A — Practicing the servant leadership style of working with an agile team.

Servant leadership is foundational to Agile. The agile project leader serves the team by removing impediments, supporting their needs, and promoting transparency. Using information radiators and being involved in team progress reflects servant leadership in action.

PMI Agile Practice Guide:

“Agile leaders act as servant leaders. They support the team, remove obstacles, and foster a transparent, collaborative environment.”

(PMI Agile Practice Guide, Section 6.2 – Coaching and Servant Leadership)

Mike Griffiths:

“Servant leadership is about enabling the team to succeed. Agile leaders serve by ensuring the team has what it needs, while maintaining visibility through information radiators.”

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

Incorrect options:

B and C are valid Agile behaviors but not the most specific or complete match.

D references feedback loops but not leadership style.

Answer: A

—

In Scrum, the goal is to have open discussions during estimation, where all team members, including junior developers, can express their thoughts and assumptions. The Scrum Master should encourage the junior developers to keep their estimations because these can highlight different perspectives, constraints, or assumptions that others may not have considered. This helps create a more comprehensive understanding of the work and fosters a collaborative environment. It also builds confidence in junior team members, allowing them to contribute more effectively and learn from their peers in the process.

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.

Value stream mapping is a key Lean technique used to visualize the sequence of steps involved in delivering value to customers. It maps out both the value-creating activities and the non-value-creating activities (waste), providing a clear view of the entire process. This helps identify inefficiencies and opportunities for improvement to optimize the flow of value.

The correct answer is D – Estimating the relative size of stories by using story points.

Planning poker is a consensus-based estimation technique used in Agile to assign relative size (often using story points) to product backlog items. Each team member selects a card to indicate their estimate, and the group discusses discrepancies to reach agreement.

From the PMI Agile Practice Guide:

“Planning poker is a consensus-based estimation technique that helps teams estimate the size of user stories using story points. It supports collaboration and shared understanding.”

(PMI Agile Practice Guide, Section 5.3 – Estimation Techniques)

Mike Griffiths writes:

“Planning poker helps teams perform relative sizing using a modified Fibonacci sequence. The goal is not precision, but shared understanding and relative complexity comparison.”

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

Why other options are incorrect:

A describes analogy-based estimation, not planning poker.

B refers to “bucket system” estimation, a separate technique.

C refers to dot voting, which is a prioritization—not estimation—tool.

Answer: D

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

In agile, early and frequent feedback from stakeholders and clients is critical to ensure that what is being built delivers the intended value. The PMI Agile Practice Guide (Section 5.5 and Section 7.2.2) promotes regular product review sessions (e.g., sprint reviews) with stakeholders to validate progress and obtain immediate feedback.

Mike Griffiths (PMI-ACP Exam Prep Book, Chapter 6: Value-Driven Delivery) explains that product validation is continuous and not left to the end of the project. Regular review sessions allow clients to confirm that the product meets expectations, reducing the risk of building the wrong solution.

Therefore, Option D is correct: holding product review sessions with the client aligns with agile values of transparency, collaboration, and value delivery.

The correct answer is D – The Product Owner is responsible for both the budget and the release plans.

In Scrum and Agile frameworks, the Product Owner acts as the voice of the customer and is responsible for maximizing the value of the product. This includes managing the product backlog, prioritization, and release planning. Additionally, in Agile environments, budget management—especially in terms of what value is delivered with what investment—is a key aspect of the Product Owner’s role.

From the PMI Agile Practice Guide:

“The Product Owner manages the backlog and prioritizes work based on value delivery. The Product Owner is also typically responsible for budgeting and release planning, often in collaboration with stakeholders.”

(PMI Agile Practice Guide, Section 5.2 – Roles and Responsibilities)

Mike Griffiths adds:

“Release planning and value-based budget decisions fall under the Product Owner’s responsibilities, as they are closest to business stakeholders and value prioritization.”

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

Why other options are incorrect:

A is partially correct but misplaces budget responsibility.

B is traditional and does not reflect Agile delegation to the team and Product Owner.

C promotes team ownership but budget and release planning specifically lie with the Product Owner.

Answer: D

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

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 C – Work with product owners and turn product backlog items into potentially shippable product increments.

Agile is grounded in the principle of delivering value early and often. Agile teams deliver value by continuously converting high-priority product backlog items into working software or product increments. These increments are potentially shippable, meaning they meet the Definition of Done and could be released at any point if the business chooses. Collaboration with the product owner ensures that the most valuable features are prioritized and refined before development begins.

From PMI Agile Practice Guide:

“Agile teams focus on delivering small, valuable, and potentially shippable increments of working product on a regular basis. This allows for frequent feedback and ensures that teams are always working on the most valuable features.”

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

From Mike Griffiths’ PMI-ACP Exam Prep Book:

“Working software is the primary measure of progress in agile projects. Agile teams collaborate with product owners to break down backlog items into increments that can be developed, tested, and delivered within a single iteration.”

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

Option A contradicts agile principles, which emphasize cross-functional teams capable of analysis, development, and testing.

Option B is a supporting activity but does not directly increase value delivery.

Option D reflects traditional project management thinking and does not align with the iterative, adaptive nature of agile.

Answer: C

The correct answer is D – Ensured that the team was comprised of cross-functional, generalized specialists.

Agile teams are expected to be cross-functional and self-sufficient. A lack of a required skill that halts progress typically points to an improperly constructed team. Building teams with broad (T-shaped) skills ensures they can collectively deliver value without external dependencies.

From the PMI Agile Practice Guide:

“Agile teams are ideally composed of cross-functional members who have both depth in a specialty and breadth across disciplines. This enables the team to self-organize and deliver complete increments of value.”

(PMI Agile Practice Guide, Section 4.1 – Building Agile Teams)

Mike Griffiths elaborates:

“Agile favors generalized specialists or T-shaped professionals who can collaborate across functions. This improves agility, resilience, and continuity within iterations.”

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

Why the other options are insufficient:

A is a reactive strategy; proactive skill assessment is preferred.

B may delay critical features unnecessarily.

C creates external dependencies, which agile seeks to avoid.

Answer: D

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

The correct answer is B – Recommend an Agile delivery approach and provide information to the stakeholders on Agile values and principles.

Agile enables early and continuous delivery of valuable software, short feedback loops, and faster time to market. When competitive advantage and speed are critical, introducing Agile principles allows the organization to remain flexible, respond to change, and deliver increments faster.

From the PMI Agile Practice Guide:

“Agile approaches provide quicker feedback, faster time to market, and more opportunity to deliver business value early. They are ideal in dynamic environments with evolving customer needs.”

(PMI Agile Practice Guide, Section 1.3 – When to Use Agile)

Mike Griffiths states:

“Agile emphasizes early and continuous delivery, allowing organizations to test, learn, and adjust quickly to changes—critical for achieving business agility and competitive advantage.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 1 – Agile Mindset)

Why other options are not optimal:

A suggests a predictive mindset and planning before implementation.

C focuses only on Scrum roles, which may be too narrow for organizational-level change.

D relies on traditional governance structures that may resist Agile change.

Answer: B

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

To effectively address blockers and minimize their occurrence, the team should first analyze the root causes of the blockers. By grouping them and identifying patterns, the team can understand the common causes of delays and take targeted actions to eliminate or mitigate these issues. This practice aligns with continuous improvement in Agile, where teams reflect on their processes, identify areas of inefficiency, and adapt their workflow to reduce future blockers and lead times. This approach allows the team to address the underlying issues and make process improvements that benefit future sprints.

The correct answer is B – The entire team is responsible for quality, but each team member ' s role may vary as stated in the definition of done (DoD).

In Agile, quality is a shared responsibility. While specialists like QA may have defined roles, all team members are expected to contribute to maintaining and improving product quality. The Definition of Done (DoD) captures shared criteria for acceptance and completion.

From the PMI Agile Practice Guide:

“Agile teams are cross-functional and collectively accountable for quality. Specific roles may perform different tasks, but everyone contributes to ensuring the product meets the agreed-upon standards.”

(PMI Agile Practice Guide, Section 5.2 – Quality and Definition of Done)

Mike Griffiths clarifies:

“Quality is everyone’s responsibility. Teams should define what ' done ' means and ensure that all members understand and uphold those standards during development.”

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

Why other options fall short:

A implies all members must be involved in every component, which may not be efficient or realistic.

C incorrectly assigns surprises or gaps solely to QA.

D misrepresents the Product Manager ' s role and overemphasizes top-down functionality.

Answer: B

The product owner is responsible for managing the product backlog and ensuring that it reflects the priorities and vision of the product. While the Scrum team can suggest changes or improvements during the refinement process, the product owner has the final say on what changes are made to the backlog. This ensures that the product backlog aligns with business needs, stakeholder expectations, and the overall product vision. Therefore, the product owner can reject changes to the backlog if they believe the changes do not align with these priorities.

The sprint review/demo is the meeting where the team shows completed work to stakeholders and gathers feedback. According to the PMI Agile Practice Guide (Section 5.3: Sprint Review) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 4: Stakeholder Engagement), stakeholders such as department heads or executives should attend sprint demos to stay informed and provide input.

Option C is correct: sprint demos foster transparency and stakeholder involvement.

Option A is typically for the Scrum team and product owner.

Option B is for team internal coordination only.

Option D is reserved for team process improvement—not stakeholder participation.

The first priority for the Scrum Master should be to ensure the project has a dedicated, cross-functional team. Scrum teams are self-organizing and cross-functional, meaning they have all the skills needed to complete the work without relying on external resources. The Scrum Master should focus on forming a team that can collaboratively work on the product development, ensuring they are committed to the project and understand their roles and responsibilities within the Scrum framework. This is essential for the team to be effective and aligned with the Scrum principles, ensuring that they can deliver value in iterative cycles.

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 — 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 — Two-way communication.

Agile thrives on collaboration and transparency. In sprint planning, the product owner presents the business needs (via user stories), and the team responds with estimates and commitments. This mutual communication fosters alignment, shared understanding, and trust, which is characteristic of two-way communication.

PMI Agile Practice Guide:

“Agile projects rely on high levels of communication and collaboration, especially between the product owner and development team.”

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

Mike Griffiths:

“Two-way communication allows feedback and clarification. Sprint planning is a prime example where the PO and team interact to shape and commit to sprint goals.”

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

Incorrect options:

A refers to managing emotions, not communication style.

C is unrelated to agile practice.

D (reciprocal communication) is a less common term and not directly aligned with the scenario.

Answer: B

—

A product roadmap is a high-level visual representation of a product ' s development strategy, highlighting upcoming product releases and the features or goals that will be included in each release. By displaying the roadmap, the agile project manager is ensuring that all stakeholders are aligned on what the product will deliver and when, helping to manage expectations and communicate progress. This is essential for ensuring that everyone involved in the project has a shared understanding of the product ' s direction and key milestones.

The correct answer is D – Encourage the team member to use experimentation/spikes for continuous improvement and help the team understand why it is important. Agile encourages learning and experimentation through techniques like spikes (time-boxed research or exploration activities).

From the PMI Agile Practice Guide:

“Agile encourages teams to experiment and learn continuously. Time-boxed spikes can be used to investigate alternative designs, reduce uncertainty, and support informed decisions.”

(PMI Agile Practice Guide, Section 5.3 – Spikes and Uncertainty Reduction)

Mike Griffiths supports this:

“Spikes are short, time-limited investigations into a design or technical approach. They are a vital part of agile development for reducing risk, exploring alternatives, and enabling innovation.”

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

Incorrect options:

A and C discourage innovation and agility.

B defers action rather than enabling real-time learning.

Answer: D

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

The correct answer is C – Facilitate a retrospective to identify areas of improvement.

In Agile, mistakes are viewed as learning opportunities. The Scrum Master should create a safe environment where the team can reflect, discuss issues openly, and identify ways to prevent similar mistakes in the future.

From the PMI Agile Practice Guide:

“Retrospectives provide a regular forum for teams to inspect and adapt. Teams discuss what went well, what didn’t, and how to improve. This supports continuous learning and performance enhancement.”

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

Mike Griffiths states:

“Mistakes are inevitable; agile teams embrace them to improve. Retrospectives are essential for structured reflection and action planning.”

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

Why other options are less appropriate:

A may reinforce outdated or flawed processes.

B may help in quality control but does not address the mistake constructively.

D promotes fear and competition, which undermines team trust and collaboration.

Answer: C