61. Everyone you know is the business meaning of the project?
want. This is Vision meaning. Don't take the project only as a job. Sometimes I want to be a pioneer in the informationization of a certain industry in China, or tell Team Member from time to time, can this project save how many million taxpayers in a certain national department each year, this is Powerful. Ordinary things can also have a noble goal.
62. Are the interfaces and operational habits of each part of the product?
To be this. To make users feel that the entire program seems to be written by one person.
63. Can you be a COOL feature as a highlight of the promotion?
want. This is an enhanced team cohesiveness, confidence. Moreover, "a junior huns", there is a highlight to cover some problems. In this way, for the customer, it feels that the product is still an acceptable from a quality point of view. Alternatively, Cool Feature or highlights can make up for measures as a matter of quality problems.
64. Shorten the start time of the product as much as possible
To be this. Software start-up time is the first impression of customers' performance.
65. Don't pay too much attention to the external impression of the first eye
Programmers are easy to make this error: Too much weight, stability, storage efficiency, but ignore the external feelings. And the high-level manager, the customer is opposite. These two aspects should be taken into account and coordinate these is the work of PM.
66. Do you have developed according to the detailed product function manual?
To be this. It is necessary to have a design to develop. Design documentation, you should say how this product will run, and you should take some stories. Don't diamond details when design, don't drill into the database, code, etc., those behind them, those behind, and step in step.
67. Do you carefully review the functional design before starting to develop and test?
To do it. Function Spec Review is used to unify thinking. Moreover, REVIEW has formed a consensus later, no one can say "you see, I am in the beginning, I am suffering now."
68. Everyone always thinks about the whole image?
To be this. Although everyone is only manufacturing a leaf, everyone should know how they are in the tree in which they are manufactured. I oppose the software blue collar, opposed excessive development of software manufacturing to the pipeline, workshop. See section 61.
69. Is the division of DEV works in a simple portrait or landscape?
It cannot be simply divided according to the functional module, or in a single score according to the performance layer, the intermediate layer, the database. I recommend this: First, according to the function module, then each "layer" has an Owner to review owner's design and code to ensure consistency.
70. Do you write program description documents?
want. However, I heard that Microsoft's programmers did not write before 1999. So, it is not absolute writing, and it is sometimes possible. See Article 56.
71. Do you write a program when you recruit him?
need. I like to make a string and list of questions. This topic has a lot of loops, judgments, pointers, recursive, etc.
72. Do you have a technical exchange?
need. Every two worships have an internal Tech Talk or Chalk Talk. Let the team members share the technical experience, this spent is sent to the outside to train.
73. Can your programmers focus on one thing?
Let the programmer focus on one thing. For example, a department has two projects and 10 people. One way is to let 10 people participate in two projects, each of each item spends 50% time; another method is 5 people going to project A, 5 Personal to project B, each person is 100% on a project. I must choose later. There are many people in this truth understand, but many leaders practices themselves as a resource that can be split. 74. Does your programmer exaggerate the time required to complete a job?
Yes, this is common, especially in the later stage of the project, the time required to do a change, boycotting Change in a time. The method of solving is to sit down and slowly, grind the programmer's counter-opposite, together analyze, and make the granular particles of the estimated time be smaller.
75. Try not to use Virtual Heads
It is best not to use Virtual HEADS. Virtual Heads means Resource IS Not Secure, Shared Resource reduces the work efficiency of Resource, which is easy to increase the chance of error, and people who will use the people don't have much time to go to Review Spec, Review Design. A Dedicated person, it is necessary to have two people who can only put 50% time and energy. I have a loss: 7 part time Tester, discovered bugs and dry live, add up to two full-time. See Section 73. 73 are for programmers, 75 are for Resource Manager.
