I'm curious, does anyone still use a Project Management Plan; not to be confused with a project schedule/timeline but a plan that consists of areas like how risk, change, etc. will be managed? If you do, under what conditions? Saving Changes...
Whether or not there is some type of collector plan that points to things like how schedule, staffing, change management, etc. will be performed depends on the project and organizational governance.
If you have stable processes and tools, that's often not necessary. Schedule management is just business as usual on the program. If there are new or significantly changed processes, then that needs to be documented somewhere.
On large complex projects, there may be a requirement to document all the component plans. In some domains this may be part of a Systems Engineering Management Plan (SEMP) that describes both how the product will be developed, and how the project will be managed.
...
1 reply by Greg Bickford
Mar 19, 2021 1:22 PM
Greg Bickford
...
Thanks for the response Keith, this makes perfect and could not agree more on your 'depends' comment. I use that more often than I would care but...in my experience there is no one size fits all so in many cases it really just depends.
Saving Changes...
Peter RapinSubject Matter Expect; Project Delivery| Independent ConsultantOntario, Canada
A project can be delivered with or without a Plan - its a matter of risk and benefit.
Much the same as a travel plan. If you are going to grandma's house you typically don't need a formal travel plan as even the car knows how to get there in the most effective way. However, if you are going across country or internationally with much complexity and passage of time, a travel plan may mitigate any risks of not getting there and/or enhance the experience of the trip.
When considering the pros and cons of a plan ask yourself "what could go wrong with or without and how such a plan, and all its elements, may lead to enhanced benefits". A plan must be based on real value not just process. Saving Changes...
James PorterSr. Project Planner| Hitachi Rail STS USAGlenshaw, Pa, United States
We have a Project Management Plan, required by the company. It is generally a high-level document (it is brief but it points to many other subsidiary project plan docs) but it explicitly details the company process documents we will follow such as software dev processes, quality processes, etc. This shows the project team is aware of and will honor the other processes we are required to follow.
...
1 reply by Greg Bickford
Mar 19, 2021 1:30 PM
Greg Bickford
...
Hello James & PA neighbor. Thanks for the reply. I am new to my current org. and they too require the use of a PM Plan.
My inquiry on this board was to gauge how often, under what conditions, and the level/complexity of content of a PM Plan; I've received a lot of very good feedback, yours included.
In my experience there are still org.'s that do not require or conditionally use a PM Plan (i.e. a structured PM Plan template that I am sure I could find on this site) but rather a Project Charter (not a 'plan' I acknowledge) and then a host of other documents to guide the project.
Whether or not there is some type of collector plan that points to things like how schedule, staffing, change management, etc. will be performed depends on the project and organizational governance.
If you have stable processes and tools, that's often not necessary. Schedule management is just business as usual on the program. If there are new or significantly changed processes, then that needs to be documented somewhere.
On large complex projects, there may be a requirement to document all the component plans. In some domains this may be part of a Systems Engineering Management Plan (SEMP) that describes both how the product will be developed, and how the project will be managed.
Thanks for the response Keith, this makes perfect and could not agree more on your 'depends' comment. I use that more often than I would care but...in my experience there is no one size fits all so in many cases it really just depends. Saving Changes...
We have a Project Management Plan, required by the company. It is generally a high-level document (it is brief but it points to many other subsidiary project plan docs) but it explicitly details the company process documents we will follow such as software dev processes, quality processes, etc. This shows the project team is aware of and will honor the other processes we are required to follow.
Hello James & PA neighbor. Thanks for the reply. I am new to my current org. and they too require the use of a PM Plan.
My inquiry on this board was to gauge how often, under what conditions, and the level/complexity of content of a PM Plan; I've received a lot of very good feedback, yours included.
In my experience there are still org.'s that do not require or conditionally use a PM Plan (i.e. a structured PM Plan template that I am sure I could find on this site) but rather a Project Charter (not a 'plan' I acknowledge) and then a host of other documents to guide the project. Saving Changes...
