Does your organisations environment encourage the formation of long lasting teams, and a safe-to-fail culture, how can we nurture more of this in the software development world?
您的组织环境是否鼓励形成长期合作的团队，以及“失败安全”的文化，如何才能在软件开发的世界培育更多这种团队和文化？
As I discussed in Part I, the distribution of teams across time and space introduces challenges and increases complexity throughout the software and systems development lifecycles.
正如我在第一部分所讨论的，团队跨越时间以及空间的分布给整个软件和系统开发的周期内带来了挑战并增加了复杂性。
The liaison between software development teams and management has always been a sticking point in IT.
软件开发团队和管理层之间的联系始终是IT中的一个关键所在。
Agile development teams attempt to use just enough process in just enough places to enable the predictable delivery of quality software.
敏捷开发团队试图用恰好够用的过程，在合适的时机，按照预期交付高质量的软件。
For example, you may have offshore development teams that need control in the distributed software delivery process.
例如，您可能拥有海边的开发小组，在分布式软件交付过程中他们也需要控制。
One way to achieve these objectives is to have teams selecting and making use of well-known software development best practices in their projects.
完成这些目标的一种方式，是让团队选择并利用项目中最有名的软件开发最佳实践。
When coupled with other techniques described in this article series, it enables development teams to deliver higher-quality software frequently.
当与本文章系列中描述的其他技术结合使用时，开发团队常常能够交付更高质量的软件。
Similarly, some groups try to improve their software development capabilities by reorganizing their teams, in the spirit of the proverbial rearranging of the deck chairs on the sinking ship.
与之类似，有些组织试图通过重组他们的团队来改善软件开发能力，这有些类似于在沉船甲板上重新安排座位。
Software development teams need to change their methods, as traditional approaches cannot keep pace and, indeed, are already failing in many instances.
软件开发团队需要变更他们的方法，因为传统方法不能跟上需求，并且的确已经在许多实例中失败。
The challenge for software development teams is not in creating a single artifact (source code, requirement, or test case) but rather in understanding the relationships between those artifacts.
对于软件开发团队的挑战不在于创建一个单一的工件(源代码、需求或者测试)，而是理解工件之间的关系。
Therefore, software development teams must learn to live in, and cope with a very dynamic world where everything constantly changes 5.
因此，软件开发团队必须学会如何生存，并且处理好这个任何事情都在不断变化的动态的世界。5。
As a general rule, I recommend that development teams check in all of their files necessary to create working software.
作为一般规则，我建议开发团队签入创建软件所需的所有文件。
Based on the six best practices listed above, the iterative approach allows development teams to add functionality to working software in increments.
基于上述的六个最好的实践经验，迭代方法允许开发团队向软件中添加功能。
On many software development projects, the relationship between developers and testers (as well as other teams) is clouded by tension in the form of misunderstanding, disappointment, and frustration.
在许多软件开发项目中，开发人员和测试人员(以及其他团队)之间的关系，由于误解、失望和挫折形式的紧张而被玷污了。
In May 2005, IBM introduced two new toolkits that enable software development teams to automatically identify and repair problems in business applications within production.
2005年5月，IBM引进了两套新的工具包，使软件开发团队能够自动地识别和解决产品在商业应用领域出现的问题。
The agile community champions software development by teams that are co-located — all in the same room, working together, communicating directly, face-to-face.
灵活的团队通过集中工作地点——所有人在同一个办公室，一起工作，直接面对面的交流的方式来支持软件的开发。
This approach to continuously ensuring quality builds success into the project rather than making teams gamble with the unpredictability inherent in software development efforts.
不断使项目逼近质量保障达到成功，而不是使团队迷失在不可预期的软件开发事物中。
Asset standardization promotes efficiency in a similar way, enabling greater efficiency and automation in software development tools and improving productivity for the teams that use them.
资产标准化以类似的方法提高了效率，使得软件开发工具可以更加高效率和自动化的操作，并且为使用它们的团队提高了生产力。
Today's software development teams are wrestling with the increase in development costs associated with maintaining and modifying software.
今天的软件开发团队，正纠结在维护和修改软件的开发成本正不断飙升的烦恼之中。
Not accidentally, this echoes the practices of Agile software teams in handling their development work.
这种方式和敏捷团队进行软件开发有异曲同工之处。
He acknowledges the differences necessary between software and hardware development approaches, and encourages hardware teams to embrace the Agile practices which can work in the hardware space.
他首先承认了在软件和硬件研发活动中存在的不同有着一定的必然性，然后还鼓励硬件团队要在硬件环境中进行敏捷实践的尝试。
In a way, you could say software development teams (for internal or external users) are locked into assembly-line thinking.
在某种程度上，您可以说软件开发团队(对于内部或外部用户)受困于装配线式的思维方式。
He is the primary author of Software Development for Small Teams: a RUP-Centric Approach, published by Addison-Wesley in 2004.
他是小型团队的软件开发：一个以RUP为中心的方法，由addison - Wesley在2004年出版的主要作者。
Gary Pollice, et. al., in the aptly titled book Software Development for small Teams, offers some great advice for the manager of small projects.
Gary Pollice等几位作者在《小型团队的软件开发》一书中为小型项目的管理者提出了一些有价值的建议。
In the fast pace of agile software development, increasing Numbers of teams are adopting Rational team Concert as their project management tool.
在敏捷软件开发的快节奏中，越来越多的团队开始采用RationalTeamConcert来作为他们的项目管理工具。
Booch and Jacobson are well-known visionaries in software development and they, along with others, have recognized the importance of supporting distributed teams.
Booch和Jacobson是软件开发中的有名的构想家，他们，以及其他一些人，已经认识到了支持分布的团队的重要性。
Next month we'll continue to consider the analogies between art and software development by looking at how highly talented software "artists" fit in on software development project teams.
下月，我们将通过研究杰出的软件“艺术”如何适合于软件开发项目团队，继续考虑艺术和软件开发之间的相似之处。
Many Banks are struggling to get software development teams to work together efficiently, and that could be a remote in-house team or an outsourced development team.
很多银行正努力促使软件开发团队在一起高效工作，这样可以形成一个远程的室内开发团队，或者一个资源共享的开发团队。
After going through the steps in this article, hopefully you've improved your productivity and quality using a procedure for automating repetitive build tasks for software development teams.
学习本文后，希望您已经通过使用实现软件开发团队的重复构建任务的自动化的过程提高了效率和质量。
Creates unambiguous documentation and communication among the various teams participating in the software development cycle via the formal, UML-based modeling of users and of user interfaces.
通过正式的、基于UML的用户和用户接口建模，在参与软件开发生命周期的不同团队之间创建明确的文档及通信。
应用推荐