Explanation/Reference:
Explanation:
When you volunteered, you signed a confidentiality statement so you could not disclose what was under way on this activity. Now the Standard has been issued, and to stay in alignment with PMI®'s best practices, you need to issue a change request based on corrective action to realign the performance of the work of your project with your project management plan.

To avoid delivering work that does not add value to the business, the project manager should have taken the following actions:
1.Define a Product Scope: Clearly defining the product scope at the beginning of the project ensures that everyone understands the boundaries of what will be delivered. By having a well-defined scope, the project manager can prevent unnecessary features or functionalities from being included.
2.Stakeholder Alignment: The project manager should have engaged with stakeholders (including business departments) to understand their needs and expectations. This alignment helps ensure that the project team focuses on delivering features that truly add value.
3.Scope Management: Throughout the project, the project manager should have actively managed scope changes. When stakeholders requested functionalities beyond the defined scope, the project manager should have evaluated their impact on business value and made informed decisions.
4.Effective Communication: Encouraging open communication between stakeholders, the product owner, and the project team is essential. Regularly reviewing progress, addressing concerns, and adjusting priorities based on business needs would help avoid unnecessary work.
References: 10. Delivering business value: The most important aspect of project management While options A, B, and C are relevant considerations in project management, the immediate focus should have been on defining and managing the product scope to ensure alignment with business value. Option D directly addresses this aspect1.

Section: Initiation

Explanation
Standup meetings are brief daily meetings that help teams catch up on the progress and challenges of their projects. They are a common practice in agile project management, but they can also be used in hybrid approaches that combine agile and traditional methods. The purpose of standup meetings is to share information, align on goals, and identify any blockers or risks that need to be addressed. Standup meetings are not meant to be long or detailed discussions, but rather quick and focused updates.
To improve the situation with the project team, the project manager should engage the team members in implementing and improving key aspects of the standup meetings, such as:
Setting clear expectations and rules for the standup meetings, such as the time, duration, location, format, and agenda.
Explaining the benefits and value of standup meetings for the team and the project, such as improved communication, collaboration, transparency, and accountability.
Encouraging active participation and feedback from all team members, and ensuring that everyone has a chance to speak and be heard.
Keeping the standup meetings brief, on track, and effective, by avoiding digressions, interruptions, or distractions, and by addressing any issues or questions offline or in separate meetings.
Making the standup meetings fun and engaging, by using different formats, tools, or techniques, such as gamification, visual aids, or online platforms.
By engaging the team in implementing and improving the standup meetings, the project manager can help the team members understand and value the standup meetings, and foster a positive and productive team culture.
References:
Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK Guide) - Seventh Edition. Project Management Institute.
Project Management Institute. (2020). Agile Practice Guide. Project Management Institute.
What Is a Daily Standup? | Coursera
Stand-up and deliver - Project Management Institute
Leading Virtual Stand Up Meetings - Project Management Academy