To help customers and the development team work together, XP came up with a customer and developer bill 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.
Programmer 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.
The bill of rights were a powerful means of setting expectations with folks, and letting them know who was responsible for what.
For example, XP made it pretty clear that developers shouldn’t be making calls about business priorities. That was the domain of customer.
In exchange, customers would stop telling engineers how long it would take to do there jobs. Or anything technical in nature (like how to build the system). That was the domain of the developers.
You may not have this problem today, but if you do, pull these out and put them infront of your team to ensure everyone knows what role they are planning, and what they should be entitled to on your project.
And if these rights don’t work for you. Create your own. Just don’t let the issue fester. Get everyone together, get into a room, and make it clear who gets to own what.
Making this clear could be the most important thing you do for your project.