The Meridian mobile-banking team has a signed 40-page requirements document, but during the first two-week iteration the client watches the working login flow and asks for three material changes. The team lead argues that the contract fixes the scope and the changes should wait for a formal change request. Which position best reflects the values of the Agile Manifesto?
- ADefer the changes to a later release, because the signed requirements document is the team's contract and must govern the current iteration.
- BWelcome the client's changes now, because responding to change is valued over following a fixed plan when it delivers a better product. Correct
- CReject the changes outright, because customer collaboration tends to matter most at the start of the project when the scope is first agreed.
- DAccept the changes only after the client raises a formal written change request through the document-control process.
Why A is wrong: This treats comprehensive documentation and the plan as fixed authority, which inverts the Manifesto value that prioritises responding to change, so it is wrong.
Why B is correct: The Manifesto value 'responding to change over following a plan' supports adapting to the emerging requirement rather than deferring to the original scope document, so this is correct.
Why C is wrong: It is tempting because early scoping does matter, but the Manifesto values ongoing customer collaboration throughout delivery, not just at kickoff, so this is wrong.
Why D is wrong: A heavyweight change-control gate favours process and documentation over individuals and interactions and responding to change, so although it feels disciplined it conflicts with the values here.