Bills of Rights

Customer Bill of Rights

• You have the right to an overall plan, to know what can be accomplished when and at what cost.
• You have the right to get the most possible value out of every programming week.
• You have the right to see progress in a running system, proven to work by passing repeatable tests that you specify.
• You have the right to change your mind, to substitute functionality, and to change priorities without paying exorbitant costs.
• You have the right to be informed of schedule changes in time to choose how to reduce the scope to restore the original date. You can cancel at any time and be left with a useful, working system reflecting investment to date.

_{Kent Beck and Martin Fowler, Planning Extreme Programming, Addison-Wesley, 2001, p. 9.}

Developer Bill of Rights

• You have the right to know what is needed, with clear declarations of priority.
• You have the right to produce quality work at all times.
• You have the right to ask for and receive help from peers, managers, and customers.
• You have the right to make and update your own estimates.
• You have the right to accept your responsibilities instead of having them assigned to you.

_{Kent Beck and Martin Fowler, Planning Extreme Programming, Addison-Wesley, 2001, p. 9.}

Tester Bill of Rights

• You have the right to bring up issues related to quality and process at any time
• You have the right to ask questions of customers and developers and receive timely answers.
• You have the right to ask for and receive help from anyone on the project team, including developers, managers and customers.
• You have the right to make and update your own estimates for your own tasks.

_{Lisa Crispin and Tip House, Testing Extreme Programming, Addison-Wesley, 2003, p. 31.}