The Project Management Office
Project Plan Template
The Project Management Plan is central to PMBOK project management. We suggest you start with this template then use subsidiary management plans to further build out your project plan.Go to Template...
Templates Organized by Process Group
Project Charter Template
Every successful project starts with a good Project Charter. We have two Project Charter templates available, a short one page version and a longer more comprehensive version.Go to Template...
In this week’s blog we have compiled a list of what we believe are the Project Management Body of Knowledge’s (PMBOK) seven most critical project management templates. Each of these templates represents an important part of an effective and integrated project plan.
- Project Charter – The project charter can be considered the foundation of a project. A completed and signed project charter establishes the authority to begin a project to address a business need that has been identified. Great care and detail should go into the creation of a charter because of its importance. If you sacrifice quality with the project charter, your project performance and deliverables will almost surely suffer. Click Here to Download Our Project Charter Template.
- Project Management Plan - If the project charter is the foundation of a project, the project management plan is its core. The project management plan is important because it is an integrated framework which includes the management plans from all of the project management knowledge areas. It ties these management plans together into a collective whole which is then used to manage the project through to completion. Click Here to Download Our Project Management Plan Template.
One of the best ways to learn is by doing. This applies not only to everyday life, but also to project communications management. This step-by-step guide is meant to be used in conjunction with our Communications Management Plan Template. By following the steps outlined below, and using our communications management plan template you'll find that developing the communications management plan for your project is quite easy and can be accomplished with little stress.
Step 1 Review the PMBOK
Read through section 10.2.3.1 of the PMBOK (Communications Management Plan). Either print this section or make a copy and keep it on your desk - this way you can refer back to it often. The PMBOK is the industry standard for project management and is extremely useful in detailing the requirements for project communication as well as other project areas. A thorough review of the applicable PMBOK section should precede work on any project management process area.
It’s a question that comes up often, and doesn’t seem to have a clear answer. Is a project plan simply an MS Project schedule? Is it a summary document of just a few pages? Or a more in-depth and detailed document containing specifics of every aspect of the project?
As you might imagine, it’s tough to write one if you don’t know exactly what’s expected.
Project Plan Basics
At its most basic level, a project plan – or Project Management Plan, as the Project Management Body of Knowledge (PMBOK) calls it – is simply a guide for how the project will be managed. Think of it as the project manager’s rulebook. It provides a structure for handling things like changes to the project, communication methods and requirements, and approval processes. It also provides a baseline for the project including cost, scope, and schedule.
The Risk assessment meeting is an important part of any project. Projects are launched to take advantage of opportunities and with these opportunities come uncertainty and risk. The project risk management plan addresses the process behind risk management and the risk assessment meeting allows the project team to identify, categorize, prioritize, and mitigate or avoid these risks ahead of time. The team uses this meeting to determine the probability and impact of each risk, determine if the risk can/should be avoided by making changes to the project, plan an appropriate response, and catalog risks and responses in the Risk Register.
The risk assessment meeting should be a formal meeting conducted during the project’s planning process. It is imperative that the project manager sends a meeting invitation and agenda to all attendees well ahead of time. This allows the meeting participants time to review what will be discussed and note any risks they may have already identified. At a minimum, the following should be invited to the risk assessment meeting:
As PMO managers we have seen many variations of Work Breakdown Structures (WBS). At one extreme, project managers create their WBS at two or three levels with loosely defined work packages including only a title and an estimate of the number of hours. At the other extreme, project managers create their WBS with levels taller than the empire state building, WBS Dictionaries which go into almost infinite detail, and work packages of just a few hours each. While these extremes may not be necessary, the WBS should be created with enough detail to serve as a useful tool in managing the project’s tasks. A Work Breakdown Structure (WBS) is a valuable tool for organizing a project by breaking it down into more manageable component parts based on the deliverables required to complete the project. It is the accepted project management document for tying the project scope, cost, and schedule together. There are many ways to configure the WBS, but within an organization, it is important to standardize the way it is formatted across the entire portfolio of projects. Just as with processes, tools, and methodologies, standardizing the WBS format is an important part of providing repeatability and consistency.