Any Work That Does NOT IN An Improved Product Is Potentially Wasted Or Misguided Effort.don't Waste The Developers' Time ON Work That Does Not Improve The Product.
These truth are completely no problem, but the author's approach seems to be too extreme. Things to be considered is meaningless. I think the progress report is exactly necessary, how is the key to do it. In our company, it was a schedule meeting every Monday. It used to be everyone to report the work of their work last week, which is really cumbersome, and it is a waste of time. Later, it was changed to the situation of this group of projects, so that there is a lot of simple understanding of the progress of the entire project, and some common resources can also be coordinated. Of course, there is no need to write a written report after willing.
The author's approach is:
.
Anytime there is a possibility That a feature will slip, the team merr Responsible for That Feature Is to Drop by my office to
Discuss the cause and brrainstorm a solution.
This kind of approach seems to have some problems. 1. If everyone will send someone to someone to everyone, will it be full of e-mail boxes? 2. Chinese people have some differences between some things and foreigners, especially about face problems, if a person is behind, I think if he is not a leader, he is very difficult to come.
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.
