Responsibility of the project leader

1, skilled use of conventional technology, the concept of technology in a thorough understanding;

2, strong understanding, analytical ability, the product needs to understand thoroughly, comprehensive, logical clear and meticulous. The boundary of functional requirements, preconditions, potential pitfalls are clear to the chest, and for the potential hazards of the treatment measures.

3, have a certain experience in development practice, to the project development may encounter problems have a certain understanding and response plan.

4, to understand the temperament of the players, personality characteristics, such as some keen to study the technology, especially the new technology, this kind of business is suitable for the complex logic, some prefer to write documents, writing skills, this kind of suitable for writing interface documents; some are good at communication, suitable for communication needs; some more silent, the pursuit of plain, it is good It is suitable for the business of routine and low logic complexity. The more important thing is to understand the needs of the players, that is, what does he want? This is particularly true of what goals to achieve.

5, able to lead the team independently, can be very familiar with the business requirements of the product line, that is, what we do, what we can do, what we have done? What are we going to do? about how long it takes, how much manpower to invest, what hardware to invest in, cost accounting, what are the possible pitfalls? There are ways to avoid problems that may arise, or to maximize the protection of your company's property. If there is a problem, we can locate the problem very quickly and clearly, and find out the reason, and give an effective solution. What is the development progress? What is the test progress? What is the quality of development? How is the test quality? What are the institutional safeguards? How's the team morale? To lead melancholy, to solve problems for the company.
How many problems can be solved, how many problems can be solved, determine how much value we have.

6, not impatient, calm, large demand disassembly for small demand, small demand disassembly as a function module, functional modules disassembled into operable curd , according to the development process and specification step-by-step coding implementation and test by scene .

7, the root cause of the problem is not serious enough, the detail is not enough, and the thought problem, lack of self-motivated, sense of responsibility.

8, troubleshooting the Method: Debug tracking code, according to the issue of time or keywords to view the log, focus on the entry, the parameter, the exception of the report, the exception code, the use of comparative methods to find differences, tired on rest, change the air, adjust the body and mind. Focus on the change of key attributes such as time, IP, operator, state value and so on.

Responsibility of the project leader