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

The correct answer is B – Have team members work in pairs to learn from each other and develop new skills. Pairing encourages collaboration, knowledge sharing, and skill development, which helps reduce dependency on specific individuals and enhances engagement through variety.

From the PMI Agile Practice Guide:

“Pair programming and other collaborative work methods help reduce repetition, promote learning, and improve motivation. These techniques allow for shared ownership and skill diversity.”

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

Mike Griffiths adds:

“Cross-training and pairing reduce boredom, eliminate knowledge silos, and increase team flexibility. They are effective responses to reduced motivation from repetitive work.”

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

Incorrect options:

A may temporarily help morale but doesn’t address the root cause.

C is more suitable for analyzing inefficiencies, not directly resolving monotony.

D adds cost and doesn’t solve the underlying engagement problem.

Answer: B

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

The correct answer is D — Periodically, at both the release and project level.

Agile planning is iterative and layered. When new requirements or constraints emerge, plans should be updated at the appropriate levels—sprint, release, and potentially the overall project level. Periodic adjustments ensure continued alignment with business needs and system dependencies.

PMI Agile Practice Guide:

“Agile planning is done at multiple levels: product vision, roadmap, release, iteration, and daily. These plans are continually updated based on new learning and stakeholder feedback.”

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

Mike Griffiths:

“Effective planning includes periodic updates at all planning horizons. Adjusting at both the project and release levels ensures strategic alignment and tactical feasibility.”

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

Incorrect options:

A misses the iterative nature of Agile planning.

B and C are too narrow in scope.

Answer: D

—

The correct answer is D – Understand the impediments and facilitate issue resolution to enable the team to succeed.

The Agile Project Manager (or Scrum Master) acts as a servant leader by removing impediments and coaching the team toward improvement. Instead of dictating action or adjusting timeboxes, the right approach is to facilitate problem-solving and help the team meet its sprint goal.

From the PMI Agile Practice Guide:

“The Scrum Master works to remove impediments and support the team’s progress. They do not give commands but instead facilitate improvement.”

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

Mike Griffiths affirms:

“Agile leaders remove roadblocks and create an environment where the team can succeed. They support rather than direct.”

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

Other options are inappropriate:

A is command-and-control, not servant leadership.

B violates timebox principles of Scrum.

C misplaces responsibility for testing onto customers.

Answer: D

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

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

From the PMI Agile Practice Guide:

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

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

Mike Griffiths notes:

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

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

Incorrect options:

A is reactive and escalatory.

C presumes the standards are flawed without analysis.

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

Answer: B

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

In agile, when uncertainty exists around a technical or functional aspect of work, the team can use a spike—a time-boxed research or prototyping activity—to explore the unknown. According to the PMI Agile Practice Guide (Section 5.2 User Stories and Spikes), spikes are ideal when the team lacks information or confidence about a proposed solution and needs to experiment before committing.

Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning) explains that spikes are used to investigate technical approaches, prove concepts, or explore new technologies, and they provide the team with the insight and confidence needed to proceed with less risk.

Option A is correct because a spike would allow the team to explore the new framework in a controlled way.

Other options such as Ishikawa diagrams (B), pre-mortems (C), and trend analysis (D) are useful in other contexts, but not suitable for increasing confidence in new technical implementation approaches.

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

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

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

“Customer collaboration over contract negotiation.”

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

And from the PMI Agile Practice Guide:

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

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

Mike Griffiths also emphasizes:

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

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

Other options don’t directly address the root cause:

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

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

Answer: A

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

A value stream map is a tool used to visualize the flow of materials and information through a process, identifying areas of waste and inefficiency. In this case, the business analyst ' s key observations will include wait times (delays between steps) and cycle times (time taken to complete each step in the process). By analyzing these, the business analyst can identify opportunities to streamline the process, reduce delays, and improve overall efficiency in delivering healthcare services.

The correct answer is B – Align with stakeholder expectations and releasable product increments.

In Agile, sprint or iteration reviews provide an opportunity for the team to present completed work and validate it against stakeholder expectations. Demonstrations should showcase working, potentially shippable increments that align with business goals and value delivery.

From the PMI Agile Practice Guide:

“The purpose of iteration reviews is to showcase a working product increment. The review should focus on what was completed and how it aligns with stakeholder expectations and business objectives.”

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

PMBOK® Guide further reinforces this point:

“The team should deliver functional product increments that are valuable to stakeholders. These should be validated for alignment with scope and business value.”

(PMBOK® Guide, 6th Edition, Section 5.5 – Validate Scope)

Mike Griffiths notes:

“Product demonstrations should confirm stakeholder needs are being met. The team’s focus should be on verifying value delivery, product completeness, and stakeholder alignment.”

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

Why other options fall short:

A is valuable context, but doesn’t directly ensure demonstration success.

C reflects team improvement but is not the purpose of a product demo.

D speaks to collaboration, not validation of stakeholder alignment.

Answer: B

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 — Organize training and development workshops to help all stakeholders form a shared understanding of agile practices.

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

PMI Agile Practice Guide:

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

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

Mike Griffiths:

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

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

Incorrect options:

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

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

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

Answer: B

—

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

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

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

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

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

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

The Minimum Viable Product (MVP) is the smallest set of features needed to satisfy early adopters and deliver value quickly while enabling further development based on feedback. From the conversation:

Android phone integration: The customer specifically asks if they can connect their phone to the calendar app, so integrating with Android is a key MVP feature.

Scheduler to add events: The customer requests the ability to schedule and manage upcoming releases, including quarterly metrics deadlines and other key dates. This is fundamental functionality for the calendar app.

Product increment release dates: The customer wants the calendar to show release dates, so having the ability to display product increment release dates is essential.

The correct answer is A – Create a user story for this new improvement and put it in the product backlog for prioritization and validation by the customer. Agile is iterative and feedback-driven. New requirements or enhancements identified during reviews are treated like any other backlog item: they are created as user stories, evaluated, and prioritized collaboratively.

From the PMI Agile Practice Guide:

“Feedback during review meetings may lead to new stories. These are added to the product backlog and prioritized based on value, risk, and customer need.”

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

Mike Griffiths explains:

“Agile welcomes change—even late in development. New feedback should be captured as stories, then reviewed and prioritized by the Product Owner in alignment with business goals.”

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

Incorrect options:

B assumes premature prioritization.

C implies scope creep, which contradicts agile’s flexibility.

D contradicts team empowerment and planning integrity.

Answer: A

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

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

The correct answer is C — Generate insights at the next retrospective and adjust processes as decided by the team.

The retrospective is the proper agile ceremony for identifying issues related to team performance, communication, and process inefficiencies. It ' s an opportunity for the team to collaboratively review their work, generate insights, and agree on improvements. Inconsistent defect data is a team-level issue best addressed through inspection and adaptation during the retrospective.

PMI Agile Practice Guide states:

“Retrospectives allow the team to inspect how they work together and continuously improve their team norms, working agreements, and definitions of done.”

(PMI Agile Practice Guide, Section 5.8 — Retrospectives)

Mike Griffiths supports this:

“Retrospectives provide teams the opportunity to identify recurring problems, such as inconsistent defect documentation, and agree upon actions for improvement. Teams should self-organize and own their process improvements.”

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

Incorrect options:

A is disruptive — iterations are not stopped unless critical.

B misuses the planning meeting, which is for backlog commitment, not process review.

D treats a process improvement as a backlog item, which may dilute accountability.

Answer: C

—

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

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

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

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.

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

The 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

—

When an agile team ' s velocity is slowing down, it is essential to regularly evaluate and adjust how the team is performing. By using feedback loops in every sprint, the team lead can continuously assess the team ' s progress, identify bottlenecks, and address issues early on. These feedback loops, typically discussed in sprint retrospectives, provide an opportunity for the team to identify the root causes of challenges, such as miscommunications, and make improvements to ensure better performance in future iterations. This approach promotes ongoing reflection and adaptation, which are core principles of Agile.

In Agile and user-centered design, creating user personas is a valuable way to represent the different types of users who will interact with the application. By identifying these personas, the project manager can ensure that the development team better understands the varying needs, behaviors, and goals of different user groups. This approach helps create a more effective and tailored user experience for the application. It also provides clear guidance to the team on how to prioritize features and functionality for diverse user groups.

The correct answer is D – Work with the team to ensure that acceptance criteria is being properly defined and understood.

Incomplete work that fails to meet stakeholder expectations often results from unclear or misunderstood acceptance criteria. Clarifying the definition of “done” and ensuring alignment between the Product Owner and development team can drastically reduce rework and defects.

From the PMI Agile Practice Guide:

“Clear and testable acceptance criteria help ensure shared understanding. Quality issues frequently stem from misaligned expectations or vague requirements.”

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

Mike Griffiths writes:

“Teams must understand what success looks like for each story. Poorly defined or misunderstood acceptance criteria are a major cause of defects and missed expectations.”

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

Other options explained:

A (spike) is used for research or uncertainty—not fixing misunderstood requirements.

B (burndown chart) helps track progress, not resolve defects.

C may help indirectly but doesn ' t address the core problem of unclear requirements.

Answer: D

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

Task boards (or visual boards) are a great way to facilitate communication within the team. By using a task board, team members can easily see what work has been completed, what is currently being worked on, and what still needs attention. This visual aid helps keep everyone on the same page, ensures that information is shared transparently, and can help identify potential bottlenecks or communication gaps. It improves collaboration and visibility, making it easier for the team to coordinate and align on tasks, leading to fewer delays in the development process.

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

To improve collaboration, it ' s essential that the team members understand the importance of the project vision statement and feel empowered to contribute. Setting clear expectations ensures that all participants know the purpose of the meeting and their role in contributing. By encouraging everyone to share their ideas and perspectives, the team can reach a consensus or at least acknowledge differing views in a constructive way. This fosters a collaborative environment where team members feel their input is valued.

The correct answer is C – Risk-value quadrant. This technique is a prioritization matrix that helps teams identify and rank backlog items by evaluating their business value against their risk. This ensures early delivery of high-value and high-risk features, supporting fail-fast learning and reducing uncertainty.

From the PMI Agile Practice Guide:

“The risk-value matrix helps prioritize features by plotting them based on business value and implementation risk. High-value/high-risk items are often addressed first.”

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

Mike Griffiths emphasizes:

“The risk-value quadrant is a powerful tool to guide agile prioritization. It ensures the most valuable and uncertain items are tackled early to deliver insights quickly.”

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

Incorrect options:

A is used for estimation, not prioritization.

B is a scheduling concept, not a prioritization method.

D refers to story quality (Independent, Negotiable, Valuable, Estimable, Small, Testable), not prioritization.

Answer: C

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

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.

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

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

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

From the PMI Agile Practice Guide:

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

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

Mike Griffiths explains:

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

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

Other options:

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

C is irrelevant to Agile effectiveness.

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

Answer: B

═════════

Agile teams are self-organizing and responsible for determining how to deliver their commitments. According to the PMI Agile Practice Guide (Section 4.3.3: Self-Organizing Teams) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning), the best course of action is to support the team in evaluating trade-offs—especially when innovation like a spike can enhance efficiency. The project leader should enable, not dictate decisions.

Option A is correct: it respects team autonomy while supporting innovation.

Option B discourages innovation and learning.

Option C may delay needed improvement and demotivates team initiative.

Option D removes the team ' s ability to decide and self-manage priorities.

The correct answer is D — Discuss the issue with the team at the next project retrospective.

Fatigue and declining productivity are ideal topics for the sprint retrospective. Retrospectives provide a dedicated time for the team to reflect on what ' s working and what ' s not, and they promote continuous improvement in a psychologically safe environment.

PMI Agile Practice Guide:

“Retrospectives allow teams to reflect on how they work and to continuously improve their practices, processes, and team dynamics.”

(PMI Agile Practice Guide, Section 5.8 – Retrospectives)

Mike Griffiths:

“Retrospectives are opportunities to openly discuss issues such as burnout or fatigue and decide as a team what improvements to implement.”

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

Incorrect options:

A (daily standup) is focused on immediate blockers, not deep reflection.

B might help but creates unnecessary ceremony; the retrospective is the correct venue.

C escalates the issue outside the team prematurely.

Answer: D

—

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

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

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

From the PMI Agile Practice Guide:

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

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

Mike Griffiths confirms:

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

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

Other options explained:

B creates unnecessary manual effort.

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

D encourages siloed behavior and contradicts collaboration.

Answer: A

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

The correct answer is C – Ask the team to discontinue developing the component. Agile empowers the product owner to make real-time scope decisions based on changing customer needs. If a feature no longer delivers value, continuing it violates agile ' s principle of maximizing value and minimizing waste—even if partially complete.

From the PMI Agile Practice Guide:

“Agile welcomes changing requirements—even late in development. The product owner’s role is to ensure that the team focuses on work that delivers the most business value.”

(PMI Agile Practice Guide, Section 3.4 – Value Prioritization and Scope Management)

Mike Griffiths affirms:

“If a component is deemed unnecessary, even mid-development, the product owner has the authority to reprioritize the backlog and halt the work. Agile values responding to change over following a fixed plan.”

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

Incorrect options:

A suggests unnecessary bureaucracy; agile favors decentralized, empowered decision-making.

B ignores the updated feedback and would create waste.

D is redundant since the sponsor already communicated disinterest; the product owner can act.

Answer: C

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

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.

The correct answer is D — Ask the agile practitioner to facilitate a story-writing workshop.

When stakeholders have conflicting inputs, a collaborative approach such as a story-writing workshop enables the team to converge on a shared understanding. The agile practitioner (Scrum Master or Agile Coach) plays a key role in facilitating these sessions to ensure productive dialogue and alignment.

PMI Agile Practice Guide explains:

“Facilitated workshops, including story-writing workshops, help surface differences in stakeholder needs and create alignment through structured collaboration. Agile practitioners often lead these sessions to ensure neutrality and focus.”

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

Mike Griffiths’ book adds:

“Agile practitioners support product owners in building and refining the backlog, especially when multiple viewpoints or conflicts exist. Facilitated workshops ensure transparency and a collaborative environment.”

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

Incorrect options:

A is incorrect because the practitioner’s role is to facilitate, not write the stories.

B is a good idea, but the product owner should not delegate facilitation to the team.

C may assist with clarification but won’t help resolve conflict or prioritize across stakeholders.

Answer: D

—

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

From the PMI Agile Practice Guide:

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

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

Mike Griffiths adds:

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

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

Incorrect options:

A assumes trimming scope is sufficient without stakeholder input.

B contradicts team stability and morale principles.

C helps identify inefficiencies but doesn’t replace transparency.

Answer: D

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

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

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

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

Option C relates to value prioritization, not operational efficiency.

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

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

From the PMI Agile Practice Guide:

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

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

Mike Griffiths further explains:

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

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

Incorrect options:

A reflects a waterfall mindset.

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

C is informative but not collaborative or sufficient for planning.

Answer: D

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

In this situation, the most practical solution is to reduce the scope of the release to meet the deadline. Since one team member will be absent, causing a reduction in velocity, the team may not be able to complete all planned work in the time remaining. By reducing the scope, the team can focus on delivering the most critical features for the industry fair and ensure that the release is still valuable and on time. This aligns with Agile principles of prioritizing the most valuable work and delivering iteratively based on available capacity.

Value stream mapping is a powerful tool in Agile and Lean methodologies used to visualize and analyze the flow of materials and information across the entire process. By mapping the current state, the team can identify bottlenecks, delays, and inefficiencies, especially when multiple teams are involved in sequential activities. Once these gaps and constraints are identified, the team can work on improving the process, such as by finding ways to increase the number of systems migrated per day from two to three, thus improving overall efficiency.

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

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

The correct answer is C – Schedule a story grooming session with the product owner before sprint planning. Story grooming (backlog refinement) ensures that stories are ready, appropriately detailed, and understood before planning.

From the PMI Agile Practice Guide:

“Backlog refinement sessions are a key practice where the team, facilitated by the Scrum Master, ensures that backlog items are well-defined and sized appropriately for future planning. These sessions reduce ambiguity and promote shared understanding.”

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

Mike Griffiths adds:

“Backlog refinement allows stories to be clarified, split, and estimated ahead of planning. Agile practitioners ensure backlog items meet the Definition of Ready (DoR) before sprint planning.”

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

Incorrect options:

A delays collaboration and is too passive.

B lacks product owner involvement.

D is a sizing technique, not a requirement clarification method.

Answer: C

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

The project lead should focus on creating a safe environment where all team members feel comfortable expressing their opinions without fear of judgment or repercussions. This can be achieved by encouraging open communication, showing appreciation for diverse perspectives, and actively ensuring that everyone ' s voice is heard. A safe environment fosters trust and collaboration, which is essential for the team ' s success. While other options may help in certain contexts, building a culture of safety and trust is the most effective long-term strategy to encourage team members to speak up.

Predictable flow in agile is achieved by reducing variability in story size and complexity. According to the PMI Agile Practice Guide (Section 5.7: Flow-based Agile and Kanban), working with small, similarly sized user stories increases throughput predictability and improves cycle time.

Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 6: Value-Driven Delivery) supports breaking large stories into smaller, testable chunks as a way to stabilize delivery and forecasting.

Option A is correct: small user stories reduce variability and support predictable flow.

Option B supports testability but doesn’t directly improve flow.

Option C and D are too broad or conceptual to specifically improve predictability.

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

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.

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.

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.

In this scenario, the team faced delays due to the absence of a single tester. To prevent similar issues in the future, the team should work on becoming more cross-functional, where team members are skilled in multiple areas (e.g., testing multiple data sources). Encouraging team members to become general specialists reduces bottlenecks and dependency on a single individual, ensuring that the team can continue to make progress even if someone is unavailable. This fosters greater flexibility and resilience within the team, improving overall efficiency and minimizing disruptions in future implementations.

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

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

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.

Agile promotes cross-functional teams and reducing bottlenecks through knowledge sharing and skill development. The PMI Agile Practice Guide (Section 4.3.3: Cross-functional Teams) recommends that team members develop T-shaped skills to handle more types of work. Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 3: Team Performance) advocates for skill broadening to improve team throughput and resilience.

Option A is correct: cross-training removes dependencies and improves flow.

Option B delays action and prolongs the issue.

Option C reduces delivery capacity rather than addressing the root cause.

Option D arbitrarily limits scope and doesn’t resolve the underlying skill gap.

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

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

From the PMI Agile Practice Guide:

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

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

Mike Griffiths writes:

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

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

Why the other options are incorrect:

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

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

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

Answer: B

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

In an adaptive environment, the project manager’s role is focused on facilitating collaboration and communication among stakeholders, teams, and sponsors to ensure that decisions are made quickly and effectively as circumstances change. This aligns with the agile principle of collaboration over contract negotiation and emphasizes adaptability and the ability to respond to changing needs. While project managers may still contribute to planning and other activities, fostering a collaborative and flexible decision-making process is key in an adaptive environment.

The correct answer is C — All stakeholders are responsible for identifying risks during standups, retrospectives, and other team meetings.

Agile promotes collective ownership. Risk identification and mitigation are shared responsibilities involving the entire team, including the product owner, developers, and other stakeholders. Agile meetings (e.g., stand-ups, retrospectives) are excellent forums for surfacing risks early.

PMI Agile Practice Guide:

“In agile projects, everyone is responsible for identifying and managing risk. Teams inspect frequently, enabling early detection and resolution of issues.”

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

Mike Griffiths:

“Risk management is embedded in agile events. Teams don’t defer risk analysis to a specialist—they collaborate continuously to identify, discuss, and respond to risks.”

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

Incorrect options:

A ignores active risk management needs.

B assumes individual rather than shared responsibility.

D misrepresents the PO’s role—risks may appear in the backlog, but management is team-based.

Answer: C

—

The correct answer is B – Review the project vision statement.

A shared vision ensures that the team and stakeholders are aligned on the purpose, value, and expected outcomes of the product. In Agile, the vision statement guides product development and ensures that decisions made during iterations are grounded in stakeholder needs.

From the PMI Agile Practice Guide:

“A clear product vision guides the team and stakeholders in understanding the product’s purpose and desired outcomes. The product vision promotes alignment and provides a foundation for ongoing decisions.”

(PMI Agile Practice Guide, Section 5.1 – Vision)

Mike Griffiths also emphasizes:

“A product vision helps ensure everyone is heading in the same direction. It’s critical to regularly revisit this vision to maintain alignment with stakeholders and the evolving product strategy.”

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

Why the other options are incorrect:

A (kick-off meetings) may help in initial orientation but doesn’t sustain alignment over time.

C contradicts Agile’s preference for lightweight documentation and ongoing collaboration.

D is general process alignment—not specific to stakeholder engagement.

Answer: B

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

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.

=========

Step 1: Identify Remaining MVP Story Points

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

Accessibility – color blind → 4 story points

Increase security → 21 story points

Add AI chatbot → 5 story points

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

Step 2: Consider Velocity and Sprint Progress

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

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

Step 3: Calculate Completion Sprint

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

The correct answer is B — Balance risk reduction and value-adding activities in the next iteration.

Agile recommends actively managing risks as part of iteration planning. While delivering customer value remains a top priority, severe risks should be mitigated as early as possible. The team should consider allocating capacity in the next sprint to reduce risk while still maintaining delivery focus.

PMI Agile Practice Guide states:

“Agile teams incorporate risk mitigation work into iteration planning. Teams should prioritize high-impact risks early and balance risk management with delivering customer value.”

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

Mike Griffiths supports this:

“Agile does not separate risk management into a different process—it is embedded within backlog prioritization. Addressing risk early can prevent downstream impacts, and teams must weigh risk vs. value regularly.”

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

Incorrect options:

A disrupts current iteration goals and contradicts agile time-boxing.

C ignores the severity of the risk.

D escalates unnecessarily—agile promotes team-level decision-making first.

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 A — Suggest the product owner start by focusing on the next 2 sprints instead of 10.

Agile embraces progressive elaboration — planning is done in detail only for the near term, while long-term plans remain high level and flexible. By encouraging short-term focus, the Scrum Master helps the product owner shift from a predictive mindset to an adaptive one.

PMI Agile Practice Guide:

“Agile projects plan at multiple levels (release, iteration, and daily), focusing on near-term commitments while allowing flexibility for change. Planning multiple sprints in detail violates the principle of adaptability.”

(PMI Agile Practice Guide, Section 5.3 — Progressive Elaboration)

Mike Griffiths adds:

“Detailed long-term estimates reduce agility. The product owner should learn to prioritize work based on value, and accept that estimates beyond the next sprint or two are rough forecasts.”

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

Other options:

B undermines agile principles by reverting to waterfall planning.

C misuses the retrospective, which is team-focused.

D may alienate the product owner rather than encourage a mindset shift.

Answer: A

—

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

—

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 – Create a collaborative team environment so that the team can explore a solution together. Agile emphasizes self-organization, teamwork, and collective ownership of problem-solving. The Scrum Master facilitates, not dictates, and enables the team to resolve impediments through collaboration.

From the PMI Agile Practice Guide:

“The Scrum Master helps the team identify, address, and remove impediments. This is often done by fostering an environment of open communication and team problem-solving.”

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

Mike Griffiths elaborates:

“Rather than escalate or assign responsibility, the Scrum Master enables the team to work together to solve problems. This builds trust, increases team capability, and supports agile values.”

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

Incorrect options:

A and B promote a command-and-control approach, which violates agile values.

C defers the solution to a future sprint, rather than solving it now.

Answer: D

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

When the organization transitions from longer to shorter iterations, it’s crucial to provide the team with the right support and ensure they have the resources to adapt. Requesting support from the enterprise coach and HR can help the team manage this change effectively, providing them with necessary training or assistance. Additionally, assessing the impact of the change and brainstorming solutions with the team helps address concerns about testing and ceremonies, while allowing the team to provide input on how they can adapt to the new iteration length without compromising quality or efficiency.

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

From the PMI Agile Practice Guide:

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

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

Mike Griffiths also writes:

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

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

Incorrect options:

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

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

C is for understanding customer satisfaction, not operational delays.

Answer: D

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

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.

In Kanban, one of the most effective ways to reduce variability in cycle time is by ensuring a consistent size of work items. According to the PMI Agile Practice Guide (Section 5.7 Flow-based Agile - Kanban), maintaining uniformity in work item size helps stabilize the system and supports reliable forecasts. Large or complex stories increase variability and unpredictability.

Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 6: Value-Driven Delivery) recommends splitting large user stories and maintaining size thresholds for items on the board to ensure flow efficiency.

Option C aligns best with this practice: establishing a policy for breaking down large stories and adjusting WIP accordingly will help standardize flow, minimize cycle time variation, and improve predictability.

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

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

PMI Agile Practice Guide:

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

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

Mike Griffiths:

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

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

—

The correct answer is D — Iteration Burndown Chart.

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

PMI Agile Practice Guide states:

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

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

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

Mike Griffiths’ PMI-ACP Exam Prep Book elaborates:

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

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

Answer: D

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

The correct answer is C – The team should discuss their definition of done (DoD) and make changes to ensure there is common understanding of the acceptance criteria.

A shared understanding of what “done” means ensures consistent quality across team members. When this understanding is missing, defects and inconsistencies arise. The Definition of Done (DoD) should be reviewed and updated collaboratively to set a clear standard for completeness and quality.

From the PMI Agile Practice Guide:

“The Definition of Done provides a shared understanding of when work is complete. This includes quality criteria, testing, and documentation. It should be revisited regularly to maintain alignment.”

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

Mike Griffiths emphasizes:

“Quality issues often result from unclear or inconsistent DoD. Revisiting and refining it ensures consistent expectations across the team.”

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

Why the other options are incorrect:

A (TDD) may help, but won’t solve the fundamental alignment issue.

B accepts a problem without resolving it.

D imposes a process without team collaboration, which is not agile.

Answer: C

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

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

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

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

“Working software over comprehensive documentation.”

From the PMI Agile Practice Guide:

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

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

Mike Griffiths adds:

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

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

Why the other options fall short:

A prolongs the wasteful practice unnecessarily.

B lacks the analysis needed before eliminating documentation.

C enforces process over value, which contradicts Agile principles.

Answer: D

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

The best answer is A because an agile practitioner should first facilitate collaboration, uncover the root causes of disagreement, and help the teams align around a shared outcome. The issue is not simply the absence of targets or KPIs; it is a cross-functional conflict involving cost, compliance, product choices, and sustainability commitments. PMI-ACP topics emphasize collaboration, stakeholder engagement, shared vision, systems thinking, and conflict facilitation.

Option B is too directive and may increase resistance because it forces compliance without resolving the underlying concerns. Option C centralizes the decision with executives, which reduces team collaboration and does not reflect agile servant leadership. Option D may be useful later, but KPIs alone will not resolve the tension or rebuild alignment. The agile practitioner should promote a collaborative approach to solving conflict and ensure common understanding of purpose and vision.

=========

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

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 C – Seek regular input from project stakeholders, and reflect this input in the backlog’s priorities. Agile is a stakeholder-driven process, and backlog refinement should be informed by continuous feedback. The product owner maximizes value by regularly reviewing stakeholder needs and reprioritizing accordingly.

From the PMI Agile Practice Guide:

“The product owner is responsible for maintaining the backlog and ensuring it reflects stakeholder priorities. Ongoing engagement with stakeholders ensures the product delivers maximum value.”

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

Mike Griffiths adds:

“Agile product owners engage stakeholders continuously to update priorities and deliver value incrementally.”

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

Incorrect options:

A is good practice but doesn’t address the stakeholder engagement challenge.

B confuses story size with business value.

D lacks the agility required in a fast-moving project.

Answer: C

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

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

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

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

Option C implies waterfall-style handoffs.

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

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.

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

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

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

The 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 – 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 daily stand-up (daily Scrum) is a time-boxed coordination meeting where each team member answers the three key questions: What did I do yesterday? What will I do today? Are there any blockers? According to the PMI Agile Practice Guide (Section 5.3: Daily Stand-ups) and Scrum Guide, in-depth discussions should be taken offline to avoid disrupting the stand-up’s purpose.

Option A is correct: deferring detailed conversations maintains stand-up focus.

Option B may derail the time-boxed meeting.

Option C overreacts and undermines team self-management.

Option D might be appropriate later but not during the stand-up.

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

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

From the PMI Agile Practice Guide:

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

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

Mike Griffiths further adds:

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

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

Why the other options are not ideal:

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

C suggests overwork, which contradicts sustainable pace.

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

Answer: A

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

The correct answer is A — Make sure the product owner is fully embedded into the project team so that they are readily available to make quick decisions.

One of the major benefits of agile is that decision-making is streamlined by having empowered roles, such as the product owner, closely embedded with the team. This reduces delays and improves the responsiveness and accuracy of decisions, especially for prioritization and clarification.

PMI Agile Practice Guide:

“Empowering the product owner and embedding them with the team ensures faster decision-making, increased feedback loops, and reduces delays.”

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

Mike Griffiths:

“Agile teams thrive when key decision-makers, especially the product owner, are available to provide clarification and approval on the spot.”

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

Incorrect options:

B is too broad and may slow decision-making further.

C adds overhead and delays.

D misplaces decision authority; the Scrum Master is not responsible for product decisions.

Answer: A

—

In this scenario, the development team is working closely with different business units to deliver value early and often. This aligns with the agile value of delivering working software frequently, with a preference for shorter timescales. By collaborating with business units, the team is enabling early feedback and adapting to changing requirements, which is a core principle of agile methodologies like Scrum.

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

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

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

Option B addresses technical quality but not stakeholder dissatisfaction.

Option C unfairly shifts blame without addressing communication.

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

The correct answer is C — The stakeholders will learn whether or not the implementation has worked by getting immediate feedback so they can correct their assumptions for the next sprint.

Agile welcomes stakeholder involvement throughout the project lifecycle. Demos (also called sprint reviews) are critical opportunities for stakeholders to inspect the product increment and provide feedback, which helps teams pivot or adapt early and often. Immediate feedback reduces the risk of building features that do not meet business needs.

PMI Agile Practice Guide:

“Iteration reviews/demos provide stakeholders with the opportunity to see working product increments and offer feedback while there is still time to make changes.”

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

Mike Griffiths supports this by stating:

“Engaging stakeholders during sprint reviews allows assumptions to be challenged early. This feedback loop ensures value alignment and reduces the likelihood of rework.”

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

Other options:

A incorrectly distances stakeholders from essential agile feedback cycles.

B shifts focus away from value to effort-based metrics.

D is more about long-term ROI, not immediate iterative feedback.

Answer: C

—

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.

A complete and realistic backlog must include not only functional stories but also non-functional and support tasks such as infrastructure setup, analysis, and design. The PMI Agile Practice Guide (Section 5.2: Backlog Composition) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning) emphasize including all types of work in the backlog to ensure accurate effort planning.

Option D is correct: effort must include technical tasks, not just feature delivery.

Option A suggests speculation on velocity and cost increases, which is unreliable.

Option B and C (adding buffers or padding estimates) violate agile’s principle of transparency and simplicity.

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.

Agile promotes self-organizing teams, where leadership can emerge naturally. The PMI Agile Practice Guide (Section 4.3.2: Team Empowerment and Leadership) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 3: Team Performance) both emphasize supporting team members who take on informal leadership roles, as this strengthens team capability and fosters growth.

Option A is correct: nurturing emerging leaders aligns with agile values of empowerment and self-organization.

Option B may suppress initiative.

Option C escalates unnecessarily.

Option D applies hierarchical control inconsistent with agile team dynamics.

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

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

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

Option A disrupts sprint scope mid-course.

Option C is unnecessary unless the issue is blocking progress.

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

Agile values active stakeholder collaboration and transparency. The best way to address stakeholder concerns is to engage them directly in the feedback loop. The PMI Agile Practice Guide (Section 7.2: Stakeholder Engagement) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 4: Stakeholder Engagement) both recommend inviting stakeholders to iteration reviews or demos to provide updates and gather feedback.

Option C is correct: inviting the regional sales manager to the review fosters transparency and collaboration.

Option A and B dismiss valid stakeholder input, which goes against agile principles.

Option D is overly cautious and does not proactively resolve the issue.

The correct answer is A – The team will be unable to understand the iteration ' s status. Agile relies on transparency and timely updates to progress tracking tools such as task boards, burndown charts, and digital boards. Incomplete or delayed updates obscure the team ' s true progress, making it difficult to inspect and adapt.

From the PMI Agile Practice Guide:

“Visibility of progress is key to agile. Without timely updates to task boards or status indicators, teams lose the ability to inspect and adapt effectively during iterations.”

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

Mike Griffiths emphasizes:

“If user stories or tasks are not updated, burndown charts and velocity metrics become inaccurate. This compromises team transparency and decision-making.”

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

Incorrect options:

B is not directly impacted by status updates.

C might result as a side effect, but A is more fundamental.

D misrepresents the problem—it is about progress tracking, not collaboration metrics.

Answer: A

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

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

The correct answer is D – 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

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

The Definition of Done (DoD) is a shared understanding of what it means for work to be considered complete. It is typically defined by the project sponsor and project team in collaboration. The DoD outlines the criteria that must be met for user stories, features, or tasks to be considered done, ensuring alignment between stakeholders and the development team. While the product owner, Scrum master, and stakeholders may influence the criteria, the final agreement on what constitutes " done " is determined by the project team and sponsor.

The correct answer is C – Ask the Product Owner to select an item from the backlog on which to work. The Product Owner is responsible for prioritizing the product backlog. When a team finishes its sprint work early, it should collaborate with the Product Owner to identify the next highest-value item to pull into the sprint.

From the PMI Agile Practice Guide:

“The Product Owner owns the backlog and prioritization. If work is completed early, the team may pull in the next most important backlog item, subject to capacity and readiness.”

(PMI Agile Practice Guide, Section 5.3 – Iteration Execution)

Mike Griffiths reinforces:

“If there’s remaining capacity in the sprint, teams should consult the Product Owner to select the next item. The Scrum Master facilitates, but the PO owns content decisions.”

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

Incorrect options:

A skips prioritization.

B misplaces decision-making authority.

D incorrectly involves the Scrum Master in backlog decisions.

Answer: C

The correct answer is C – Share information via interactive methods such as a brainstorming session.

Agile promotes collaboration, continuous stakeholder engagement, and open communication. When a stakeholder lacks understanding, the practitioner should use interactive techniques like brainstorming, user story workshops, or product visioning sessions. These methods foster transparency, build trust, and allow stakeholders to co-create the product vision.

From the PMI Agile Practice Guide:

“Effective stakeholder engagement relies on interactive communication methods such as workshops, demos, and feedback sessions to ensure alignment and transparency.”

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

Mike Griffiths notes:

“Interactive, face-to-face collaboration provides the richest communication. Agile favors dialogue over documentation to enhance shared understanding.”

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

Why the other options are less ideal:

A (status emails) are passive and limited in effectiveness.

B may violate Scrum guidelines—daily standups are not intended for stakeholders.

D delays engagement and limits collaboration to after-the-fact review.

Answer: C

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

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

Planning Poker is a well-known estimation technique where team members use numbered cards (usually Fibonacci series) to estimate story point values based on relative size. It’s a consensus-based estimation method, as described in the PMI Agile Practice Guide (Section 5.2: Estimation Techniques) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 6: Estimating Techniques).

Option D is correct: Planning Poker is explicitly designed for estimating stories in terms of points.

Option A (Parametric) is more common in traditional (predictive) planning.

Option B (One-to-one comparison) refers to relative sizing without collaboration.

Option C (Affinity) is another agile technique but typically used for grouping stories into size buckets, not direct story point consensus estimation.

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

From the PMI Agile Practice Guide:

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

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

Mike Griffiths also explains:

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

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

Incorrect options:

A and D bypass collaborative evaluation.

C is too extreme for a small but valuable change.

Answer: B

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

The correct answer is B — Establish a live video feed between the dispersed teams to enable spontaneous engagement and collaboration on issues.

Agile encourages face-to-face communication as the most effective form of knowledge sharing. For distributed teams, this means using video conferencing, virtual whiteboards, and real-time collaboration tools to replicate co-located team dynamics. This improves clarity, reduces misinterpretation, and accelerates problem-solving.

PMI Agile Practice Guide states:

“For distributed teams, using video conferencing, shared tools, and real-time collaboration platforms helps bridge communication gaps and maintains team cohesion. Face-to-face communication, even via video, remains the most effective method.”

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

Mike Griffiths also notes:

“Distributed teams must invest in communication technologies to reduce barriers. Real-time, visual communication enables faster resolution of issues and a shared understanding of tasks.”

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

Incorrect Options:

A involves centralized control and status reporting — not Agile.

C demands co-location, which may not be feasible.

D accepts poor performance instead of addressing root causes.

Answer: B

—

The correct answer is A — Foster stronger communication by hosting cross-organizational meetings between the two teams.

Integration issues often result from mismatched expectations, lack of alignment, or asynchronous collaboration. A practical solution is to improve communication via cross-functional and cross-team meetings, which support transparency, alignment, and shared understanding.

PMI Agile Practice Guide states:

“Strong communication is essential in hybrid environments. Agile practitioners must foster collaboration between diverse teams to ensure integration points are clear and timely.”

(PMI Agile Practice Guide, Section 4.3 — Communications and Collaboration)

Mike Griffiths notes:

“When agile and non-agile teams must work together, agile leaders facilitate boundary-spanning conversations to ensure mutual understanding and coordinated delivery.”

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

Other options:

B oversimplifies the solution and may create unnecessary disruptions.

C contradicts agile ' s principle of just-enough documentation.

D is rarely practical in hybrid or large-scale environments.

Answer: A

—

Agile emphasizes sustainable pace and continuous improvement, not overworking or overcommitting. The appropriate response is to identify why the team overcommitted, learn from it, and adjust future sprint planning. This aligns with the PMI Agile Practice Guide (Section 5.4: Sprint Planning and Velocity) and Section 5.6: Retrospectives, which recommend using retrospectives to address such issues.

Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning) explains that over-committing leads to poor predictability, and inspecting root causes helps refine estimation and velocity in future sprints.

Option C is correct: it supports learning and improves future planning.

Option A promotes unsustainable practices.

Option B misunderstands velocity—it’s a measurement, not something to be increased by will.

Option D undermines team stability and agile planning based on consistent team capacity.

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.

A product roadmap is a strategic plan that outlines the vision for the product, the business objectives that need to be achieved, and the timeframes for delivering key milestones or features. It provides a high-level overview of the product ' s development, aligning the team and stakeholders on the product ' s direction and the expected delivery timeline.

Product vision defines what the product aims to achieve and the value it will deliver to customers or the business.

Business objectives outline what the product aims to accomplish in terms of business impact, like increasing revenue or improving customer satisfaction.

Timeframes indicate when key milestones or releases are planned to occur, ensuring that progress can be tracked and expectations set.

This high-level structure is essential for guiding product development and keeping stakeholders aligned, without delving into the specific details of design or project management, which are more suited for other planning documents.

Story point estimation in agile is a collaborative team activity, and consensus is critical. Techniques like Planning Poker are designed to reveal differences in understanding. According to the PMI Agile Practice Guide (Section 5.2 Estimating Techniques) and Mike Griffiths (Chapter 6: Adaptive Planning), when there ' s a discrepancy in estimates, it is essential to discuss and understand the rationale behind differing views.

Option C is correct: the team should discuss and clarify to reach a shared understanding.

Option A ignores potential misunderstandings.

Option B unnecessarily delays estimation.

Option D is incorrect—the team, not the customer, estimates the effort.

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

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

PMI Agile Practice Guide:

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

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

Mike Griffiths:

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

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

Incorrect options:

A skips backlog prioritization and team alignment.

B deflects the issue without analysis.

C ignores risk and blindly follows the existing priority.

Answer: D

—

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

From the PMI Agile Practice Guide:

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

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

Mike Griffiths explains:

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

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

Incorrect options:

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

B is passive and doesn’t reflect tangible benefits.

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

Answer: D

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

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

From the PMI Agile Practice Guide:

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

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

Mike Griffiths adds:

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

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

Incorrect options:

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

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

C delays resolving an immediate misunderstanding.

Answer: D

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

Relying solely on the developers ' experience with similar systems to define functionality can be limiting and potentially result in misaligned expectations with actual user needs. Effective Agile teams should focus on understanding and addressing the needs of end users, leveraging continuous feedback from customers, and engaging stakeholders directly. This ensures the product is built to meet real user expectations and can evolve as necessary based on user input. Instead of relying on previous experience, the team should be focused on co-creating value with customers through collaboration, feedback, and agile practices like user stories and regular testing.

In Agile, transparency and communication within the team are key. The team member should log the concern into the risk register to formally track the issue and share it with the team at the next standup. This allows the entire team to discuss and assess the situation collaboratively, ensuring that the concern is addressed and managed collectively. This approach aligns with the self-organizing nature of Agile teams, where team members are responsible for working together to find solutions.

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

Iteration reviews (or sprint reviews) are designed to demonstrate completed, potentially shippable product increments. According to the PMI Agile Practice Guide (Section 5.3 Sprint Review and Acceptance), the purpose of the iteration review is to showcase work that meets the Definition of Done (DoD) and to receive stakeholder feedback. Demonstrating incomplete or in-progress stories can mislead stakeholders about progress and reduce trust in the team.

Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 6: Value-Driven Delivery) emphasizes the importance of showing only completed work to maintain transparency and clarity in stakeholder communication.

Option A is correct: only completed stories should be demoed to ensure expectations are managed effectively.

Option B and C are not part of the typical iteration review agenda unless explicitly required.

Option D is incorrect, as it blurs the line between done and in-progress work.

A spike is a time-boxed research activity used in Agile to explore uncertainties or unknowns, such as dependencies in this case. If the product owner is unsure about the risks related to migrating to a new version of a database, they can request a spike from the team. This will allow the team to investigate the dependencies, assess potential risks, and gather the necessary information to move forward with the user story. This helps reduce uncertainty and makes it easier to make informed decisions about the next steps.

When plotting performance and dependencies on the product roadmap, the product manager should consider features, stages of development, technology and infrastructure, dependencies, and risks. These components are critical for understanding how the product will evolve over time, the technical requirements, how different parts of the system depend on each other, and the potential risks that may arise. This approach ensures that the team can manage dependencies effectively, mitigate risks, and deliver the product in line with business goals and timelines.

The correct answer is A – Lead time, throughput, and due date performance. These are key flow-based metrics used in Kanban systems to monitor performance, efficiency, and predictability of delivery.

From the PMI Agile Practice Guide:

“Kanban systems rely heavily on flow metrics to measure performance and identify bottlenecks. Key Kanban metrics include lead time, throughput, and cycle time. These metrics provide insights into how quickly work is flowing through the system.”

(PMI Agile Practice Guide, Section 5.5 – Kanban System Metrics)

Mike Griffiths further explains:

“Kanban teams track cumulative flow, lead time, and throughput to ensure steady and predictable delivery. Due date performance is used to evaluate commitments and reliability.”

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

Incorrect options:

B refers to tools and principles, not performance metrics.

C includes practices not specific to Kanban metrics.

D includes some Scrum metrics, such as burndown, but not Kanban-centric ones.

Answer: A

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

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

—

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.

To improve the team’s productivity, it is essential to keep both the product backlog and the iteration backlog up to date. The product backlog contains the overall product features and requirements, while the iteration backlog focuses on the work planned for the current iteration. Ensuring that both backlogs are updated as issues and new tasks arise will help maintain clarity and avoid confusion, enabling the team to prioritize and track progress more effectively. This will also help minimize delays and rework, as the team will have a clear, accurate view of what needs to be done and what has been accomplished.

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

From the PMI Agile Practice Guide:

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

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

Mike Griffiths explains:

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

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

Incorrect options:

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

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

D adds administrative burden without solving the underlying problem.

Answer: B

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

DevOps is a methodology that focuses on enhancing collaboration between development and operations teams to create a continuous feedback loop and speed up the delivery process. The key to enabling and sustaining a fast workflow is the establishment of a culture of collaboration, supported by the right tools and processes that allow for continuous delivery. This culture helps break down silos between teams, leading to faster and more efficient workflows that can continuously deliver value to customers.

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 – Ask the team to decide if the task should be reassigned. In agile, the Scrum Master serves as a servant leader and facilitator, not a manager. Task decisions are made by the team through collaboration and self-organization.

From the PMI Agile Practice Guide:

“Agile teams self-organize and make decisions collaboratively. The Scrum Master facilitates discussion and decision-making but does not dictate task assignments.”

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

Mike Griffiths adds:

“The Scrum Master’s role is to empower the team to find their own solutions and make informed decisions that support sprint goals. When adjustments are needed, the team should decide how to proceed.”

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

Incorrect options:

A undermines self-management and may create fear or pressure.

B implies outside control instead of team autonomy.

C ignores opportunity for improvement and team input.

Answer: D

The correct answer is C — Work with the product owner to assess the impact for reprioritization.

Agile recognizes that new priorities may emerge during a sprint. The product owner owns the backlog and prioritization. If a request threatens sprint commitments, it should be reviewed and discussed with the product owner to determine the trade-offs and make informed decisions.

PMI Agile Practice Guide:

“New requests should be assessed in collaboration with the product owner. The team should make prioritization trade-offs in a transparent manner to maintain focus on delivering value.”

(PMI Agile Practice Guide, Section 5.5 – Iteration Planning and Section 5.7 – Change Management)

Mike Griffiths:

“Product owners are responsible for backlog prioritization. When urgent issues arise, teams should discuss them with the PO rather than unilaterally shifting focus.”

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

Incorrect options:

A risks burnout and violates sustainable pace.

B avoids accountability.

D assumes the change can wait, which may not align with customer needs.

Answer: C

—

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

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

Agile roles are clearly defined to avoid overlap and confusion. According to the PMI Agile Practice Guide (Section 3.3 Agile Roles), the Product Owner is responsible for backlog prioritization and stakeholder communication, not managing team tasks. Task management is the domain of the self-organizing team and facilitated by the Scrum Master or Agile Project Manager.

Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 4: Stakeholder Engagement) reinforces that resolving role confusion through discussion helps realign expectations and improve team performance.

Option C is correct: by clarifying roles and responsibilities, the agile project manager helps prevent overreach and ensures smoother collaboration.

Option A addresses the issue too late and in the wrong forum.

Option B misrepresents agile dynamics (self-organizing teams).

Option D risks team morale and doesn’t address the root cause.

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