The project manager should establish a project governance model that aligns with the company's strategic, investment, and compliance requirements. This involves creating a structure that provides oversight, decision- making processes, and performance measurement to guide the project in accordance with the company's objectives. It is essential to tailor the governance model to the specific needs of the project while ensuring it supports the organization's broader governance framework1.
References:
PMBOK Guide - Sixth Edition
"Project Governance Critical Success" by Salina Sandra Alie, MSc, BSc, PMP1.
"Governance of Portfolios, Programs, and Projects: A Practice Guide" by PMI2.

The best course of action in this scenario is to ensure that the content of the project report is clearly understood by all stakeholders and to actively seek their feedback. This approach aligns with the principles of transparency and communication found in both the PMBOK Guide and the Professional in Business Analysis Reference Materials. By clarifying the report's content and engaging stakeholders in providing feedback, the project manager can address any concerns or misunderstandings regarding the project's progress and the iterative nature of the releases. This proactive communication helps to set accurate expectations and fosters a collaborative environment where stakeholders are informed and involved in the project's development process. References: PMBOK Guide, Professional in Business Analysis Reference Materials12.

The stakeholder engagement plan is a component of the project management plan that identifies the strategies and actions required to promote productive involvement of stakeholders in project decisions and activities1.
The project manager should review and update the stakeholder engagement plan to address the needs and expectations of the newly appointed technical manager, who is a key stakeholder for the project. The project manager should also communicate with the technical manager to understand the information gaps and provide the necessary updates on the project deliverables. Updating the issue log and escalating to the project sponsor (option A) may not be the best first action, as it could create unnecessary conflict and damage the relationship with the client. Identifying the lack of information as a risk and updating the risk register (option B) is not appropriate, as the situation is not a potential uncertain event that could affect the project objectives, but rather a current issue that needs to be resolved. Scheduling more frequent meetings with the technical manager (option C) may help to improve the communication, but it does not address the root cause of the problem, which is the inadequate stakeholder engagement plan. References:
* 1: A Guide to the Project Management Body of Knowledge (PMBOKGuide) - Sixth Edition, Project Management Institute, Inc., 2017, p. 518.

In a situation where customer feedback indicates a strong demand for a new feature, it is advisable to deliver a minimum viable feature (MVF) that can provide immediate value while full development continues. This approach aligns with Agile project management principles, which prioritize rapid delivery of value through iterative and incremental development1. By planning for an MVF, the project manager can demonstrate responsiveness to customer needs and provide a tangible product increment within a short timeframe, thus satisfying the urgent request from the marketing department without disrupting the ongoing work of Company B2.
References:
PMI. (2021). A Guide to the Project Management Body of Knowledge (PMBOK Guide) - Seventh Edition.
Atlassian. (2023). Minimum Viable Product (MVP): What is it & Why it Matters2.
MPUG. (2023). Understanding the Minimum Viable Product (MVP) in Agile Project Management1.