Product Operations Program ManagerBarcelona, Cataluña, Spain
Typically a Project Charter is used for that purpose, along with a stakeholder register. Saving Changes...
Kenneth MyersPresident| Blue Falcon CobraOakton, Va, United States
I've used a project initiation document when a full project charter was not needed. It contained the tailored elements of a project charter and a stakeholder register similar to what Eduard mentioned in his post.
My initiation document was what I used to gain approval from the project owner and contained at a minimum the project purpose or justification, expected outcome including objectives and success criteria (measurable), project key personnel, assumptions, bugdet (if other than resource cost), and stakeholders. Projects of all sizes should have something like this to document the intent of the project and act as a baseline to document any changes to the scope.
...
2 replies by Chandrashekhar Thatte and Kenneth Myers
Feb 07, 2017 1:36 AM
Chandrashekhar Thatte
...
Kenneth,thanks for sharing.How did the project performance meet the expected outcome including objectives and success criteria (measurable) ?Please elaborate ...
Mar 01, 2017 2:28 PM
Kenneth Myers
...
Project come in all shapes and sizes. I just used one to write a white paper on an analysis of alternatives for a new tech integration.
I documented the expected outcomes and reviewed it with the project champions to make sure I captured their expectations. Once I knew there success criteria, I was able to plan the section of the paper (WBS) and estimate level of effort in writing each part. This included research, analysis, writing, and review periods. The success criteria was to review at least three potential integration products against alignment metrics. How well the product aligned with business objectives, budgetary constraints, technical integration, and operations and maintenance. All of those were given a quantitative assessment on a scale from 1 - 10 to arrive at a final value or recommended product. The paper had a 45 day window so I scheduled my deliverable from that day with a critical path based on section drafts. We were able to stick to the schedule and deliver a final paper that met the criteria although not the recommendation we had anticipated (different product based on business alignment).
I've used a project initiation document when a full project charter was not needed. It contained the tailored elements of a project charter and a stakeholder register similar to what Eduard mentioned in his post.
My initiation document was what I used to gain approval from the project owner and contained at a minimum the project purpose or justification, expected outcome including objectives and success criteria (measurable), project key personnel, assumptions, bugdet (if other than resource cost), and stakeholders. Projects of all sizes should have something like this to document the intent of the project and act as a baseline to document any changes to the scope.
Kenneth,thanks for sharing.How did the project performance meet the expected outcome including objectives and success criteria (measurable) ?Please elaborate ... Saving Changes...
Maria, it was really educative !Many thanks ! Saving Changes...
Kenneth MyersPresident| Blue Falcon CobraOakton, Va, United States
Feb 03, 2017 11:38 AM
Replying to Kenneth Myers
...
I've used a project initiation document when a full project charter was not needed. It contained the tailored elements of a project charter and a stakeholder register similar to what Eduard mentioned in his post.
My initiation document was what I used to gain approval from the project owner and contained at a minimum the project purpose or justification, expected outcome including objectives and success criteria (measurable), project key personnel, assumptions, bugdet (if other than resource cost), and stakeholders. Projects of all sizes should have something like this to document the intent of the project and act as a baseline to document any changes to the scope.
Project come in all shapes and sizes. I just used one to write a white paper on an analysis of alternatives for a new tech integration.
I documented the expected outcomes and reviewed it with the project champions to make sure I captured their expectations. Once I knew there success criteria, I was able to plan the section of the paper (WBS) and estimate level of effort in writing each part. This included research, analysis, writing, and review periods. The success criteria was to review at least three potential integration products against alignment metrics. How well the product aligned with business objectives, budgetary constraints, technical integration, and operations and maintenance. All of those were given a quantitative assessment on a scale from 1 - 10 to arrive at a final value or recommended product. The paper had a 45 day window so I scheduled my deliverable from that day with a critical path based on section drafts. We were able to stick to the schedule and deliver a final paper that met the criteria although not the recommendation we had anticipated (different product based on business alignment). Saving Changes...
Yes, plenty of these type of documents used for various purposes for a project, procurement, steering committee etc. What is the required deliverable, process document or PMO template? It's usually a project charter but it be another similar type document like many have stated here. Saving Changes...
Community Champion
