Skip to Content

Changes for page Bill of Rights

Last modified by chrisby on 2024/06/20 14:39
From version 1.16
edited by chrisby
on 2023/11/18 13:56
Change comment: There is no comment for this version
To version 1.20
edited by chrisby
on 2023/11/26 14:04
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,15 +1,11 @@
1 -# Introduction
1 +The purpose of the [Bill of Rights](https://www.informit.com/articles/article.aspx?p=2990402&seqNum=3) is to resolve common disputes between customers and developers by defining a clear, distinct sets of rights and expectations for effective cooperation. Make sure that developers and customers can always visit a bill to resolve disputes that arise during discussions. Below is the original version of the Bill of Rights, with the sub-bullets being some of the more detailed explanations I have provided.
2 2  
3 -The purpose of the [Bill of Rights](https://www.informit.com/articles/article.aspx?p=2990402&seqNum=3) is to resolve common disputes between customers and developers by defining a clear, distinct sets of rights and expectations for effective cooperation. Make sure that developers and customers can always visit a bill to resolve disputes that arise during discussions.
4 -
5 -# Commented Bill of Rights
6 -
7 7  ### 1. Customer Bill of Rights
8 8  
9 9  You have the right to
10 10  
11 11  * an overall plan and to know what can be accomplished when and at what cost.
12 - * Developers can't predict the exact amount of work for a story, but they must specify the uncertainties. See [[Planning Game|doc:Software Engineering.Agile.Extreme Programming.Planning Game.WebHome]].
8 + * Developers can't predict the exact amount of work for a story, but they must specify the uncertainties. See [[here|doc:Software Engineering.Agile.Extreme Programming.Planning Game.Effort Estimation.WebHome]] for more details.
13 13  * get the most possible value out of every iteration.
14 14   * Developers must work on the features that have the highest level of usable business value. "Usable" means ready to be used effectively by end users.
15 15  * see progress in a running system, proven to work by passing repeatable tests that you specify.
... ... @@ -27,10 +27,10 @@
27 27  * know what is needed with clear declarations of priority.
28 28   * Developers can ask customers to clarify requirements. Customers have the right to change requirements outside of an iteration, but not within an iteration.
29 29  * produce high-quality work at all times.
30 - * No developer should be forced to damage their reputation or violate their work ethic by delivering low-quality code.
26 + * No developer should be forced to damage their reputation or violate their work ethic by delivering low-quality code. It is the developer's right to spend time refactoring code until it is clean.
31 31  * ask for and receive help from peers, managers, and customers.
32 32   * With the right to ask for help comes the responsibility to give help.
33 33  * make and update your own estimates.
34 - * Estimates are intelligent guesses, not commitments. Of course, estimates get better over time as new insights are gained.
30 + * Estimates are intelligent guesses, not commitments. Estimates improve over time as new knowledge is gained, so they should be updated.
35 35  * accept your responsibilities instead of having them assigned to you.
36 36   * For each iteration, customers specify the tasks to be done, but developers internally negotiate who does what. Developers have a deeper understanding of the technology and team experience, resulting in a more efficient allocation of resources. An individual developer has the right to say "no" to a task during the negotiation process, due to the availability of better alternatives or a lack of confidence in their abilities, and take on another task instead.