In an Adaptive (Agile) project environment, change is expected and welcomed. To manage this, the project manager (often acting as a servant leader) must foster an environment of transparency and rapid feedback.

Transparency and Checkpoints (Choice B): This is the core of agile project management. By giving access to information (transparency), the team understands the why behind changes in the product backlog. Frequent team checkpoints (such as Daily Stand-ups, Sprint Planning, and Retrospectives) provide a structured way for the team to process changes, ask questions, and adjust their work in real-time. This reduces the fear of the unknown and makes change a standard part of the workflow.

Command and Control (Choice A): In adaptive environments, " control " without delegation is counterproductive. High-performing agile teams are self-organizing. If a project manager centralizes all decisions, the team becomes a bottleneck and is less resilient to change.

Rotating the PM Role (Choice C): While agile encourages shared responsibility and cross-functionality, simply rotating the " Project Manager " title for stakeholder reviews is not a standard practice for managing a team ' s comfort with change. Consistency in leadership roles often provides the stability a team needs when the project scope is shifting.

Change Control Board (Choice D): Formal Change Control Boards (CCBs) are characteristic of Predictive (Waterfall) environments. In adaptive projects, the Product Owner typically manages the backlog changes, and the team is notified immediately through ceremonies like Backlog Refinement. Waiting for a CCB would slow down the agility of the team and create a barrier between the team and the evolving requirements.

By prioritizing B, the project manager aligns with the Agile Manifesto principles of " Responding to change over following a plan " and " Building projects around motivated individuals. " Transparency ensures that the team is not just reacting to change, but actively participating in it.