According to the PMBOK Guide 7th Edition, the project manager should lead and support the project team and collaborate with them to deliver the project outcomes. In this case, the project manager should meet with the project team to discuss the concerns and determine how to ensure the project's deliverable can compete with the competitor's, such as by incorporating customer feedback, enhancing the features, or applying the newest technology. The project manager should not perform a Kano analysis, as this is a technique to prioritize the customer requirements, not the competitor's. The project manager should not meet with the development team only, as this may exclude other team members who may have valuable inputs. The project manager should not note this concern in the risk register and meet with the sales team only, as this may not address the root cause of the problem and may not involve the project team12. References: PMBOK Guide
7th Edition, Chapter 3: Project Performance Domain, Section 3.3: Lead the Team, Page 65; Chapter 4: Project Delivery, Section 4.2: Collect Requirements, Page 89.

A spike is a time-boxed activity that is used to explore a specific topic or issue, such as a new requirement, a technical challenge, or a risk. A spike can help the project team to gain more knowledge, reduce uncertainty, and plan better. In this case, the project manager should inform the project team of the new privacy law and create a spike for the next iteration to investigate how to comply with it and what impact it will have on the project scope, schedule, cost, and quality. References: PMBOK Guide, 7th edition, section 6.2.3.2; Professional in Business Analysis (PMI-PBA) Guide, 2nd edition, section 5.2.3.2.

In a situation where the project delivery is based on a fixed price in cryptocurrency, and there is an agreement to adjust the scope according to the value of the cryptocurrency at the end of each iteration, an incremental approach with a minimum viable product (MVP) is most suitable. This approach allows for the delivery of increments of value in alignment with the agreed price and enables both parties to assess and adjust the scope iteratively. It accommodates the volatility of cryptocurrency by allowing scope adjustments that reflect the currency's value at regular intervals, ensuring that the project does not exceed the financial constraints while still delivering value12.
References:
* Agile and fixed price projects: How to make it work1.
* PMI's resources on agile project management3.
* Professional in Business Analysis Reference Materials4.

According to the PMBOK Guide, 7th edition, one of the principles of project management is to collaborate with stakeholders. This means that the project manager should maintain effective communication and engagement with the project stakeholders throughout the project life cycle, especially during changes and transitions. When the customer's project manager changes during the final stage of a project, the project manager should review the latest project status report and update the stakeholders, including the new customer's project manager, on the project progress, deliverables, issues, risks, and closure activities. This will help to ensure a smooth handover, alignment of expectations, and timely completion of the project closure process. The project manager should also seek feedback and confirmation from the stakeholders on the project outcomes and satisfaction. References: PMBOK Guide, 7th edition, page 9, Principle 2:
Collaborate with Stakeholders; page 31, Section 2.3.1, Project Stakeholders; page 41, Section 2.5.2.1, Project Status Report.

In an agile project, the project manager does not assign tasks to the team members, but rather facilitates the team's self-organization and empowerment. The team decides how to plan, execute, monitor, and control the work within the sprint, based on the agreed-upon requirements and priorities. The project manager supports the team by removing impediments, providing feedback, and ensuring alignment with the project vision and goals. The daily standup is a short meeting where the team members share their progress, challenges, and plans for the next 24 hours, not a place where the project manager instructs the team what to do. References:
* Agile Practice Guide, page 37
* PMBOK Guide 7th Edition, page 97