Three projects in parallel, how to make a schedule

Excel expressions are mostly presented in numbers or graphs. If you think that this form can also meet your requirements, then it is nothing to make ** with excel. However, it is not clear how to do it in a few words, and there is a lot of content related to the progress of the project on the Internet.

You should look at other people's cases, analyze and learn from them, and then make your own.

The schedule of a software project is not substantially different from that of any project. Start by identifying a set of project tasks, establishing interrelationships between tasks, then estimating the workload of each task, allocating human and other resources, and specifying a schedule schedule.

Parallelism of software development tasks.

If a software project is attended by multiple participants, the activities of multiple developers will run in parallel.

Gantt Chart.

Gantt diagram is often used to describe the decomposition of tasks into sub-tasks, as well as the progress of each sub-task, the diagram representation method is simple and easy to understand, at a glance, and dynamically reflects the progress of software development. As shown in the table below:

Process planning timeline.

Engineering network diagram.

An engineering network diagram is a directed diagram in which a circle represents an event, a directed arc or arrow indicates the progress of a subtask, the number on the arrow is called a weight, which indicates the duration of this subtask, the number in parentheses below the arrow indicates the maneuvering time of the task, and the circle in the diagram represents the point in time when an event starts or ends with a subtask. As shown below:

Software Quality Assurance Software quality assurance is an important part of software engineering management, and software quality assurance should do a good job in the following aspects:

1) Adopt technical means and tools.

2) Organize a formal technical review.

3) Strengthen software testing.

4) Implement software engineering specifications (standards).

5) Control the change of the software.

6) Measure the quality of the software.

The success of a project is 100% due to the project team, and the failure is 100% responsible for the project manager

1. The failure of the project may be due to some external factors, which means that the project manager's risk assessment of the project is not thorough enough;

2. The loss caused by the delay or inability of the project due to the transfer or turnover of key personnel in the project indicates that the human resource reserve is limited, and more importantly, whether the project manager has considered how to make the project complete on schedule due to the flow of one or many personnel in the team during the project;

3. After the completion of most of the functions of the project, the customer's initial inspection is required, and then a lot of functional improvements and additions are needed, which may be unavoidable, but some of the more absurd is that the customer may say to you after reading it: "This is different from what you want", at this time you can only have the right to do one thing, that is, to enjoy the dizziness! Because some project managers have never said a word to the customer or even worse, have not met once, the initial determination and demand of the project is directly to the business personnel, most customers do not know how to show the real thing in reality in the way of the program to realize, so the project manager at least has to drink an afternoon tea to tell the customer:

The above summarizes the three points of success or failure of the project:

1. Whether the project manager's risk assessment of the project is thorough;

2. Whether the project manager can try his best to save the project progress and complete the task on time in the absence of team members; 3. Whether the project manager has a more in-depth conversation with the customer, the project manager must consider whether the actual problem is really solved for the customer.

Be a good project manager (start with yourself).

First: resource integration before the project; Try to provide a good environment for project development, a comfortable workspace and the working tools that the project is expected to need (try to provide the best), just like a developer has a good machine, you think about how energetic he is! Then there is all the human resources that are actually needed to convene this project;

Second: aptitude test; In view of the characteristics of the software industry, it is not excluded that there are unfamiliar faces in your project team, or it may be the personnel sent from another project team, or the developers of another cooperative company, at this time, you may need to test the ability of the team members, the test is not a question of the ability of the team members, but a test of what role a team member should be placed in a certain position, or what role in the project development is more appropriate. There are many ways to do this kind of test, which can be to do some games or let the team work together to complete a thing that has nothing to do with the project, to observe the characteristics and habits of each member of the team, and then to do a specific test for each technical link in the project, in order to better skip the technical pitfalls, the test method can be customized, but for the team members can not let them feel that this is a kind of test, so that each team member can play their maximum potential in their own suitable position!

Managing a project involves knowledge of project management.

First of all, the project is divided into five stages: project establishment, demand research, implementation, supervision and acceptance, and the general management is also managed according to these five stages.

After a project is established, the project manager should be determined and the stakeholders of the project should be clarified, and the key point of management at this stage is to ask the project manager to complete the written material of the phased achievement "Project Proposal".

Second, the demand research is based on the research content determined by the project proposal, the research and analysis of the project requirements, as well as the completion plan, the description of the project results, and the acceptance criteria. The key point of management at this stage is that the project team submits a Feasibility Report to the project manager

Third, the implementation stage is generally parallel to the supervision stage, which is the key stage of project management, this stage should be real-time control of project progress, funds, quality, manpower, and materials, and it is recommended that the project leader be required to report regularly to facilitate control and management.

Fourth, the acceptance stage is to accept the project results according to the initial goals and acceptance standards. This is where the project manager needs to organize an acceptance review meeting.

Project management contains a lot of details, and it is recommended to start with a book like "Project Management Guide" to learn it systematically.

Just follow the PDCA management tool (plan, execute, inspect and improve the action).

Milestone management has a very important practical significance in the "internal work process management of the enterprise", and is the main management means to ensure the quality of work, so that the "project manager" and "company leaders" can clearly monitor the progress of each work item and make timely arrangements to ensure the completion quality of the entire "work item", so as to effectively improve work efficiency and reduce work costs, especially in major work such as "R&D projects".

The refined ERP enterprise management platform has 100% realized the "milestone" management method, and completely simulated the "management details" and "monitoring process" in reality.