This manifesto appears as the customer bill of rights in Chapter 2 (on Fear) of Planning Extreme Programming. That chapter also covers customer fears, developer fears, the customer bill of rights, and the programmer bill of rights -- Arie Van Deursen
To the managers and customers of this software project:
Article 1:
You have the right to an overall plan. The team should tell you what they could accomplish in the next year or two, and tell you how much that would cost.
Article 2:
You have the right to see progress. From the very beginning of the project, the team should be producing functionality that you care about. The functionality should be in the form of a running system, proven to work by passing repeatable tests that you specify.
Article 3:
You have the right to change your mind. As software development proceeds, you should be able to substitute new functionality for old. You should be able to change the relative priorities of the features of the system, dictating what should be done first and what should be done later.
Article 4:
You have the right to be informed of schedule changes as soon as the programmers know about them. You have the right to exercise your business judgment by choosing among options for reducing scope so as to restore the original date. You have the right to cancel further development at any time and be left with a useful, working system that reflects your investment up to that date.
This is beautiful. Thanks for writing this. --Walden Mathews
The process outlined in the Extreme Programming Summary is designed to allow programming teams to hold up their end of this deal.
See also Help Your Manager
See original on c2.com 