The project summary a year ago, brought ugly, and learned with you. Project team project development experience summary (5 points)
2 Before developing, do a good job.
a) The project plan should be divided by milestones, such as:
i. Initial Plan (Phase I) only achieves basic functions.
II. Overall Plan (Phase II) to achieve the most urgent functions.
Iii. The three-phase plan implements all functions.
IV. The four-phase plan realizes the accessory function.
b) Detailed plan, the project plan is only a general plan, generally only guiding, and does not operate.
I. If necessary, do weekly planning a week.
Ii. Week plan to track, do not plan to feel the same.
Iii. Summary cannot complete the task. The concentration of firepower destroyed it, and it will be lost.
c) Plan to adjust it at any time according to the actual environment
i. After finishing the plan, it is not equal to all things, and it is planned to adapt to a variety of different needs, rather than need to adapt to your plan.
2 In development, we must do a variety of review, which is the fundamental of quality assurance.
a) code inspection
i. Team members inspect each other
II. Interface people review providers
Iii. When the milestone, the code collectively checks
b) Document review
i. Good design is good code
Ii. Before the documentation review (or if there is no commonality, become a discussion)
III. The meeting record of the documentation review must be implemented (the problems found by the review have not been revised, it is equal to no review)
c) Help each other
i. The ability of the collective is greater than the sum of individuals
1. In software development, the group of groups is the best way to solve the problem.
II. Each group member is not only to do its own business, but also doing things to do other groups.
1. The task with your interface must be strictly checked, because it directly affects your quality of work.
2. The progress of any group will affect the overall progress, everyone is obliged to help other members
3. Serious pre-examination is responsible for the quality of the development of the entire group
Doing your own business is to contribute to yourself and help others contribute to the entire group.
2 Test work should be fully fitted
a) Pay attention to testing
i. When I found a problem, I rushed to the scene in the first time.
1. Because some problems can not be well reproduced
2. Confirm that BUG is still misuse
Ii. The problem of problem is resolved, don't shirk responsibility
Iii. The question proposed to solve it, don't have it.
Iv. Test staff ask questions to accept
1. Test staff is the first user of the project. If you have the first user's opinion, you are not accepted, then wait until the release is the complaint of the user.
v. Solve bugs to cure, dig out the substance of the back, but in a few days, it is going to resolve this bug.
Vi. bug is going to track. This is the responsibility of the test results. (Developers, not just testers)
VII. There are many bugs to pay special attention.
2 Things to do when the project is closed
a) Summary of the items to be lost (avoiding mistakes in the future)
b) Reconstruction code
i. Some common algorithms or functions are refined into public modules, and after the use, it also increases the development speed after
II. Redesign for many issues, it is not easy to understand or do not comply with code specification.
c) Celebrate (raise morale), of course, it is best to celebrate every milestone.
2 Project team leader to do something (do a good nanny).
i. Solve the most difficult problems.
u When solving a difficult problem, stand in the first line.
Ii. Provide a good environment to group members. u Solve the leaders of the external interface, do not affect the work of the team.
u Resolve the problem of group members.
III. Coordinating relationships
u Appropriate communication can avoid various conflicts
u Improve group combat skills
IV. Tilting Policy
u When a teamwork work is difficult, he often assists him.
V. Do a good job of tracking (including progress, bug, meeting, design, etc.)
Vi. Encourage (team leader is a group of morale symbols)
The U project is long, and there will always be discouraged, and you will encourage the team members.
VII. Awards and penalties (this group is not implemented, but also the company supports)
u is good, it should be different from not doing well.
u has a short award and long-term reward.
