If such a set of rules existed and was known to work well, a large industry of consultants would disappear overnight. By the contrapositive, there are no "rules" that meet your qualifications.
All the roles are part of the same team, so everyone share the same goal. People collaborate, meet daily, communicating directly, preferably face-to-face.
Everything is based on trust, there is no need for "protection".
The relationships should all be spelled out pretty well in Agile. Of course, with Agile the point isn't to protect you from each other, it's to eliminate differences between you.
For instance, you are supposed to get rid of the concept of code ownership, if you find broken code you fix it. If you need help, pair with the original author.
QA needs representation in the core team. They don't get left behind because they are in every scrum meeting--as, of course, is the customer.
Management's role (if there is management) in agile is to stay out of the way and provide treats :)
These kind of things weren't just made up for fun, they really are important.
Just keep communicating and addressing trouble when it comes up.
It's like in marriage: you can't prepare for every contingency beforehand -- you must be willing to deal with every setback that occurs by talking it through with your partners and finding a way to cope with it.
发布评论
评论（5）
如果这样一套规则存在并且行之有效，那么一大批顾问行业就会在一夜之间消失。反过来说，不存在符合你资格的“规则”。
If such a set of rules existed and was known to work well, a large industry of consultants would disappear overnight. By the contrapositive, there are no "rules" that meet your qualifications.
所有角色都是同一个团队的一部分，因此每个人都有相同的目标。人们协作，每天见面，直接沟通，最好是面对面的。
一切都基于信任，不需要“保护”。
All the roles are part of the same team, so everyone share the same goal. People collaborate, meet daily, communicating directly, preferably face-to-face.
Everything is based on trust, there is no need for "protection".
这些关系都应该在敏捷中得到很好的阐明。当然，敏捷的重点不是保护你们免受彼此的侵害，而是消除你们之间的差异。
例如，你应该摆脱代码所有权的概念，如果你发现损坏的代码，你就修复它。如果您需要帮助，请与原作者配对。
QA 需要核心团队中的代表。他们不会因为每次 scrum 会议而被抛在后面——当然，客户也是如此。
管理层在敏捷中的角色（如果有管理层）就是不妨碍并提供款待:)
这些事情不仅仅是为了好玩而编造的，它们确实很重要。
The relationships should all be spelled out pretty well in Agile. Of course, with Agile the point isn't to protect you from each other, it's to eliminate differences between you.
For instance, you are supposed to get rid of the concept of code ownership, if you find broken code you fix it. If you need help, pair with the original author.
QA needs representation in the core team. They don't get left behind because they are in every scrum meeting--as, of course, is the customer.
Management's role (if there is management) in agile is to stay out of the way and provide treats :)
These kind of things weren't just made up for fun, they really are important.
敏捷宣言怎么样？
http://agilemanifesto.org/
还有 12 条原则，我相信您会链接到：
http://agilemanifesto.org/principles.html
编辑
抱歉，我误解了这个问题。这些还是一些很好的原则！
How about the agile manifesto?
http://agilemanifesto.org/
And the 12 priciples, which I'm sure you'll link through to:
http://agilemanifesto.org/principles.html
Edit
Sorry, I misunderstood the question. These are still some good principles!
只要继续沟通并在出现问题时解决即可。
就像在婚姻中一样：你不可能事先为每一种意外情况做好准备，你必须愿意通过与伴侣讨论并找到应对方法来应对发生的每一次挫折。
Just keep communicating and addressing trouble when it comes up.
It's like in marriage: you can't prepare for every contingency beforehand -- you must be willing to deal with every setback that occurs by talking it through with your partners and finding a way to cope with it.