Developing the resource management plan is the first process in the resource management knowledge area.
The resource management plan describes how the project resources, including human resources, will be acquired, allocated, developed, managed, and released. One of the components of the resource management plan is the training plan, which identifies the training needs, objectives, methods, and evaluation criteria for the project team members. By developing the resource management plan and ensuring adequate training, the project manager can address the skill gaps of the team members and prepare them for the key tasks later in the project. This will also enhance the team performance, motivation, and satisfaction. References: (Professional in Business Analysis Reference Materials source and documents)
* PMBOKGuide, 6th edition, Section 9.1, pp. 308-313
* PMI Professional in Business Analysis (PMI-PBA)Examination Content Outline, Domain II:
Planning, Task 2, p. 9
* Business Analysis for Practitioners: A Practice Guide, Section 3.4.1, p. 66

According to the PMBOK Guide, scope change control is the process of managing the changes to the project scope and ensuring that they are aligned with the project objectives and benefits. Scope change control involves identifying, documenting, analyzing, approving, or rejecting changes to the project scope. Scope change control also requires updating the project management plan, project documents, and project baselines to reflect the approved changes. Scope change control is part of the integrated change control process, which involves coordinating changes across all aspects of the project, such as schedule, cost, quality, risk, and stakeholder expectations. The CCB is a formal group of stakeholders who are responsible for reviewing and approving change requests and ensuring that they are consistent with the project charter and business case.
The CCB also monitors the impact of changes on the project performance and benefits. The project manager should collaborate with the CCB to review the scope and submit any change requests that are necessary to keep the project on schedule while still meeting the project objectives. This will ensure that the scope changes are properly evaluated, authorized, and communicated to the project team and other stakeholders. The other options are not the best choices because they do not follow the scope change control process and may result in scope creep, rework, conflicts, or missed expectations. Option B is incomplete because it does not mention the collaboration with the CCB and the review of the scope. Option C is risky because it may increase the cost and complexity of the project without ensuring that the scope changes are justified and approved. Option D is irresponsible because it ignores the impact of scope changes on the project schedule and quality. References:
* PMBOK Guide, Seventh Edition, Chapter 4: Project Integration Management, Section 4.6: Integrated Change Control
* PMBOK Guide, Seventh Edition, Chapter 5: Project Scope Management, Section 5.6: Scope Change Control
* PMI-PBA Guide, Chapter 5: Planning the Business Analysis Approach, Section 5.3: Benefits Tracking
* Scope change control - Project Management Institute

Knowledge transfer is the process of sharing relevant and valuable information, skills, and experiences among project team members and stakeholders. It is essential for agile projects, as they require frequent collaboration, communication, and feedback among the project team and other parties. Knowledge transfer can help the new team member to understand the project vision, scope, objectives, deliverables, requirements, and processes, as well as the roles and responsibilities of the project team and the customer. It can also help the new team member to learn from the best practices, lessons learned, and challenges faced by the previous team member and the rest of the team. The project manager should schedule knowledge transfer sessions with the new team member, involving the previous team member (if possible), the other team members, the customer representative, and any other relevant stakeholders. The knowledge transfer sessions should be interactive, engaging, and tailored to the specific needs and interests of the new team member. The project manager should also assign less complex tasks to the new team member, to allow them to gain confidence, competence, and familiarity with the project work and the agile approach. The project manager should provide feedback, coaching, and support to the new team member, and monitor their progress and performance. This is part of the Manage Team process, which aims to optimize the project team's performance and interaction. The other options are not the best choices because they do not facilitate effective knowledge transfer and integration of the new team member into the project team. Assigning the new team member the same tasks that were assigned to the previous team member who they replaced (option A) may be unrealistic, as the new team member may not have the same level of skill, experience, and knowledge as the previous team member. It may also create confusion, frustration, and conflict among the team members and the customer. Sending technical documentation to the new team member and scheduling training for the next iteration (option C) may be helpful, but it is not sufficient to provide the new team member with the contextual and practical knowledge that they need to perform effectively on the project. It may also delay the new team member's contribution and involvement in the project work. Having the new team member complete all of the company's mandatory training (option D) may be a requirement, but it is not specific to the project and may not cover the agile principles and techniques that are relevant for the project activities. References:
* Project Management Professional (PMP) Reference Materials:
* A Guide to the Project Management Body of Knowledge (PMBOK Guide), Sixth Edition, Chapter 9: Project Resource Management, pp. 313-372
* Agile Certified Practitioner | PMI
* Professional in Business Analysis (PBA) Reference Materials:
* Business Analysis for Practitioners: A Practice Guide, Chapter 3: Needs Assessment, pp. 41-42
* Knowledge Transfer and its Importance for Project Managers

According to the PMBOK Guide, a servant leader is a leadership style that focuses on serving the needs of the team, empowering them, and creating a culture of trust, collaboration, and ownership. A servant leader should also motivate and inspire the team, especially when they face challenges or fatigue. If some team members are starting to complain about the length of the project, creating a risk for lack of performance at this critical stage, the project manager should schedule a team event with the project sponsor to highlight the importance of the project and recognize the work of the team. This will help the project manager to mitigate the risk by showing appreciation and gratitude to the team, reinforcing the project vision and value, and boosting the team morale and engagement. Scheduling a team event with the project sponsor is also a way of celebrating the team's achievements and rewarding them for their efforts. Meeting with the team to reinforce their responsibilities and the consequences if the project deliverables are not completed on time is not a servant leader approach, as it may demotivate and pressure the team, and create a negative atmosphere. Applying additional controls to the project deliverables to ensure that all milestones are achieved on time is not a servant leader approach, as it may micromanage and constrain the team, and reduce their autonomy and creativity. Contacting the functional manager to ensure that team motivation remains high until the end of the project is not a servant leader approach, as it may delegate the responsibility and authority of the project manager, and undermine the relationship and trust between the project manager and the team. References:
PMBOK Guide, 6th edition, pages 56-57, 686-687, 723-724.

For a new product launch aimed at testing market readiness, an adaptive approach is recommended. This approach allows for flexibility in responding to the market and adjusting the product based on feedback.
Clearly defined user stories help the team understand and deliver what is most valuable to the customer, which is crucial in a business transformation context where the goal is to open new delivery channels for the product. This aligns with the PMBOK Guide's guidance on adaptive environments where requirements and solutions evolve through collaboration12. The PMI-PBA also emphasizes the importance of understanding stakeholder needs and defining requirements to meet business objectives, which is facilitated by well-defined user stories34.
References:
PMBOK Guide - Seventh Edition5
PMI Professional in Business Analysis (PMI-PBA) Handbook3
PMI Professional in Business Analysis (PMI-PBA) Examination Content Outline4
"How Do You Decide Which Project Delivery Approach to Take?" - PMI1
"Which Project Delivery Approach Is Right For My Project?" - Portland Webworks2