I. Project manager definition: responsible for plan, budget, contact with management, negotiate with customers. It may be accepted by technical training, but do not do development; in a large project or cross-domain project, it may be necessary to guide several team leaders to carry out work; mainly responsible for delivery within the budget.
Second, the step of the new project leadership: 1. Study the project information, find relevant personnel to talk to seize the problem = "decided to join the team. 2. Draft Project Plan - Outline - based plan - more detailed, better (best yourself) 3. Project demand manual (in the same way as possible, try to write more accurate, more professional) - "Let others review -" Recently collect detailed opinions of customers (those "most important people", such as customers or markets) (it is best to be responsible) 4. Define the best structure (modules and libraries) and Design (the entire technical team participation) - "Determining key interfaces in the system (note: Use all other external resources, such as ready-made available libraries, tools, and a block, etc.) =" minus teamwork. 5. Create a coding frame (internal and external rough interface) - "unit test structure (completed by one or two people) -" Other people's audit (for the first time for encoding) - "Organization project structure (including creation A project directory, establish a version control, an enterprise internal network, etc., and create a framework to make everyone working in this framework) - "Create the original directory and file, even if there is nothing else (eg, Final test file). 6. Detailed plan and Gantt chart (initially assigned work tasks for team members) 7. Beginning the implementation of the project (ie the team begins to fill the desired design, writing code, daily test and document record) - "Check has been completed What work has been (Note: Do not use the original model as the final product, to filter the beneficial thing to reuse) - team stable, forming leadership "plateau" (I can relax) At this time my main task: 1 Clear obstacles. Solve problems in advance, such as training needs, etc. 2) Let everyone use Wuzhi and let them work together. = "Everything is inserted. 3) Defend the design. Prevent anyone from getting shortcuts during design. 4) Demonstrate the management and customer demos. = "Is recognized. 5) Contact and discuss (with other project leaders, departments and organizations) = "seek the help and resources needed, while reminding people to note this project. 6) Call experts and consultants (from organizational internal or external) = "Methods 7 for help" to do small, daily technical decisions, or authorize others to do these decisions. These decisions are required for projects. 8) Keep the project is in order. Manage a folder related to the project, an enterprise internal network and an IT directory. Turn the past work record, organize the management of the configuration. 9) Grasp the correct direction of the project. It is not possible to allow project deviation from the right direction. 10) Decide when to issue progress to the customer or market. Includes internal release of the formal testing of the project, but also decides to publish. 11) Check the design, encoding, and file records at the appropriate time. 12) Update demand instructions, test instructions, design, etc. 13) Handling changes in demand, resource issues, and other factors that interfere with the original plan implementation. 14) Call the meeting when necessary. 15) Guide and pay attention to other members of the team, especially some of the primary levels. 16) By granting certain responsibilities and encouraging training to promote membership development, it is necessary to keep their knowledge to keep up with the trend.
