How to effectively control project progress -- pay attention to details

Text/Li chenxu-author Li chenxu, manager of R & D center of fanshun panteng (Beijing) Network Technology Co., Ltd.

The purpose of project management is to smoothly analyze and manage personnel, products, processes and projects according to the predefined cost, schedule and quality requirements. In project management, some details need to be paid attention by the Project Manager.

Planning Based on experience

That is, a small amount of planning is done first, and further planning is made based on the information obtained in the practical process, which can improve the feasibility of the project. It is difficult to predict the future. Unless you are a prophet, you should try your best to make plans and schedules based on your experience in the project.

Schedule a project

First, schedule by deliverables rather than by functions; second, schedule by iteration; and again, schedule by using less difficult tools. A project timeline that is excessively perfect may mean wasting more time in real projects.

Enough time to plan

The schedule is developed by the entire project team. Therefore, everyone must have confidence in the schedule. However, there will always be some unexpected events, so we have to make enough time to plan and use a wave of planning to flexibly update the schedule as the environment changes.

Manage meetings

When organizing a project, the project manager should avoid wasting time on meetings. This is the simplest and most effective way for teams to focus on projects. When helping the team move toward a reasonable delivery deadline, ensure that the team is not affected by external interference. If the meeting is of no value to anyone, cancel it and allow team members not to participate in meetings that cannot contribute or reap value. Some team members may be unhappy and think that they are not important enough to attend the meeting. I want to explain to them that you don't want them to participate because they are too important.

Speed chart

If you can only draw one chart, select a speed chart. The speed Gallery has three measurement methods: requirement, completed work, and time. Although you cannot see the defect rate or cost you want to know, you can grasp the overall progress of the project from this figure. Using a speed chart, you can measure multiple trends at the same time in a chart: the overall number of requirements and completed work, including all tests, documents, project requirements, and other content. This is the most useful chart and a good friend of the Project Manager. However, note that a speed chart is only a tool for obtaining data, not an aim.

Test

From the beginning of the project, we must adhere to the principle of "reducing technical debt" to synchronize testing and development. The test will present project risks to everyone. The sooner you see these risks, the better. In projects that adopt a sequential life cycle, testers should be involved in the requirement analysis stage to ask their feedback on product requirements. In projects that adopt iterative life cycles, ask the tester to help evaluate the prototype. For projects that use an incremental life cycle, the tester can test the function as early as possible if there is a part available for testing. In agile projects, ensure that testers work with developers to conduct technical tests. At the same time, testers should work with product owners to compile customer-level tests.