Project Stakeholder Rights
The rights of project stakeholders are:
1)To have developers learn about their business and objectives.
2)To expect developers to learn and speak their language.
3)To expect developers to identify and understand their requirements.
4)To receive explanations of artifacts that developers use as part of working with project stakeholders, such as models they create with them (e.g. user stories or essential UI prototypes), or artifacts that they present to them (e.g. UML deployment diagrams).
5)To expect developers to treat them with respect.
6)To hear ideas and alternatives for requirements.
7)To describe characteristics which make the product easy to use.
8)To be presented with opportunities to adjust requirements to permit reuse, reduce development time, or to reduce development costs.
9)To be given good-faith estimates.
10)To receive a system that meets their functional and quality needs.
11)To determine how their resources will be spent by the project team, including the extent of the investment in permanent documentation.


Project Stakeholder Responsibilities
The responsibilities of project stakeholders are:
1)To provide resources (time, money, ? to the project team.
2)To educate developers about their business.
3)To spend the time to provide and clarify requirements.
4)To be specific and precise about requirements.
5)To make timely decisions.
6)To respect a developer's assessment of cost and feasibility.
7)To set requirement priorities.
8)To review and provide timely feedback regarding relevant work artifacts of developers.
9)To promptly communicate changes to requirements.
10)To own your organization's software processes, to both follow them and actively help to fix them when needed.

-by Scott W. Ambler, Copyright 2002

 转载说明。
　

---

这片短文列出了Project Stakeholder角色的权力和职责。我们在项目开发中可能遇到各种各样的Project Stakeholder，如何能合理的解析他们的权力和职责，引导或者遵从Project Stakeholder的协作和指令是开发团队能否开发成功一个项目的关键因素之一。我看到这篇短文的介绍，觉得考虑得比较全面，张贴出来大家一起看看，探讨探讨？

The rights and responsibilities of project stakeholders are:

To have developers learn about their business and objectives.
To expect developers to learn and speak their language.
Must educate developers about their business.

To expect developers to identify and understand their requirements.
Must spend the time to provide and clarify requirements.

To receive explanations of artifacts that developers use as part of working with project stakeholders, such as models they create with them (e.g. user stories or essential UI prototypes), or artifacts that they present to them (e.g. UML deployment diagrams).
Must be specific and precise about requirements.

To expect developers to treat them with respect.
Must respect a developer's assessment of cost and feasibility.

To hear ideas and alternatives for requirements.
Must make timely decisions.

To describe characteristics which make the product easy to use.
Must promptly communicate changes to requirements.

To be presented with opportunities to adjust requirements to permit reuse, reduce development time, or to reduce development costs.
Must review and provide timely feedback regarding relevant work artifacts of developers.

To be given good-faith estimates.
Must set requirement priorities. //有点牵强

To receive a system that meets their functional and quality needs.
Must own your organization's software processes, to both follow them and actively help to fix them when needed.

To determine how their resources will be spent by the project team, including the extent of the investment in permanent documentation.
Must provide resources (time, money, ? to the project team.
　

但是——估计你也是开发者吧？:(

原文的作者是一个非常著名的人物，他正在主持AgileModeling的讨论组，并写了不少文章和一本（或几本？）关于AM的书。很有经验。

不过真正开发项目中遇到的客户各种各样，我感觉是很难按照他描述的那样去顺利地展开工作的。话虽如此，他提出的这些权力和职责（呵呵，也包括您提出的诸多must）相信对Project Stakeholder具有很好的参考价值。

关键在“沟通交流”－“理解尊重”。

呵呵，幸好，我们项目的Stakeholders还都是通情达理的。（至少没有很多开发人员经常抱怨的那些弊病）
作为项目经理，处理好各个StakeHolders之间的关系确实是一件很复杂的事情。

“沟通交流”还可以通过能力训练来提高；“理解尊重”就包含着一点人格魅力的因素在里面了。——所以，不是每个优秀的开发人员都可以当项目经理的。

关于Scott W Ambler，我是从几篇他关于EJB和UML的文章开始知道他的。确实很有经验。