In a project with tight deadlines, global virtual teams, and a fixed budget, avoiding scope creep and keeping the team focused on meeting requirements during the planning phase is critical. The best approach for a project manager (PM) in this scenario is:

A. Go through formal approval processes for all scope changes

Here’s why this option is the most appropriate:

1. Formal Approval Processes for All Scope Changes:
   • This ensures that any changes to the project scope are thoroughly evaluated, justified, and approved before being implemented. This helps prevent unauthorized changes that could lead to scope creep, keeping the project on track with its original goals and budget constraints.
   • According to the Project Management Institute (PMI), a formal change control process is essential for managing scope changes effectively. It helps maintain control over the project by ensuring that all changes are documented, reviewed, and approved by the appropriate stakeholders​ (Time and Date)​​ (WeatherBug)​.
2. Daily Stand-ups with All Development Teams:
   • While daily stand-ups are useful for team coordination and quick issue resolution, they do not directly address scope creep. They are more focused on daily progress and impediments rather than controlling scope.
3. Detailed Documentation by Development Team Leads:
   • Detailed documentation is important for clarity and consistency, but it does not inherently prevent scope creep. Documentation should be a part of the overall project management process, including how changes are managed.
4. Keeping Stakeholders Separate from Development Team Leads:
   • Effective communication and collaboration between stakeholders and development teams are crucial for project success. Separating them might lead to misunderstandings and misalignment with project goals.