Agile promotes transparency and ongoing communication with all stakeholders, including legal and compliance teams. According to the PMI Agile Practice Guide (Section 7.1 Communications), one of the Scrum Master ' s responsibilities is to keep stakeholders informed of project progress and projections using tools like burnup/burndown charts, velocity trends, or product roadmaps.

Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 4: Stakeholder Engagement) emphasizes that sharing the trajectory of progress and scope delivery builds trust and provides clarity to non-technical stakeholders.

Option C is correct: sharing actual progress and trends with legal ensures alignment and transparency.

Option A misplaces the responsibility—it ' s the stakeholders who need visibility.

Option B shifts product decisions prematurely.

Option D assumes satisfaction trumps contractual obligations—this can cause legal issues.

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

As the project team scales and expands to build a business-critical platform, having a work collaboration platform is the most effective way to ensure that the team can work toward a common goal and communicate efficiently. Such a platform centralizes communication, document sharing, task tracking, and collaboration, which is essential for maintaining alignment, especially as the complexity of the project increases. Tools like Slack, Microsoft Teams, or similar platforms allow for seamless communication and collaboration, even across distributed teams, making it easier to manage and track progress, share knowledge, and keep everyone on the same page.

The correct answer is D – Advise the team of the risks and invite them to change.

Agile teams are encouraged to self-organize, but this should not result in the formation of silos, which can hinder collaboration and shared knowledge. As a servant leader, the Agile practitioner or Scrum Master should coach the team by facilitating discussions about the risks of silos (e.g., dependency bottlenecks, reduced flexibility) and encourage cross-functional collaboration.

From the PMI Agile Practice Guide:

“Agile leaders help teams reflect and improve. When silos form, the coach facilitates awareness of the impacts and invites the team to adopt knowledge sharing practices.”

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

Mike Griffiths states:

“Silos reduce adaptability and team learning. A coach should raise awareness and help the team find new behaviors that support agility and collaboration.”

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

Why other options fall short:

A escalates prematurely and undermines team self-management.

B enforces rules instead of fostering understanding.

C imposes a solution instead of empowering the team to solve its own issues.

Answer: D

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

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

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

From the PMI Agile Practice Guide:

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

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

Mike Griffiths adds:

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

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

Incorrect options:

A implies a heavy process not aligned with agile.

B prematurely limits feedback before collaborative prioritization.

D ignores the product owner’s prioritization role.

Answer: C

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

To create a high-performing team, the project manager should foster an environment where the team is aligned on a shared vision and empowered to make decisions collaboratively. Promoting consensus-driven decision-making helps team members feel involved and respected, and a shared vision ensures that everyone is working towards the same goal. This approach encourages teamwork, open communication, and collective ownership of the project’s success, which is crucial for a high-performing team.

In Agile, continuous integration and regression testing should be part of every iteration to ensure that the product is always in a potentially shippable state. These practices help catch issues early in the development process, preventing defects from accumulating and becoming harder to fix later. By integrating and testing frequently, the team ensures that new code works with existing code and that the product maintains its quality throughout the development lifecycle. This approach aligns with Agile principles of delivering working software regularly and maintaining high-quality standards throughout each iteration.

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.