This document discusses how agile software development can go wrong if not implemented properly. It provides an example of a project between an offshore vendor in India and a UK customer that failed due to a lack of understanding of agile methods. Key issues included using a standard development contract with fixed dates and prices instead of a flexible agreement, and limited experience with agile practices by both parties. Potential solutions involve using multi-stage, target cost or target schedule contracts; creative pricing models; and effective governance to formalize regular scope and schedule changes. The conclusion emphasizes that the contract must be dynamic to guide a collaborative relationship rather than just state obligations.