Difference between revisions of "Template:ProjectCharter"
Jump to navigation
Jump to search
(4 intermediate revisions by the same user not shown) | |||
Line 67: | Line 67: | ||
|} | |} | ||
==Understand how to define the SCOPE (project guidelines)== | |||
Business Case <br /> | |||
:Provisional Start & End Dates<br /> | |||
:Business Needs<br /> | |||
Benefit Management<br /> | |||
:Target Benefits<br /> | |||
:Timeframe for Realizing Benefits<br /> | |||
:metrics<br /> | |||
:Identify Risks // (Spreadsheet)<br /> | |||
:Strategic Alignment<br /> | |||
:Benefit Owners<br /> | |||
Assumptions LOG<br /> | |||
:Assumptions register // (Spreadsheet)<br /> | |||
:Constrains register // (Spreadsheet)<br /> | |||
Project Charter<br /> | |||
:Project Purpose<br /> | |||
:Measurable Project Objectives<br /> | |||
:High-Level Requirements <br /> | |||
:Overall Project Risk<br /> | |||
:Summary Milestone Schedule<br /> | |||
:Pre-Approved Financial Resources<br /> | |||
:Key-Stakeholder List // (Spreadsheet) Name, title, organization, influence <br /> | |||
:Client List // (Spreadsheet) Name, title, organization, influence <br /> | |||
:Productr List // (Spreadsheet) Name, title, organization, influence <br /> | |||
:Project Approval requirements <br /> | |||
:Profissional Estimated Budget<br /> | |||
Approval/E-Sign (auth)<br /> | |||
:Assigned Project Manager<br /> | |||
:Assigned Project Owner/ Sponsor<br /> | |||
:History Log<br /> |
Latest revision as of 22:09, 7 July 2022
Projects scope must be described on PKC on the following structure (PKC Project page structure):
- Intro (no title)
- Product Scope
- Project Scope
- History factors (in case it needed or if exists)
- Logic Model (Purpose, Problem-solving or how project differ from others, success criteria; inputs, process, Outputs) There is a template for the logic model in here.
- Define project needs (resources, time, costs)
- Define context (if needed e.g. education - What, How, why, etc... of curriculum or programs)
- Quality issues or boundary conditions
- Stakeholders identification
- Budget
- References
- Related pages
SIMILAR TO PROJECT CHARTER - PROJECT MANAGEMENT (INITIATING STAGE) (Working as a ricardian contract)
This includes the following:
- Define [[{{{Project_name}}}/Context|context]] with historical factors(if needed e.g. education - What, How, why, etc... of curriculum or programs)
- Introduction and [[{{{Project_name}}}/Goal|Goal]]s of the project
- Quality issues ([[{{{Project_name}}}/Criteria|Success criteria]]) and relevant boundary conditions
- Required [[{{{Project_name}}}/Input|Input]]s and Stakeholders identification
- Proposed [[{{{Project_name}}}/Process|Process]] of Execution
- Budget
- Expected [[{{{Project_name}}}/Output|Output]]s/Outcomes
- References
- Related pages
Logic Model (PROJECT CHARTER) Template:ProjectCharter 07 7, 2022 Script error: You must specify a function to call. | ||||||
---|---|---|---|---|---|---|
| ||||||
| ||||||
|
Understand how to define the SCOPE (project guidelines)
Business Case
- Provisional Start & End Dates
- Business Needs
Benefit Management
- Target Benefits
- Timeframe for Realizing Benefits
- metrics
- Identify Risks // (Spreadsheet)
- Strategic Alignment
- Benefit Owners
Assumptions LOG
- Assumptions register // (Spreadsheet)
- Constrains register // (Spreadsheet)
Project Charter
- Project Purpose
- Measurable Project Objectives
- High-Level Requirements
- Overall Project Risk
- Summary Milestone Schedule
- Pre-Approved Financial Resources
- Key-Stakeholder List // (Spreadsheet) Name, title, organization, influence
- Client List // (Spreadsheet) Name, title, organization, influence
- Productr List // (Spreadsheet) Name, title, organization, influence
- Project Approval requirements
- Profissional Estimated Budget
Approval/E-Sign (auth)
- Assigned Project Manager
- Assigned Project Owner/ Sponsor
- History Log