Customer Focused

Correct Answer: Discuss the impact of the change with the customer, revisit the project schedule, and adjust tasks as per priority if feasible.

In Agile methodology, teams should be prepared to handle change, even in later stages of the project. The answer 'Discuss the impact of the change with the customer, revisit the project schedule, and adjust tasks as per priority if feasible' is the most appropriate because it indicates a strategy toward managing this change. A frank discussion would clarify how this change could impact the project's timeline or cost, giving the customer an opportunity to make an informed decision. It's also important to revisit the project schedule and reallocate tasks based on new priorities. The other answers are not the best responses: Refusing the customer's request outright contradicts the Agile principle of customer collaboration, incorporating changes without evaluation may lead to project risks and promising changes in the next version without consideration wouldn't be addressing the current situation appropriately.

Correct Answer: Propose a compromise to provide updates every three days to align with the customer's need and your team capacity.

In Agile, the value is placed on customer collaboration and responding to change. Therefore, the best approach is negotiation and compromise that is in line with Agile principles. This is represented by the answer 'Propose a compromise to provide updates every three days to align with the customer's need and your team capacity.' This option tries to balance the customer's requirement and the capacity of the team to deliver, which aligns with the Agile philosophy. This differs from the other options: Ignoring the customer's request ('Ignore the customer's request and proceed with the weekly updates.') is not a good practice as it goes against customer collaboration, an Agile principle. Forcing the team to comply with the customer's request ('Demand the team to provide daily updates as requested by the customer.') may overburden the team and affect the project negatively. Finally, proposing a hike in project cost ('Propose a change in the project cost to meet the customer's demand for daily updates.') may not lead to satisfactory results or desired collaboration with the customer.

Correct Answer: Prioritize the new requests with the customer, understand impact on the project, and adjust the project plan accordingly.

In an Agile environment, change is expected and should be embraced through the project's lifecycle. The best response as an Agile practitioner when the customer asks for additional features midway through the project is to have a discussion with the customer to prioritize these new requests, understand the impact on the project, and adjust the project plan accordingly. This enables the team to be flexible, adapt to change, and deliver the maximum value project to the customer. It is a way to manage scope creep in an Agile environment. The idea behind Agile is to be flexible and responsive to changes, rather than sticking rigidly to the initial plan or rejecting change. So, the options 'Ignore the new requests and continue with the initial plan' and 'Inform the customer that additional features cannot be added midway' are not suitable because they do not follow Agile principles. On the other hand, immediately starting the implementation of new features without prioritization or understanding the impact on the project ('Immediately begin implementing the new features without questioning.') can lead to scope creep, project delay, cost overruns, and reduced project quality, hence, not the right approach.