Project plan documents do not have to be long. Often, a 1 to 2 page document is more than sufficient for small project and that small size also encourages people to actually read the project plan and identify the things they agree with and the things they don’t like. Getting perfect agreement on the project plan the first time people see it is not particularly desirable. It may indicate the plan does not surface the issues and disagreements people have about what the project would produce. We definitely want to uncover those issues before we start work and get them resolved. That is far superior to having these disputes about the projects goals and directions come up in the middle of the work effort. Main Project Planning Page
A good project plan details how we will finish on time and deliver the scope as defined, which gives us a happy sponsor or client. Creating a good plan is a complex and political task. Follow these steps to craft a solid plan for your next project. First, you define the scope with the sponsor as a deliverable that you can measure with a metric. With that metric we have a solid foundation for the project plan. It is the key to working top down from a measurable project scope, and then breaking that down into the project’s major deliverables, which are also defined with metrics. You must define each deliverable so you can measure the result and so the team member who has to produce it knows what is expected before they start work. That network of deliverables that leads to the scope is the backbone of the other components of the project plan. We use it to create our work breakdown structure (WBS), make estimates for each of the deliverables and then assign people to them as we build a schedule.
You learn all of those skills in our project management basics courses. Take a look at the basics course in your specialty.IT Projects Business Construction Healthcare Client Projects