Schedule management

First, planning, schedule management, scheduling planning unit, progress report formats such as separate modules: divided into several modules, and the demand for modules in subdivided, resources allocated to each module performs order: do the function first, after doing those function to estimate the working hours: forecast each module of the working hours, gives a report schedule chart formulation: Schedule control based on project priorities, block priorities, and resource calendars: Schedule control is implemented based on the schedule. First, determine the scope and decomposition of objectives strictly determine the scope of the project, and then break the project into modules, fine granularity of what each person does. Second, make good use of schedule management software use some management software. Such as ONES, Zen, etc., can timely check the current project status. 3. Carry out the daily station meeting, summarize the problems of yesterday and plan the tasks and progress of the day. 4.Copy the code

Project resource coordination

Planning resource management, estimating the amount of resources needed for the project and allocating resources: Allocating resources according to the priority of the project and the resource calendar of each person. Managing resources: After the team is finalized, managing all aspects of internal resources, such as conflict resolution, morale building and resource release: If there are resources in the project that have been completed in the current project, they can be redeployed to other projects to summarize resource management: Summary resource management experience and record 1, according to the project priorities, to specific which project priority use of resources, 2, and resource calendars for each resource, based on its resource calendar coordinate cooperate with project priorities in 3, improve the work ability of every engineer, improve output 4, appropriate to give some reward policy 5, coordinated by the influence of superior leadershipCopy the code

Software quality management

First planning of quality management, according to the risk register, schedule a benchmark or the national standard of iso9001, the quality of some, secondly management quality, ensure project has been according to quality standards, if there is a problem, find the problem, and correct them, the rushed out, the deployment of resources deployment of resources The final quality control: Quality verification is carried out at each stage to ensure that the quality is always the last step in accordance with the standards. Maintainability of the quality management process is summarized: the software developed has high maintainability in the later use, because Internet companies have frequent staff turnover. Code readability: the readability of the code is very important, high readability, for later project maintenance friendly software testability: testers for the test when the bug of positioning is very clear, not confused front end, increase the cost of testing code modifiability: if there is a bug, it changes time, want to have good changes Robust code: The code should be robust, and the try should be judged when the try is made. The running speed of the system is a very important part of the requirements of today's customers. Security: the confidentiality of some key data in our own system, as well as the confidentiality of customer dataCopy the code

Risk management

The first planning risk, early identification of some risk Second planning risk response to the identification of risks or planning, preparing for the plan to deal with risks, if there is a risk, to to update the risk response and risk, some qi fengxia no no, you want to update, and delete summarized risk, the risk arising from the project summary, Risks that may help project management for future projects: demand risk, unclear demand, change of customer demand schedule risk: technical level, or lack of resources, project experience quality risk: technical level leads to poor system quality Technical risk: design, interface, maintenance, management risk: Business risk is caused by the situation of the manager and the managed: product development conforms to the strategy in the early stage, but does not conform to the strategy in the late stage. Legal risk: license right, patent social factor risk: influence of national policy, customer company's late applause system, etcCopy the code

What is most important in project management

1. Understanding ability: First of all, it is necessary to understand the development direction of the company, the intention of the leader, and the leader's expectation for the project; Then it is to understand the needs of customers, this understanding is not only the customer said I understand it, the key is to be able to tap the deep needs of customers; The third is to be able to understand the feedback of various stakeholders in the process of the project and be able to accurately respond to it; 2. Communication skills, communication skills do not mean to be a microphone, but to have clear logical and analytical skills, able to quickly make analysis and judgment; 3. Risk control ability, able to timely predict risks in the project process, take measures and give appropriate feedback to leaders of both parties.Copy the code

How are requirements controlled when they change

Demand change is often encountered in software projects. In the process of preliminary demand research, it is necessary to cover all stakeholders, including the decision-making layer, the control layer and the executive layer, so as to understand the most complete requirements through their work and form standardized documents. It is best to sign and confirm the requirements when they are recognized by both sides. Develop a complete process of changing requirements, what process should be adopted once the requirements are changed, and what leaders are needed to review, which should be standardized in advance.Copy the code

If the project team continues to improve echelon construction

The first step is to set up the project objective, implement the whole objective to all team members, so that the team has a common direction of effort; The second step is to be able to be alone with each employee to understand the details of each member of the team, including technology, strengths, weaknesses, and areas of expertise. Task decomposition and role division are carried out according to each person's situation. The third step is to establish a team learning and sharing mechanism, so that everyone can be improved in this project. The fourth step joint functional departments regular assessment, reward and punishment clear; The fifth step is to hold various group constructions at irregular times within the cost range.Copy the code

What should we do when we meet strong customers

If it is the demand raised by the department leader of the customer and cannot be rejected, I think we can first coordinate research and development to make a preliminary demo, so that the customer leader can see our execution ability and attitude, and then step by step explore the customer demand and improve. Because the customer's demand is not immutable, most of the time, the customer does not know what function or demand they want, he may just have a preliminary idea, if we put a lot of energy into it, most of the work may be useless.Copy the code