Don't take milestones as stones---------Project planning of IT project management

If there is no plan to do the project, I am afraid no one will agree. Does every project plan play a role? But not really. Know how to plan, but do not know why to plan, how to plan is still a few. So many plans become leaf out, become a decoration.

The purpose of the IT project plan is very clear. Because we cannot know in advance what the system will ultimately look like, whether it is consistent with the user's imagination, and whether the needs of the user match, we need to pass a plan, from the requirements, to the design, to the final test. Every step forward, make sure to no longer rework back to the previous stage. If a plan does not work as it should, the project will be in a circle. And this is by no means a genius of the system can be solved. Because no one knows exactly what it looks like before it is finished, we have to use some imagination. Even if there are prototypes or models, it is just a glimpse of the whole picture. And the imagination of the masses is limitless.

In fact, the Apple that Steve Jobs gave people is not what people think they want, and it's not something that's beyond your imagination. He was given a carrier, a window. Through it to find their own imagined things. So as to meet the diverse needs of people. IT systems also exist such a system, that is, tool-level things, whatever you do, but do not ask. For a system that is specific to a particular requirement, all we have to do is find a direction that is generally applicable, and then go in that direction together, and either tease the circle or make it less fun.

Once there was a project, and every project review, there was a bunch of problems. Many questions are unclear about how long it will take to solve the problem. There are also problems, solutions, and implementation plans. However, when asked about the impact on the overall project progress, the project manager confidently said "no impact". Once two times also forget, later clearly a task postponed outrageous, how also said does not affect the project on the floss? Having the project manager present the milestone plan reveals that the problematic tasks are not related to the milestone nodes (so-called not on the critical path), so that they are deferred to the next stage, post-stage, or not adjusted for milestone planning.

---that really needs to be pushed to the point after the online time? Is there such a thing?

---there!

---how does that affect the project on-line?

---put it on the line to perfect the stage.

I have been doing it project for more than 10 years, I did not understand the time, after-line perfect is what thing. Only after the on-line support, where again out of the line after the perfect it?

It was later understood that the project plan, in addition to the milestone time node unchanged, the others are changing. What can not be completed by the time of the task, are postponed, postponed, and so on down the line node is also unable to keep, on-line after the perfect.

Understand, there is a kind of urge to curse. Is this a project? Isn't that the foot on the watermelon skin? The whole one does not take the milestone (milestone) as stone. When it does not exist, transparent, all through. Finally, the network structure diagram of the task node is in the pipeline project progress, without the concept of the project stage.

Perhaps for the comfort of the heart, because the task has been postponed, the project manager will be able to arrange the early things in advance to do. The problem is that many things do not have a clear account on the milestone node, and those things that are done early are likely to be redone.　For example, if the development is not finished, we will arrange some users to do pilot operation. If the development is completed, some places have been adjusted, then pilot small units were sacrificed, into the pioneer pioneer.

As for the so-called on-line after the perfect thing is endless. Wait until the project is ribbon-cutting, set off firecrackers to celebrate the success of the online, who will also control the improvement of imperfect things. Worse than that, the "perfect" ended up as an endless career. That's not going to be called a project.

In fact, the project milestone node means the quality gate. In some cases, it is true that concessions are released. But the time and content of concessions have a bottom line. The bottom line is, I can not let go of the release of things. To the general acceptance of the time, the determination can not be perfected, also recognized. Without this consensus, no concession can be allowed.

It projects are in fact from coarse to thin design, from thin to coarse execution. When making a plan, make a milestone plan and clear the big stage goal. As long as the detailed plan to achieve the current stage, so-called "progressive details." Don't rush to think about what you're going to do on your last day. But be sure to know the goal of the last phase from day one.

Wait until the plan is executed from thin to thick. At the most detailed level of operation, you need to feed back to the top of the milestone plan to determine if milestones need to be adjusted. In the above case, it is often a matter of a specific plan, such as the data migration when the project is on-line (usually refers to unfinished business operations, such as a purchase order not closed) plan. But this is an isolated task plan, and the relationship with the milestone plan is completely ignored. As a project, because of its uniqueness, it is very necessary to assign the networked task relationship to each major stage, and then proceed to the "forward or backward" assessment on the milestone node. Milestones are the real cornerstone of the project process, and you can move forward and not look back.

Don't take milestones as Stones---------Project planning for IT Project management (RPM)