Let's talk about our project plan.

everything in the world begins with a plan. The success of one thing must also have a comprehensive plan. To achieve great success, we need to set different milestones to achieve the ultimate goal. To do a good job, we also need to know when to do what to do. A plan is always bound to a task. It is a prelude to the beginning of the implementation cycle of the entire task. Without good strategizing, you cannot have a good start. Of course, you don't have to think about a successful ending. The same applies to a software project. In the early stage of the project, we should formulate a plan, establish a project, draft a construction scheme, analyze and discuss the feasibility, participate in bidding, and win the bidding; after the project is awarded and the contract is signed, it is actually the start of the project. What we need to do is to appoint a project manager, set up a project team, set up a project management committee, and draft a project implementation outline, A bunch of tedious things come one after another, such as making software development cycles, allocating resources, and adjusting the progress. In the face of such a messy project cycle, I would like to explain how to ensure the final successful delivery of the project without a good plan.
the projects I mentioned below are all based on common software projects. Since I have been engaged in this line of work, I have to have the right to publish this line of software. The project plan I want to talk about here is also limited to the software development process we are familiar with. The scope is too large, so there is no time, and I am worried that there are too many theme-less topics. If it is better, I will start here.
the software development process we recognize mainly involves analysis, design, Code writing, testing, trial run, and delivery to customer acceptance.. So these steps are actually milestones in our project plan. Ideally, these milestones require comprehensive review and notification of customers. The reason why I say this is the ideal state is that such a process exists in the scope of the actual project implementation process or, more certainly, it is basically impossible to exist. Because a plan is only an ideal state in advance, once it is put into practice, the plan will always be subject to too much resistance and uncertain interference, in this case, the most basic task is to calculate the time and cost. The problem arises here. We need to make a plan and make the requirements conform to the actual situation, and how to make the plan becomes the most important issue, this will return to the center of this article (isn't it enough to bypass, O (∩ _ ∩) o... haha ).

 

First, let's talk about when to start planning.
The project plan is generally started after the contract is signed and the Project Manager is appointed. Only when the contract is signed can we know the development cycle of the project accurately, exclude holidays and break time for daily work, and finally obtain the real time amount for project development. In the true sense, it may also be an ideal state, because we have not considered the time for risk occupation, such as power outages, Project changes, unexpected project members, and resignation. Of course, there may also be more extreme periods of time, such as earthquakes, weather, social unrest, 2012 (O (∩ _ ∩) O... haha) and so on. The project time point must be determined by the Project Manager, because only when the project time period is well calculated can the corresponding steps be effectively allocated within working days, only when time points are set for each step can the task volume, task scope, expected goal, and execution resource of each step be clearly defined.

 

Second, let's talk about how to plan
The effective construction period is clearly defined and the work objectives of each stage are set up, and the main framework of the Project Plan is basically completed. What we need to do next is to refine the workload, time progress, Task Difficulty, time matching, and establishment of task execution personnel based on milestones in various stages. At the same time, we will further indicate what is done every week in the plan, what is done every day, what is done by James today, and what should James do tomorrow. In this way, the task confirmation in the smallest unit of day basically completes the planning. Of course, if you have a more intelligent head, you can go deep into the afternoon, hour, minute ....

Third, let's talk about planning risk prediction and control.
As we mentioned above, the validity period of the planned project needs to consider its uncertainties. Similarly, the completion of a plan also requires the prediction and control of the Plan risks. When you finish the plan, have you ever asked yourself that my plan is actually ready? What are the risks of the plan? What if Wang Wu is ill today? What if Xiaoqiang leaves tomorrow? Suppose that Wei is out of love the day after tomorrow. What should I do? These are your risks, but not all of them. The aforementioned power outages and the force majeure are all part of the scope of planned risks. The risks of the plan are unpredictable. How to effectively control the plan? Here I propose three solutions: first, we should respect the facts more objectively when formulating the plan and try to deviate from the actual situation as little as possible; second, reserve as much time as possible for temporary scheduling and matching. Third, when planning a is completed, create a Plan B. Once a Large-Scale Delay plan is found or will be discovered, immediately adjust the remedy.

Fourth, let's discuss how to implement the plan.
A plan is always handed over to people for execution. If there is no executable object, it is a piece of waste paper. The same plan is also reflected by the participants in the implementation process. Therefore, the effective implementation of the plan cannot be separated from the performer's participation. This requires that we should arrange enough time to communicate closely with the plan participants after the preparation of the plan or plan is completed, do you know if they can complete the schedule within the scheduled time? Is there any delay resistance? Do you need effective adjustments? In many cases, people who plan are always walking based on their own ideas and ideas, and do not impose their wishful thinking on others, do not always tell your executors that they can do this without working overtime. This is very violent.

After talking so much, I don't know if I have any feelings or help for you. In a word, the plan is not to waste, to make a mess, but to make a person or a person (humanized ).

(Note: All articles are original articles. for reprinting, please indicate the source! 20100614 is written in Shenzhen .)