减小的团队大小。
"Luck" will not hold as the team size scales up.
“幸运”并不会随着团队规模的增加而保持住。
A typical team size is about 10 programmers.
一个典型的团队规模大约是10的程序员。
Communications problems appear when the team size increases.
当团队规模增长时沟通问题就会出现。
Ever-dwindling team size made pair programming more difficult.
团队人数的减少使得成对编程更为困难。
Obviously, the cost of idle resources goes up as the team size goes up.
很明显的是，空闲资源成本随着团队大小的增长而提高。
Decide on the iteration length, as well as the expected team size and composition.
决定迭代长度，以及期望的团队规模和组成。
Research and experience show that ideal agile team size is 20 to 30 people-or fewer.
研究和经验表明，理想的敏捷团队规模为20到30个人员——或者更少。
It may seem silly to be so specific, but keep your team size small during Elaboration.
说得这样明确可能很愚蠢，在细化阶段，使您的团队大小保持小规模。
Use small team size to reduce the cost of development by reducing the impact of idle resources.
使用小型团队，通过减少空闲资源的影响来减少开发成本。
Selecting a process to match team size is usually done by someone, or some group, in the team who will use it.
选择一个过程来与团队规模匹配通常由团队中使用它的人或者团队来完成。
It's also important to note that reducing team size can have far-reaching effects beyond what I've shown here.
还有一点十分重要，缩小团队的规模能够产生超出预想的效果。
If we consider process as a standardizing mechanism, then the need for process goes up as the team size increases.
如果我们将过程看作一个标准化的机制，那么当团队规模增长时对过程的需求就会随之增长。
Team size affects more than just the number of communication channels. It affects all parts of the team's process.
团队规模的大小不仅仅影响到沟通渠道的数量，它还影响团队过程的各个部分。
Large project: Has a budget over $500,000, a team size of thirteen or greater, and a duration of more than a year.
大型项目：预算超过$500,000，团队规模为十三人或者更大，项目进行时间超过一年。
In study iv, the author discusses the relationship between team size, social exchange, and team effectiveness.
研究四中，本文作者讨论了团队规模、社会交换和团队效能三者间的关系。
Team size can be as small a 1 and as large as 500, it all depends on your definition of team and member involvement.
团队规模可以是1个人这么小，也可以是500人这么大，完全基于你对团队的定义和成员的投入程度。
The model shows that output of single team increases as team size growing, but the marginal return is decreasing.
模型分析表明，单个团队的产出随着团队规模的增大而增大，但是增加团队规模的边际产出是递减的。
Two main factors increase the odds of a script being duplicated in a single web page: team size and number of scripts.
两个主要因素增加单个We b页中被重复的脚本的赔率：团队大小和数量的脚本。
Medium project: Has a budget of $100,000-$500,000, a team size of six to twelve, and a duration of six months to a year.
中等项目：预算$100,000-$500,000，团队规模为六到十二人，项目进行时间为六个月到一年。
However, many organizations still struggle with questions related to the optimal team size and an efficient team composition.
然而，很多组织仍然纠结于最佳的团队规模和有效的团队构成。
For project teams with more than seven members, Scrum advises breaking into multiple teams rather than increasing the team size.
对于人数多于7人的项目团队，Scrum建议与其扩大团队规模不如将团队分组。
In small development efforts (in terms of team size or deployments), ignorance of the separation of roles can be successful enough.
在小型开发工作中（指的是团队规模或部署规模），即使忽视角色划分也能获得成功。
Figure 1: the effect of team size on communication: as teams grow larger, the number of communication links grows in a non-linear fashion.
图1 .团队规模对沟通的影响：当团队规模增长，沟通连接的数量并不是呈线性增长的。
In Agile, the team size is pretty small, so if only one person keeps working on the new technology, then the team becomes dependent on him.
在敏捷里，团队规模相当小，因此，假若某人一直在从事新技术，那么团队就会对他产生依赖。
In my view, team size along with communication issues they bring are directly proportional to product size, so I focus on team size as the leading indicator.
在我看来，它们产生的团队规模连同沟通的问题与产品的规模是成比例的，因此我将团队规模看作最主要的指示标识。
IBM Rational's tool in this arena is called Rational Portfolio Manager (RPM) and can significantly help to automate 1, 2, 4, and even 6 when it is time to expand the team size.
在此领域内的IBMRational的工具叫作 RationalPortfolioManager（RPM）并且当是时候扩展团队大小时能够较大地帮助将1、2、4甚至6 自动化。
This paper analyzes the influences of salary system, team size, the degree of risk aversion staff and pay gap on team cooperation, team competition and team efficiency within a unified model.
本文在一个统一模型下分析了企业薪金制度、规模大小、员工风险厌恶程度和报酬差距等激励因素对团队合作、团队竞争和团队效率的影响。
The second approach to estimating a team velocity is to determine the iteration length and team size, and then decide how many stories the team could complete in an iteration. This is done as follows.
第二个估算团队速度的方法是，确定迭代的长度和团队规模，然后决定团队在一个迭代内能完成多少故事。
The second approach to estimating a team velocity is to determine the iteration length and team size, and then decide how many stories the team could complete in an iteration. This is done as follows.
第二个估算团队速度的方法是，确定迭代的长度和团队规模，然后决定团队在一个迭代内能完成多少故事。
应用推荐