Review of Debugging the development process 1. Laying The Groundwork

Any work that does not result in an improved product is potentially wasted or misguided effort.
Don't waste the developers' time on work that does not improve the product.
这些从道理上来说是完全没有问题的，但是作者的做法似乎是太极端了。认为进度报告这样的事情也是毫无意义的。我认为进度报告完全是有必要的，关键是怎么样来做。在我们公司，是每周一召开一次进度报告会议。以前是每个人都要汇报一下自己上周所做的工作情况，这样确实很繁琐，比较浪费时间。后来就改成了由各项目组长汇报本组的情况，这样就一下简单了许多，大家也可以对整个项目的进展情况有个大致的了解，一些共有资源的使用上也可得到协调。当然，会后再写一个书面的报告就完全没有必要了。

作者的做法是：
Each time a team member merges a new feature into the master sources, he or she is to send a short piece of e-mail announcing the new functionality to the rest of the team.
Anytime there's a possibility that a feature will slip, the team member responsible for that feature is to drop by my office to
discuss the cause and brainstorm a solution.
这样的做法似乎有些问题。1. 如果每个人都把自己完成某 件事的讯息发给大家，会不会塞满了每个人的电子信箱？2. 中国人在有些事情上想法与老外有些区别，特别是关于面子问题，如果一个人在进度上落后，我想如果不是领导询问的话，他本人是很难自己提出来的。

Establish detailed project goals to prevent wasting time on inappropriate tasks.
Minimize the project's dependencies on other groups.
Establish coding priorities and quality bars to guide the development team.