改善软件团队成员之间沟通的方法 [英] Ways to improve communication between members on a software team

问题描述

当我所在的团队致力于形式化和建立更多的开发实践时，我发现交流似乎在以下几点上失败了：

1. 在有关项目的非正式对话中，脑力激荡成为一项新功能/要求。经过一段时间后，这些附加组件似乎无法通过裂缝或使细节变得模糊。




2. 在没有目标或任务的会议中明确授权，参加会议的成员对实际讨论的内容有不同的说法。




3. 作为一个团队，我们一直在面临挑战（现在，我们越来越渴望编写它们）以生成质量规格和技术文档，以详细说明项目中需要具备的功能。

我的问题是：解决这些通信瓶颈和效率低下的建议和方法有哪些？没有程序员喜欢编写文档，但希望有一种方法可以使我们集中理解，并在项目的生命周期中使信息更加可见和可用。

谢谢您的帮助！

解决方案

坚持到议程。保持目标。当事情开始偏离路线时，可以安排其他会议，也可以在会议结束后通过电子邮件发送给他们。在预期的时间做什么。是的，这意味着有人需要在会议期间编写/键入内容。

如果文档变得越来越重要且需要，那么我强烈建议您提出简单的标准，然后坚持下去。

Wiki。维基。维基。对团队有用的所有部落知识信息都需要进入Wiki。如何设置开发环境，常见的调试技巧等。

As the team I am on works to formalize and establish more development practices, I find that communication seems to fail at the following points:

1. During an informal conversation about a project a brain spark moment becomes a new feature/requirement. These "add-ons" seem to fail through the cracks or the detail become fuzzy after some time has passed.

2. In meetings where objectives or tasks aren't clearly delegated, the members involved in the meeting have different accounts of what was actually discussed.

3. As a team we are constantly challenged(more so now that we actually are aspiring to write them) to generate quality specs and technical documents that detail exactly what features need to be in projects.

My question is: What are some suggestions and approaches to addressing these communication bottlenecks and inefficiencies? No programmer likes writing documentation but there hopefully is a way that we can centralize understanding and keep that information more visible and available during the life-cycle of a project...

Thanks for your help!

解决方案

Stick to the agenda. Stay on target. When things begin to veer off course, either schedule another meeting or take it to email after the meeting.

End each meeting with action items - a written list of who's going to do what and when it's expected. Yes, this means someone needs to write/type something during the meeting.

If documentation is becoming important and needed, then I strongly suggest you come up with simple standards and then stick to them.

Wiki. Wiki. Wiki. All "tribal knowledge" information useful for the team needs to go into a wiki. How to set up dev environments, common debugging tips, etc etc.

这篇关于改善软件团队成员之间沟通的方法的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！