I wrote a "philosophy" of leading software development teams in which you may find some useful perspectives. Find it here : http://aaronofward.com/philosophy.html
There are other factors that come to my mind in terms of being major impacts on a team:
Motivation - Does everyone in the team do their best? How committed to achieving success are they? Do they have that drive to get to the finish line? Is everyone conservative in their work because everyone is afraid to make mistakes and fail? I don't think this falls under the "simple and clear way." Culture or psychology could be other terms to describe this aspect of what's important to get things done.
Technique - Process would be another term for this part. How do things flow, does the team seem to be running at a good pace or are there spurts and stops? If this isn't set up well, then it should be obvious what kind of disaster can come. I'll grant you that a "simple and clear way" is very similar to this point.
Just to give a bit more of an example to this, let me explain some of how things work in my team:
There are daily Stand up meetings where each person summarizes their progress yesterday, what they plan for today and what blockers do they have. Blockers while they may seem a simple concept for someone that has spent some time doing technical things, isn't necessarily that simple in the end. Why does this prevent you from finishing tasks, what work arounds are available, who has the authority to decide which path should be taken are a few questions about it that some may have.
Then there is pair programming where a developer pairs with another and together some task gets done so that a pair of people have the knowledge of what was done and that it isn't just one person's mad science experiment.
Sprints and the planning meetings around it are another aspect used to help structure how we get things done and promoted through our environments so that priorities can be adjusted as needed over time.
Story cards are used to break work down into bite-size pieces and move along a wall to mark progress as well as tracking time spent on each card for a burndown chart.
Now, take all those ideas and practices, does it seem like I work in a simple and clear way? While each little part may be simple, collectively I don't think it is that easy to pick up and understand all the subtlities of how things get done. For more information look at Motivation and Technique.
发布评论
评论（2）
我写了一篇领导软件开发团队的“哲学”，您可能会在其中找到一些有用的观点。 在这里找到它：http://aaronofward.com/philosophy.html
I wrote a "philosophy" of leading software development teams in which you may find some useful perspectives. Find it here : http://aaronofward.com/philosophy.html
在对团队产生重大影响方面，我想到的还有其他因素：
动机 - 团队中的每个人都尽力而为吗？ 他们对取得成功的决心有多大？ 他们有动力到达终点线吗？ 每个人在工作上都保守，因为每个人都害怕犯错误和失败吗？ 我认为这不属于“简单明了的方式”。 文化或心理学可以是描述完成工作的重要方面的其他术语。
技术 - 过程是这部分的另一个术语。 事情进展如何，团队是否运行得很好，或者是否有突然和停止的情况？ 如果这个设置不好，那么会发生什么样的灾难应该是显而易见的。 我承认“简单而清晰的方法”与这一点非常相似。
举一个更多的例子，让我解释一下我的团队中的一些事情是如何运作的：
每天都有站立会议，每个人都会总结他们昨天的进展、他们今天的计划以及他们有哪些障碍。 对于花了一些时间做技术事情的人来说，拦截器似乎是一个简单的概念，但最终并不一定那么简单。 为什么这会阻止您完成任务、有哪些解决方法可用、谁有权决定应采取哪条路径，这些是一些人可能会提出的问题。
然后是结对编程，其中一个开发人员与另一个开发人员结对，共同完成一些任务，这样两个人就知道所做的事情，并且这不仅仅是一个人的疯狂科学实验。
冲刺和围绕它的规划会议是另一个方面，用于帮助构建我们如何通过我们的环境完成和推广工作，以便随着时间的推移可以根据需要调整优先级。
故事卡用于将工作分解为小块，并沿着墙壁移动以标记进度以及跟踪每张卡上花费的时间以形成燃尽图。
现在，看看所有这些想法和实践，我的工作方式看起来是不是简单明了？ 虽然每个小部分可能都很简单，但总的来说，我认为掌握和理解事情完成方式的所有微妙之处并不是那么容易。 有关详细信息，请参阅动机和技术。
There are other factors that come to my mind in terms of being major impacts on a team:
Motivation - Does everyone in the team do their best? How committed to achieving success are they? Do they have that drive to get to the finish line? Is everyone conservative in their work because everyone is afraid to make mistakes and fail? I don't think this falls under the "simple and clear way." Culture or psychology could be other terms to describe this aspect of what's important to get things done.
Technique - Process would be another term for this part. How do things flow, does the team seem to be running at a good pace or are there spurts and stops? If this isn't set up well, then it should be obvious what kind of disaster can come. I'll grant you that a "simple and clear way" is very similar to this point.
Just to give a bit more of an example to this, let me explain some of how things work in my team:
There are daily Stand up meetings where each person summarizes their progress yesterday, what they plan for today and what blockers do they have. Blockers while they may seem a simple concept for someone that has spent some time doing technical things, isn't necessarily that simple in the end. Why does this prevent you from finishing tasks, what work arounds are available, who has the authority to decide which path should be taken are a few questions about it that some may have.
Then there is pair programming where a developer pairs with another and together some task gets done so that a pair of people have the knowledge of what was done and that it isn't just one person's mad science experiment.
Sprints and the planning meetings around it are another aspect used to help structure how we get things done and promoted through our environments so that priorities can be adjusted as needed over time.
Story cards are used to break work down into bite-size pieces and move along a wall to mark progress as well as tracking time spent on each card for a burndown chart.
Now, take all those ideas and practices, does it seem like I work in a simple and clear way? While each little part may be simple, collectively I don't think it is that easy to pick up and understand all the subtlities of how things get done. For more information look at Motivation and Technique.