When faced with the competitor's announcement, the project manager should take the following actions:
1.Reduce Scope Items: Given the competitor's shorter timeline and fewer features, the project manager should reevaluate the project scope. Reducing the scope items of the final deliverable allows the project team to focus on essential features and deliver a more streamlined product within the available time frame.
2.Discuss External Risk with Project Sponsor: The project manager should engage

In a hybrid project life cycle, which combines elements of both traditional (predictive) and agile (adaptive) methodologies, empowering the team to self-organize and make their own decisions is often the most effective approach. This is particularly true in situations where requirements are continuously changing, as it allows the team to adapt more quickly and effectively. In this scenario, the project manager should empower the team to advance the stones without waiting for his or her approval, thereby increasing the speed and efficiency of the testing process. References: PMBOK Guide, 6th Edition, Section 3.1.3 - Life Cycle Description: Predictive, Iterative, Incremental, and Agile

According to the PMP Exam Content Outline, one of the tasks of the project manager is to "Assess and prioritize impact on project scope, schedule, cost, quality, and risks of approved changes, and determine cause and effect relationships" (Task 5, Domain II: Process). This implies that the project manager should evaluate the impact of any change that affects the project performance, such as the removal of a key team member. By doing so, the project manager can identify the potential consequences and benefits of the change, and look for alternatives to mitigate the negative effects or enhance the positive ones. The project manager should also submit a change request if required, to update the project management plan and baselines accordingly. This will help to maintain the project alignment with the objectives and expectations of the stakeholders. References:
PMP Exam Content Outline, Domain II: Process, Task 5, page 101
PBA Exam Content Outline, Domain IV: Evaluation, Task 4, page 152
A Guide to the Project Management Body of Knowledge (PMBOK Guide), Sixth Edition, Chapter 4: Project Integration Management, Section 4.6: Perform Integrated Change Control, page 1233 Business Analysis for Practitioners: A Practice Guide, Chapter 6: Traceability and Monitoring, Section 6.4:
Manage Changes to Requirements, page 117

In an iteration-based project, the project team should collaborate with the stakeholders frequently and continuously to ensure that the product meets their expectations and needs. The project team should also identify and resolve any impediments or issues that may affect the delivery of the product. By holding a touchpoint with the marketing team before the demo, the project team could have aligned their expectations, clarified the requirements and constraints, and addressed any potential risks or challenges. This would have helped to avoid the issue of the marketing team needing more iterations to launch the product and not starting their work yet. References: (Professional in Business Analysis Reference Materials source and documents) PMBOK Guide, 6th edition, Chapter 5, Section 5.1.2.1, page 152 PMBOK Guide, 6th edition, Chapter 6, Section 6.2.2.1, page 191 PMBOK Guide, 6th edition, Chapter 13, Section 13.2.2.1, page 507 PMBOK Guide, 6th edition, Appendix X3, Section X3.2.2, page 718 PMI PMP-Project Management Professional Practice Exam Q. 781 to 790

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.