Everyones Rights And Responsibilities

From post by ScottAmbler to the AgileModeling mailing list at 2003.04.08 6:27 AM

Everyone's Rights:

To be treated with respect.
To produce and receive quality work at all times based on agreed to project standards and principles.
To estimate the activities you are actively involved with, and to have those estimates respected by others.
To be provided adequate resources (time, money, .) to do the job that's been asked of you.
To determine how your resources will be invested. For people funding the project how the funds will be spent and for people working on the project (e.g. investing time) what tasks they choose to work on.
To be given the opportunity to gain the knowledge pertinent to making the project a success. Business people will likely need to learn about the underlying technologies/techniques and technical staff to learn about the business.
To have decisions made in a timely manner.
To be provided good-faith information in a timely manner. Sometimes this is just the "best guess" at the time, and that's perfectly all right. This includes but is not limited to business information such as prioritized requirements and detailed domain concepts as well as technical information such as designs and detailed technical concepts.
To own your organization's software processes, following and actively improving these processes when needed.

Everyone's Responsibilities:

To produce a system that best meets your needs within the resources that you are willing to invest in it.
To be willing to work with others, particularly those outside your chosen specialties.
To share all information, including "work in progress".
To actively expand your knowledge and skillset.

This list is a work in progress on the AgileModeling mailing list.

If the first right is to be treated with respect, shouldn't it be the first responsability to treat with respect?