The project manager should use synchronous communication methods if they prefer to have immediate contact with team members. Synchronous communication is a type of communication that occurs in real time and allows for faster response times and more interactive discussions. Examples of synchronous communication methods include phone calls, video conferences, instant messaging, and face-to-face meetings. Synchronous communication can help to build rapport, clarify doubts, and resolve issues quickly among team members.

Synchronous communication should be used when the project manager prefers to have immediate contact with team members. Synchronous communication allows for real-time interaction and feedback, enabling faster response times and more interactive discussions. References: CompTIA Project+ Study Guide Section 3.1.3

An issue log is a tool that records and tracks any issues that arise during the project. It helps the project manager to identify, prioritize, assign, monitor, and resolve the issues in a timely manner. An issue log can also include information such as the issue description, impact, status, owner, and resolution date1. An issue log is different from a defect log, which records and tracks the defects or errors in the project deliverables. A risk register is a tool that records and tracks the potential risks that may affect the project objectives. A change log is a tool that records and tracks the changes that are made to the project scope, schedule, budget, or quality2.

The project manager should communicate with the affected stakeholders first after realizing that the sign-off for the project scope baseline is delayed due to multiple changes and that the budget for this project is restricted by the project sponsor. The affected stakeholders are those who have an interest or influence on the project and may be impacted by any changes or delays. Communicating with them can help to explain the situation, assess the impact, seek feedback, and manage expectations.

A wiki knowledge base is a collaborative online platform that allows users to create, edit, and share information about a specific topic or domain1. A wiki knowledge base is best to use for storing lessons learned because it enables easy access, retrieval, and update of the lessons learned by project teams and stakeholders2. A wiki knowledge base can also support keyword search, version control, and linking of related documents3. A wiki knowledge base is different from a whiteboard, which is a physical or digital board that can be used for brainstorming, sketching, or presenting ideas; a content management system, which is a software application that allows users to create, manage, and publish digital content; and a workflow platform, which is a software tool that automates and streamlines business processes4. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 14: Closing the Project, page 403; Capturing Lessons Learned in Project Management [2023] • Asana, Different types of lessons learned sessions and Lessons Learned Process in Project Management sections; Project Management Lessons Learned | Smartsheet, What Are Lessons Learned in Project Management? and Lessons Learned Process in Project Management sections; How to Do Lessons Learned in Project Management, Store and Retrieve sections.

An Ishikawa diagram, also known as a fishbone diagram, is a tool used to identify and analyze the root causes of a particular problem. CompTIA Project+ references this tool as essential for quality management and problem-solving.

A RACI (Responsible, Accountable, Consulted, Informed) matrix clarifies roles and responsibilities, indicating who needs to be communicated with at various levels. CompTIA Project+ highlights RACI as a critical tool for effective project communication and accountability.

Meeting minutes should be prepared to ensure team members who are absent remain informed about assignments. Meeting minutes document what was discussed, decisions made, and assignments given during a meeting, providing a record of the team's progress and ensuring absent members are up-to-date. References: CompTIA Project+ Study Guide Section 4.2.2

The project manager should prepare meeting minutes to ensure team members who are absent remain informed about assignments. Meeting minutes are a written record of what was discussed and decided in a meeting. They usually include information such as attendees, agenda items, action items, decisions made, issues raised, and deadlines assigned. Meeting minutes can help to communicate important information to team members who could not attend the meeting and provide a reference for future follow-up.