According to the Professional in Business Analysis (PMI-PBA) Examination Content Outline1, one of the tasks of a business analyst is to "communicate and manage solution scope boundaries and approval processes to stakeholders" (Task 5.2). This implies that any changes to the solution scope should be approved by the relevant stakeholders and follow a predefined process. The PMBOK Guide2 also states that "the project manager, project team, and other stakeholders are responsible for determining how the project scope will be managed, how scope changes will be integrated into the project, and who will approve the scope changes" (Section 5.6.1). Therefore, the project manager should advise the team not to engage in modifications unless it follows the proper change approval process, as this would ensure that the scope is controlled and aligned with the project management plan. References:
* 1: Professional in Business Analysis (PMI-PBA) Examination Content Outline
* 2: A Guide to the Project Management Body of Knowledge (PMBOK Guide) - Sixth Edition

According to the Agile Testing: A Practical Guide For Testers And Agile Teams1, security and performance testing are two types of nonfunctional testing that are important for agile teams. Security testing ensures that the system is protected from unauthorized access, data loss, or corruption. Performance testing measures how the system responds to different levels of load, stress, and concurrency. These types of testing can be done at different levels of granularity, from unit testing to system testing, and can use tools such as JMeter, LoadRunner, or Selenium.
Story testing is a type of functional testing that verifies that the system meets the acceptance criteria of each user story. User stories are short descriptions of the features or functionalities that the customer wants from the system. Story testing can be done by the developers, testers, or customers, and can use tools such as FitNesse, Cucumber, or SpecFlow.
Tests based on behavior and test-driven development are two approaches that support agile testing practices.
Behavior-driven development (BDD) is a technique that uses natural language to describe the expected behavior of the system in different scenarios. Test-driven development (TDD) is a technique that involves writing the tests before the code, and then refactoring the code to make the tests pass. Both BDD and TDD help to clarify the requirements, design the system, and ensure the quality of the code. They can use tools such as JUnit, NUnit, or RSpec.
References: (Professional in Business Analysis Reference Materials source and documents) Agile Testing: A Practical Guide For Testers And Agile Teams, Lisa Crispin and Janet Gregory, Addison- Wesley Professional, 2009 Scrum Testing: A Detailed Guide to Testing on an Agile Team, Testim, Accessed on January 29, 2024 Agile Testing Best Practices & Why They Matter, Atlassian, Accessed on January 29, 2024

The stakeholder engagement assessment matrix is a tool used to document the desired and current engagement levels of stakeholders and identify potential gaps in their involvement. It is particularly useful in complex projects with a large number of stakeholders to ensure that their participation and involvement are aligned with project needs. By evaluating this matrix, the project manager can strategically plan how to engage each stakeholder group effectively, which is crucial for the successful delivery of the project12.
References:
* Stakeholder Engagement Assessment Matrix: Uses & Example [PMP-relevant] - Project-Management.info1.
* Stakeholder Engagement Assessment Matrix: PMP Tips [2024] - DeepProjectManager.com2.
* A Guide to the Project Management Body of Knowledge (PMBOKGuide)3.
* The PMI Guide to Business Analysis3.

A hybrid approach combines predictive and adaptive elements to deliver projects. In a hybrid approach, the project manager can break down the requirements into smaller and manageable chunks, and prioritize them based on their value and risk. This way, the project manager can deliver the most important and uncertain requirements first, and get feedback from the stakeholders and customers. This feedback can help clarify the unclear requirements and improve the quality of the project deliverables. The project manager can also adjust the delivery plan based on the changing requirements and environment. A hybrid approach is suitable for projects that have some degree of uncertainty and complexity, and that need to respond to changing customer needs and expectations. References:
* A Guide to the Project Management Body of Knowledge (PMBOK Guide) - Seventh Edition, Chapter
2: Value Delivery System, Section 2.3: Delivery Approaches, pp. 31-35
* Project Management Professional (PMP) Handbook, Section 2.2: PMP Exam Content Outline, Domain II: Process, Task 1: Plan and manage project scope, pp. 14-15
* Hybrid Project Management: What It Is & How to Implement It, by Simplilearn, published on February
10, 2020

In an agile project, transparency and communication are key. When a team member anticipates a delay, it is important to discuss the issue openly with the team as soon as possible. This allows the team to understand the potential impact on the project and to collaborate on finding a solution. The agile methodology encourages daily meetings for this purpose, making it the ideal setting to address such concerns. This approach is supported by the PMBOK Guide, which emphasizes the importance of communication and stakeholder engagement in project management. Additionally, the Professional in Business Analysis (PBA) reference materials highlight the value of addressing issues promptly and collaboratively in an agile environment.
PMBOK Guide - Sixth Edition; Professional in Business Analysis (PBA) Reference Materials.