An agile team's client has been asked to expedite the delivery of the next release. By delivering one month early, the company can generate USS40.000 more than expected for the quarter. What should the agile team do?

An agile team is responsible for maintaining a sustainable pace and ensuring product quality. Expediting a schedule introduces significant risks, such as technical debt, reduced quality, and team burnout. The team's professional responsibility is to be transparent about these risks. Advising the client that it is best to continue as planned is a direct way of communicating that the proposed change carries a high risk of being counterproductive. This opens a collaborative discussion about the trade-offs between the potential financial gain and the risks to the project's long-term health and quality.

A. Immediately adhering to a new deadline without assessing its feasibility and impact on quality is irresponsible and not an agile practice.
C. Proposing a price increase based on the client's potential profit is adversarial and undermines the agile principle of customer collaboration.
D. Requesting additional resources assumes that adding people will solve a schedule problem, which is often false (Brooks's Law) and ignores other solutions like scope reduction.

1. Project Management Institute. (2017). Agile Practice Guide. Principle #8, "Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely," p. 9.

2. Beck, K., et al. (2001). Manifesto for Agile Software Development. The principle of "Sustainable Pace" is a cornerstone of agile development, ensuring long-term productivity and quality.

3. Brooks, F. P. (1995). The Mythical Man-Month: Essays on Software Engineering. Addison-Wesley. This foundational text explains why adding manpower to a late software project makes it later.