On-Site Customer

Correct Answer: Assess the requirement, its impact on the current sprint and discuss the possibility of addressing it in the next sprint with the customer.

The best course of action when a new requirement is provided by the customer in the middle of the current sprint, according to Agile principles, is to assess the requirement, its impact on the current sprint and discuss the possibility of addressing it in the next sprint with the customer. Incorporating the requirement immediately without any discussion could lead to scope creep and potential resource shortages. Rejecting the requirement as it was not in the initial scope is against Agile's iterative and collaborative approach, which encourages changes. Simply ignoring the requirement until the ongoing sprint is over might lead to customer dissatisfaction and loss of potential value added to the product.

Correct Answer: Educate the customer on the Agile principles, emphasize on prioritizing value and reassure them of the iterative nature of Agile.

Agile methodology values customer collaboration and responding to change, but this does not mean the scope of a sprint should be continually expanded. Sprints should be manageable and well-defined. Attempting to squeeze in more work into the sprint, ignoring the customer's suggestion completely or arguing with the customer would not adhere to the principles of Agile, and could lead to stress, reduced quality of work and dysfunctional team dynamics. The best response is to educate the customer on the Agile principles and reassure them of the iterative nature of Agile, which emphasizes delivering value incrementally and making adjustments based on feedback after each iteration.

Correct Answer: Involve the customer in a discussion about the problem and altering product scope due to limitations.

In an Agile project, transparency and active communication are fundamental. When encountering a problem, the Agile team should inform the customer and involve them in the discussion. This will lead to either finding a solution together, or altering the product scope due to the technical limitations. This approach ensures that all stakeholders acknowledge the problem and any consequent changes are agreed upon. Other options such as ignoring the problem, hoping it will resolve itself (not a proactive approach), or keeping the customer in the dark to maintain a positive image (against Agile’s transparency principle), or asking the customer to solve the technical issue (not a role of the customer) are not align with Agile principles and may harm the project and team's relationship with the customer.