问题描述
背景信息：：我们工作中的会议越来越多，我的老板/团队正在思考如何在此处实施更多的最佳实践。 （这里 =一个很小的应用程序开发商店。4个开发人员）
Background info: More and more of our meetings at work involve my boss/team pondering how to implement more "best practices" around here. ("Here" = a very small application development shop. 4 developers)
以下是我的整个团队都同意我们需要的项目：
The following things are items that my whole team agrees that we need:
- 夜间构建
- 将我们的错误跟踪器中的错误分解为更小，更具体的项目
- 自动测试
我相信，如果我的商店可以简单地选择 清晰明确的计划 或一组规则，那么其他所有内容掉到位。现在，我们陷入对模糊，感觉良好的想法和听起来不错的流行语的讨论。
I believe that if my shop could simply choose a clear and specific plan or set of rules, then everything else would fall into place. Right now we are stuck in discussions of fuzzy, feel-good ideas and nice-sounding buzzwords.
请向我推荐您最喜欢的书（或在线资源），其中应包含清晰的内容，是用于实施指导TDD或敏捷团队/商店的管理方案的分立的顺序步骤。
Please recommend to me your favorite book (or online resource) that contains clear, discrete, sequential steps for implementing a management scheme for guiding a TDD or Agile team/shop.
我意识到，除了TDD和Agile之外，还有其他范式也可以解决这些顾虑，但是我自己的利益和偏见指向TDD和敏捷，因此我很想利用团队对变革的渴望，并朝着这个方向轻推它。或者，如果您强烈不同意我的观点，请随意打我一下！我不会冒犯。 ：）
I realize that there are other paradigms besides TDD and Agile that would also address these concerns, but my own self-interests and biases point toward TDD and Agile so I would love to harness my team's desire for change and "nudge" it in that direction. Or feel free to slap me down if you vehemently disagree with my sentiments! I will take no offense. :)
谢谢大家。
推荐答案
抛出另一个实用程序员标题混合在一起：
To throw another Pragmatic Programmers title in the mix: Ship It!
好书-看一下，可能会适合您的管理需求。
Great book - take a look, might suit your needs with management.
这篇关于最佳混凝土“操作手册” *管理*测试驱动和/或敏捷开发？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！