Skip to Content

Changes for page Bill of Rights

Last modified by chrisby on 2024/06/20 14:39
From version 1.23
edited by chrisby
on 2024/03/04 21:43
Change comment: There is no comment for this version
To version 1.21
edited by chrisby
on 2024/02/22 16:20
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,4 +1,4 @@
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 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.
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 3  ### 1. Customer Bill of Rights
4 4  
... ... @@ -7,7 +7,7 @@
7 7  * an overall plan and to know what can be accomplished when and at what cost.
8 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.
9 9  * get the most possible value out of every iteration.
10 - * 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, not theoretical business value provided by partial implemented features.
10 + * 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.
11 11  * see progress in a running system, proven to work by passing repeatable tests that you specify.
12 12   * Developers must write acceptance tests that are developed in collaboration with customers.
13 13  * change your mind, to substitute functionality, and to change priorities without paying exorbitant costs.