Those small mistake often made by the project planning process:
1. Because of the small amount of work or simple but not into the project plan
2. misjudged the availability of resources
3. workload to plan projects without taking into account the duration
4. No consideration dependencies
5 The resource does not heal
I have said previously the project management process is the most important thing is the management of change, related concepts I have mentioned in this article: What [project management] Project Management tube? Change tube
change is bound to happen, did not do change management, we do not know what is meant by re-planning (re-plan) that your chances of project failure is certainly up to ninety percent, but today we talk about change management, today to talk about the project planning a small common mistakes, but these small errors can greatly affect your project forward, the same can not be imprudent.
Or simply because of the small amount of work into the project plan and did
some work items because a small amount of work, such as 10 minutes or half an hour to complete, in a very small proportion of the overall project, even compared with other work items are insignificant, this kind of work could easily be that "someone will remember the process", or "incorporated into a work item in the implementation of" good, but because the project is not described in this little work, there is no clear allocation of the work carried out and by whom this Therefore, when ignored, to the project if found to have problems, found early will find someone as soon as possible to deal with, could be found only after late to remedy the problem, the cost is very high at this time of heavy industry.
It is recommended that, no matter how small the work item, if need be executed, then please hang them into appropriate work packages, so your project is a complete plan.
Misjudged resource availability
When the project needs to reference external resources (including cross-sectoral manpower, assets belonging to non-project) when, but you do not clear before booking at the resources on the first written project plan, as soon as possible to confirm or not after they wrote a project plan the availability of the resource, but the time is coming when, etc. to booking, at this time you would have to assume a lot of risk. The most common situation is that the project has a special work needs to be professional practitioners, such as contract review, writing financial reports, patent examination, but these people in the company are usually many routine tasks to deal with, if you do not early booking their time, when possible no one will bother you; for part of the assets, you may need a versatile video conference room to landmark report sponsor, and such a company-wide meeting room and only one, you no booking as soon as possible down easily by other people snatched priority, you certainly forced milestone report postponed. If this happens to work in the critical path or critical path of the intersection, then you definitely a head two big.
On this point I have two suggestions:
1. As far as the resources of the project can be confirmed as soon as possible as quickly as possible down to
2. If this is not related to the use of external resources predecessor, that is, without waiting for the other to complete tasks carried out, then as soon as possible, in order to avoid any accident
at work to plan the project without considering the duration of
the work item is an item then one, but there may be a waiting time between work items and work item, for example, to build a house irrigation mud time may be two days, but if you want to continue to wait for cement works must be frozen in order to carry out, while cement generally may take about five days before solidification, if ran into rain, may have to wait two days , then cementing the duration of the work item should be seven days, but the workload is two days, and followed the work item should be expanded in seven days, instead of 2 days, but many people in the planning of the project often because lack of experience while ignoring this matter.
My suggestion for this is very simple, project management should work on each of the propertiesThere are more understanding, clearly distinguish the differences in workload during the work, so that it can plan a reasonable project plan.
Without considering dependencies
so-called dependency relationships do first is A do B, if the order is to be mandatory norms, called the forced dependency, if it is based on rules of thumb A good think to do first, who is called preference dependencies. Have a dependency different degrees (most probably prefer dependent) on a number of working principles of the project, and therefore we can smooth discharge of our project plan, decide what priority is implemented, which is scheduled for the end of the project, but we also often see the PM's lack of experience in comparative lack of job dependencies concept, and therefore often do half only to find the wrong order, was quickly put to work moving forward, this move may have little effect, but also It may indeed affect the whole body, causing the entire project needs to re-planning.
If you project to an industry or field is very strange, then you can ask more in the planning of relevant experts, and health status process should always check the items in the project, and for more discussion of the work down , confirming everyone down to do where there is no jammed, so you can arrange for a project not carried out proper place as soon as possible.
Resources not heal
concept of resources to heal can refer to this: [project management] how to expand the WBS, schedule-term planning and resources?
If each member of the project work independent of each other, there will be two people in charge of a work, that in principle the use of project resources is relatively simple, but if your project has many work items are jointly responsible for more than 2 people or a person on the same day will put more work items, make sure that you pay attention to the usage of resources when planning the following diagram, if a member of our plan one day to work eight hours, eight hours of work amount equivalent to 100% of his taking up human resources to work on behalf of more than excessive, less than 100% represents the resources are not fully utilized, neither of which it is a normal phenomenon (in fact, eight hours a day is not a good basis points ), we must be as rational use of human resources project, I have seen many examples do not heal after finished planning, you will find some people in the workload of up to 300% on some days, but in some no work day is done, it will not matter carried out early in the project, but with the outbreak of the project will gradually come out.
My advice is to get everyone off the daily workload between 85-100%, why is it 85%? There are two reasons, one, I believe that a day can not continue to focus on eight hours, people must set aside some time to rest, the other, there will always be changes in the project, which can be used as a response when the project change margin, I think without overtime situation, a focus 6-6.5 hours a day has been considered very good.
The above points are the initial project planning very easy mistake to make, project management available to you as a reference, if you plan to think about some of the project started to observe the health of the project and make change management, I believe that the management of the case will be able to successfully closed.
 |
Shu tour sail (gipi) Exploring Force Co-founder, former TutorABC associate director of computer and took the lead, and won the election two-time Microsoft Most Valuable Professional (MVP), founded after leaving the workplace to explore the Force, dedicated to helping young people develop the ability to face the future. Yucai fact that education is closely related with the organization, are in the reserve energy for the future, since 2018, established a one-year special courses "career jump of 24 key lesson" for the training of future leaders of China Taiwan and work. |
Original: Large column [project management] project planning process often make those little mistakes