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.

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 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 A – Continue working on the task until it is completed. Agile teams commit to the sprint goal and are expected to deliver what they’ve planned to the best of their ability. If a task takes longer than estimated, the team inspects and adapts but generally tries to complete the committed work within the current sprint.

From the PMI Agile Practice Guide:

“Agile teams are committed to delivering the work they planned for the iteration. If estimates are off, the team inspects the impact and continues, learning from it for future planning.”

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

Mike Griffiths explains:

“If something takes longer than expected, the team should strive to complete it and use the experience to improve future estimation. Agile teams maintain sprint commitment integrity.”

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

Incorrect options:

B is punitive and unaligned with Agile values.

C contradicts Agile’s emphasis on stable teams and sustainable pace.

D breaks commitment and risks value delivery.

Answer: A

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

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

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

From the PMI Agile Practice Guide:

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

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

Mike Griffiths notes:

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

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

Incorrect options:

B contradicts continuous delivery and customer collaboration.

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

D is more about process quality than business value.

Answer: A

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

The team lead should facilitate a constructive discussion by restating both perspectives clearly, which can help ensure that all team members understand each other ' s viewpoints. Asking for more details about both approaches allows the team to analyze each method ' s pros and cons, fostering a collaborative, solution-focused discussion. Creating a chart of similarities and differences can provide a visual representation that helps the team make an informed decision, highlighting which elements from both approaches might be beneficial. This approach encourages open communication, avoids escalation, and leads to a productive exploration of options without dismissing either side.

The correct answer is D — Facilitate a team retrospective.

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

PMI Agile Practice Guide:

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

(PMI Agile Practice Guide, Section 5.8 – Retrospectives)

Mike Griffiths affirms:

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

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

Incorrect options:

A skips team-level resolution and risks undermining trust.

B manipulates metrics without solving the root problem.

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

Answer: D

—

—

The correct answer is B – Ask the team for suggestions. Agile teams are self-organizing. The Scrum Master should facilitate problem-solving by enabling the team to collaboratively decide how to handle bottlenecks. This approach respects the team ' s autonomy and encourages shared ownership.

From the PMI Agile Practice Guide:

“Scrum Masters facilitate team collaboration and self-organization. When problems arise, they engage the team in identifying and implementing solutions, rather than solving issues unilaterally.”

(PMI Agile Practice Guide, Section 4.3 – Servant Leadership and Team Empowerment)

Mike Griffiths explains:

“The Scrum Master’s role is to facilitate rather than direct. If a team member falls behind, the team should collectively explore options for support, ensuring accountability and transparency.”

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

Incorrect options:

A undermines team autonomy and assigns tasks, which the Scrum Master should not do.

C may help, but addressing issues privately doesn’t promote transparency.

D involves the Product Owner unnecessarily in team internal issues.

Answer: B

The correct answer is B – Invite the team to evaluate the suggestion and measure the effectiveness of the implementation.

In Agile, continuous improvement is a shared responsibility, and retrospectives are meant to be collaborative sessions where all team members—regardless of experience—can contribute. Ideas that could enhance performance should be discussed by the team as a whole and, when deemed valuable, tested and evaluated in upcoming sprints.

From the PMI Agile Practice Guide:

“The team owns the process and should inspect and adapt at regular intervals. During retrospectives, the team identifies potential improvements and experiments with them in subsequent iterations.”

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

Mike Griffiths states:

“Retrospectives empower teams to improve. All suggestions, regardless of origin, should be treated with respect. Teams test ideas and inspect outcomes to improve incrementally.”

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

Why other options fall short:

A delays action and discourages innovation.

C makes the product owner responsible for a team process decision, which is outside their role.

D promotes hierarchy, which undermines team collaboration and Agile values.

Answer: B

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