A Kanban board is a visual management tool that helps teams visualize work, identify bottlenecks, and track progress in real time. It promotes transparency and fosters collaboration by allowing all team members and stakeholders to understand the current status of work items at a glance.
According to the Agile Practice Guide (Chapter 5), the Kanban board is instrumental in enhancing collaboration, especially in teams using Scrum or hybrid models. It supports continuous delivery and helps visualize workflow, making it ideal for monitoring sprint progress and optimizing teamwork.
Option A (Retrospective) improves future performance but doesn't show real-time progress.
Option B (Daily meetings) help with communication but do not visualize progress.
Option D (Gantt chart) is more aligned with predictive models and doesn't serve collaboration well in Agile.
References:
Agile Practice Guide, Chapter 5 - Agile Tools and Techniques
PMBOK Guide - Seventh Edition, "Tailoring for Agile Environments"
##############################################

When a project requires a significant resource, such as the installation of a call center, it's important for the project manager to conduct an alternative analysis. This analysis will help determine the most effective and efficient approach, whether that's hiring people directly or contracting with a company. The decision should be based on various factors such as cost, time, quality, and the specific needs of the project. References:
Project Management Professional (PMP) Reference Materials, Professional in Business Analysis Reference Materials study guide. Please note that the exact documents and page numbers are not provided as the information is based on general project management principles. For more detailed information, please refer to the specific guides and documents mentioned.

According to the PMBOK Guide, the project manager should initiate the project by developing the project charter with the key stakeholders. The project charter should define the project objectives, scope, deliverables, success criteria, and high-level risks. The project charter should also establish the project vision, value proposition, and definition of done (DoD) for the agile project. The project charter should provide clarity and alignment among the project stakeholders and enable the agile team to deliver value to the customer in short iterations. Therefore, the project manager should schedule meetings with key stakeholders to build the agile project charter and set clear expectations for the project. References: PMBOK Guide, 6th edition, pages 18,
37, 75-76, 286-287.

This question belongs to the People domain because it centers on stakeholder management, communication, and responding professionally to dissatisfaction. PMI guidance highlights that project managers need strong communication and consulting skills, especially in transformation efforts where stakeholder expectations may shift and dissatisfaction may signal a deeper need that has not been fully understood. The best first response is to listen carefully and show understanding of the stakeholder's growing needs. That demonstrates emotional intelligence, respect, and a willingness to understand the concern before defending the current status.
Option A is too defensive because being on schedule does not necessarily mean the stakeholder's business need is being met. Option B is too submissive and assumes fault before understanding the issue. Option C is also defensive because its purpose is to prove the stakeholder wrong rather than address the concern. PMP- style reasoning favors active listening first, then clarification, then appropriate action. By understanding what is driving the dissatisfaction, the project manager can address the real issue and maintain a productive relationship with a key stakeholder.

In an agile project, the sprint review is the appropriate meeting for stakeholders, including board members, to attend. It is a formal opportunity to inspect the increment of the project's deliverables and adapt the product backlog if needed. The sprint review is designed to gather actionable feedback and foster collaboration between the development team and stakeholders12.
: = Agile practices in project management encourage stakeholder involvement in product backlog and project progress1. The PMI also highlights the importance of stakeholder engagement in agile projects, suggesting their participation in planning and review sessions2. Additionally, the importance of board member attendance in meetings is emphasized as it is essential for legal transaction of business and effective board engagement3.