In an agile project, risks are managed in a continuous and iterative manner, which involves constantly evaluating risks and adapting the project backlog and priorities accordingly. This approach is aligned with the agile principle of responding to change over following a plan, as it allows for flexibility and quick adjustments based on the evolving nature of the project and its associated risks.
References: = Agile methodologies emphasize the importance of continuous risk evaluation and adaptation.
The PMBOK Guide also supports this approach by recognizing the need for iterative planning and response to risks. Agile practices such as daily stand-ups, sprint reviews, and retrospectives are designed to identify and assess risks regularly, ensuring that the project can adapt to changes quickly and efficiently12.

Explanation
According to the PMBOK Guide, project monitoring and controlling involves the processes of tracking, reviewing, and regulating the progress and performance of the project. One of the tools and techniques for monitoring and controlling project work is data analysis, which includes methods such as performance reviews, trend analysis, and variance analysis. The project lead should use data analysis to collect and evaluate the operational usage data of the software system, which reflects the actual behavior andpreferences of the users. This will help the project lead to measure the delivered value of the project and identify any gaps or improvement opportunities. Building the functionality in the software to collect the operational usage data is the most accurate and reliable evaluation practice, as it avoids the biases or errors that might arise from other methods such as questionnaires, feedback forms, or interviews. References:
PMBOK Guide, Sixth Edition, Chapter 4: Project Integration Management, pp. 111-158.
PMP Exam Prep Coursebook, Chapter 4: Project Integration Management, pp. 4-1 - 4-24.
Project Evaluation Process: Definition, Methods & Steps by Peter Landau

Explanation
According to the PMBOK Guide, 6th edition, page 368, communication can be classified into formal and informal, written and verbal, and vertical and horizontal, depending on the context, purpose, and audience of the message. Informal verbal communication, such as a conversation, is a type of communication that is spontaneous, casual, and flexible, and that can be used to exchange information, ideas, opinions, or feedback in a timely and direct manner. Informal verbal communication is suitable for handling a situation where a team member is not performing very well, as it can allow the project lead to express concern, empathy, and support, as well as to identify the root causes of the poor performance, and to explore possible solutions or improvements. Informal verbal communication can also help to maintain a positive and trusting relationship between the project lead and the team member, and to avoid any misunderstanding, resentment, or demotivation that may arise from more formal or written communication. References:
PMBOK Guide, 6th edition, page 368
Free PMP Practice Exam Questions - 120 Sample Test Questions