2. Summary of daily plan management

1Daily MEETING

We adopt a meeting mechanism for routine work arrangements and inspections.

The meeting mechanism ensures the daily arrangement and follow-up of project tasks and achieves orderly saturation of the project team's work. In March, the team adopted the daily meeting mechanism, which was proposed and discussed by the "intensive meeting". In March 4 and, the team improved the meeting to meet on Monday, Wednesday, and Friday. In May 6 and July, due to work shortage and high Progress requirements, the daily meeting mechanism was adopted and the customer was reported on work days. The meeting will be held on Monday, Saturday, and Friday after the task is relaxed in March.

(1) The key to meeting mechanisms is:

① Time is short.What we hate most is the long meeting. One meeting is one morning and one afternoon. The long meeting is very inefficient and exhausting. Therefore, the first key to the meeting is to control the meeting time, generally within 15 minutes.

② Fast frequency.The short meeting time means that we have more time to work. Once a problem or new situation occurs, we can quickly meet again to discuss the situation and respond quickly.

③ The number of students is small.Except for specific meeting meetings, other meeting meetings will be attended by people, and non-related people will not be allowed to participate. Generally, the best meeting person is 3-5 people.

(2) benefits:

① High Efficiency.The meeting will be one of the most effective ways of communication in the process of handling daily affairs. In a short period of time, the relevant personnel should communicate with each other in order to solve and handle the problem, and the relevant personnel should immediately work again.

② Strong controllability.Since the project work is always in contact and communication, all the operations are clear, and the work is not going to be conducted in a similar way, so as to avoid situations where the work has been completed and found completely different from what was originally imagined, the control of the project process is enhanced.

③ High transparency.As you interact with each other to understand their work conditions and make relevant work transparent, you can easily understand what to do at hand to avoid laziness and motivate your work.

 

However, there will also be some inapplicable points, mainly for some things that require a long discussion to produce results, such as demand review, design review, and work summary discussion.

 

2Long-term project planning

The Team has always had a good weekly report mechanism for customers and a monthly report system for the company. At present, we feel that monthly reports, weekly reports, and daily work tasks cannot be directly associated, not integrated, and tracing is inconvenient, which is not conducive to global grasp. There is a lot of room for improvement.

We tried to improve this problem in March, but it was interrupted by the shortage of tasks. Our idea is to build a tool to integrate the plan decomposition arrangement with the daily task report, so as to implement the plan decomposition layer by layer, one report of the task, unified summary, and a global view. There are three key points:

① Globally unified plan management and reporting;

② It must be integrated with requirements, Bug management, and other transactions;

③ Combine the rewards and punishments mechanism.

By doing so, you can:

① Rewards and Punishments mechanism to guide the completion of work;

② Performance basis, fairness and justice;

③ The view at each layer is transparent and the progress of the auxiliary project is controllable.

 

The current idea of Project Plan Management is as follows:

Implement a project management tool to manage the goals, tasks, resources, and problems in the project, so that project members can achieve the goal management and quickly report the work and problem completion.

Functions:

1, Resource management

(1) manage resources within the project, and the resources are cost-effective;

(2) collect statistics on the usage of each resource, list of tasks allocated to the resource, and generate reports;

(3) various resources canVery convenientView and manage your goals, tasks, and problems;

2, Task management

(1) management personnelQuick release CreationA task is assigned to a resource. The task includes the name, content, weight, start date, completion date, resource allocation and time, and attachments;

(2) project memberQuick CreationTask;

(3) management personnelEasy to adjustTasks, including task-level relationships, ownership relationships, and resource allocation;

(4) project members can conveniently report the task completion status, and set the completion level for task completion, for example, excellent or poor;

(5) The task completion status can be summarized in layers and categories;

(6) various resources allow you to conveniently view the task lists of yourself and its subordinates (days, weeks, and months );

3, Target management

(1) Hierarchical Decomposition of objectives;

(2) A target can be associated with multiple tasks. In principle, a task only belongs to one target;

(3) Quantifiable completion degrees can be set for the target, for example, excellent or poor;

(4) Target Process Management is planning;

4Requirement Management

(1) The requirement is to describe what the project is to be done. It is the foundation of the project, the source of the target, and the task;

(2) requirements can be divided into functional requirements, performance requirements, implementation requirements, and release requirements from the information system perspective;

5, Problem management

(1) problem management includes System Bugs, small demands raised by the customer, and small improvements made by the system, which are generally tested, investigated, or proposed by the customer;

(2) problems can be obtained after a task is completed. You can specify the task that generates the problem, or assign a task to solve the problem;

 

Question:

1What are the relationships and differences between goals and tasks?

The goal is a state and result that can be achieved through long-term efforts. It is a long-term result, such as a goal;

A task is a short-term process to achieve a certain result. For example, a task is heavy;

The goal is achieved by completing the task;

Both the target and task can be hierarchically decomposed;

2What are the relationships and differences between goals and needs?

The requirement is to describe what the project is and define the scope of the entire project;

The goal is to define when to complete the requirements and fulfillment;

3What are the relationships and differences between tasks and requirements?

Tasks must be carried out based on requirements. tasks that are separated from requirements are not allowed;

4What are the relationships and differences between tasks and problems?

After a task is completed, a question is raised, which is the result of the task completion;

In order to solve the problem, the corresponding task will be arranged, which is the content of the task;

After the task is completed, there will be problems, which will reflect the quality of the task completion;

This reflects the task completion Assessment: The task completion is assessed by the completion time and the two elements of the problem.

Compared with the actual completion time, the smaller the actual completion time, the higher the task completion efficiency;

Compared with "actual task completion time * resource usage unit cost" to solve the problem and "actual task completion time * original resource usage unit cost", the lower the ratio, higher task completion quality;