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

To ensure a smooth transition to SAFe, the agile team lead should have an open discussion with the team about what will change and the reasons behind these changes. Establishing a clear understanding of the transition process and addressing any concerns proactively helps alleviate fears and encourages buy-in. It ' s also important to discuss the timeline for the transition and how the team will adapt. By providing clarity and a process for addressing concerns, the team will feel more comfortable and confident in adopting the new methodology.

This approach reinforces the core values of agile, particularly the idea that a self-managed team should be collaborative and support one another. The agile lead should focus on creating a safe environment where team members feel comfortable sharing challenges and asking for help. This will not only help the junior team member but also improve the overall team dynamics and performance by fostering a culture of openness and mutual support.

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

The correct answer is C – Encourage the team to more frequently interact with all stakeholders. When an agile team is struggling to meet commitments, one key cause is often a lack of communication or feedback from key stakeholders. Increasing interaction helps align the team ' s priorities, clarify requirements, and improve ownership and accountability.

From the PMI Agile Practice Guide:

“Teams that engage in regular, open communication with stakeholders are better able to align with the evolving needs of the business and take ownership of their commitments. Agile coaches support this behavior by facilitating frequent interactions and improving team dynamics.”

(PMI Agile Practice Guide, Section 4.2 – Stakeholder Engagement and 6.2 – Coaching the Agile Team)

Mike Griffiths’ PMI-ACP Exam Prep Book reinforces this:

“Encouraging frequent stakeholder interaction fosters a sense of ownership in the team. Agile coaches guide teams to seek clarity through communication rather than rely on assumptions.”

(Mike Griffiths, Chapter 4 – Team Performance and Coaching)

Why the other options are incorrect:

A – Involving the sponsor in team-level performance issues may undermine team self-organization.

B – Providing a list of deliverables doesn’t address the root cause (lack of communication or clarity).

D – Upfront product design goes against agile principles and does not improve team ownership or delivery capability.

Answer: C

The correct answer is D — Work with the team to analyze the market opportunity and create a tailored agile approach if needed.

Agile promotes context-based tailoring. Just because an approach works well in one project doesn’t guarantee it will fit another. The agile leader should collaborate with the team to analyze current needs and adapt or design the most suitable process accordingly.

PMI Agile Practice Guide:

“There is no one-size-fits-all approach. Agile methods should be tailored to suit the project context and objectives.”

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

Mike Griffiths:

“Teams must evaluate project needs and customize their process accordingly. Blind reuse of past methods often fails to address unique challenges.”

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

Incorrect options:

A involves stakeholders, but D emphasizes team and tailoring for delivery.

B ignores the unique needs of the new project.

C undermines agility and team ownership.

Answer: D

—

Delivering value in agile depends on frequent prioritization and real-time feedback. According to the PMI Agile Practice Guide (Section 5.1 Product Backlog and Prioritization), product owners and agile teams must continuously reprioritize the backlog based on changing stakeholder needs, market shifts, and feedback. Failure to do so can result in building the wrong product—even if it ' s " done. "

Mike Griffiths (PMI-ACP Exam Prep Book, Chapter 6: Value-Driven Delivery) stresses that value delivery is iterative and depends on current priorities, not static backlogs. It is vital that teams confirm that they ' re working on the highest-value items before committing to a sprint.

Option A is correct: proper backlog refinement and reprioritization ensures alignment with evolving stakeholder needs.

Option B is an anti-pattern; agile welcomes change even late in development.

Option C and D are irrelevant or do not address the core issue of prioritization.

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

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

Option A skips team consensus and formal prioritization.

Option B contradicts self-organizing team principles.

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

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