We need to come up with a project and present a PPT in 2 slides according to the project charter
The Food Club, India authorizes a project to design a wellness program to reduce employee turnover, and increase engagement focusing on the employee’s healthy lifestyle and the sustainability of the company. Less employee turnover Motivation to stay for longer and loyal to organization Increasing job satisfaction and more engagement Improve bonding with management and co-workers (less conflicts) Maximise work productivity and minimize the absence of the workers Improve health of employees by health benefits accordingly organization healthcare cost will be reduce Managing chronic diseases in the workplace Attractive work culture and enhance corporate image
Need 2 slides on
1. High-Level Requirements
2. High-level Project Boundaries and Key Deliverables
|<Project Name>||Revision: <6.0>|
|Project Charter||Date: 23 July, 2021|
|Document Code: PMBOK184.108.40.206|
Document Code: PMBOK220.127.116.11
CEO of <Organization Name>
<Name and authority of the sponsor or other person(s) authorizing the Project Charter>
<This section briefly describes the purpose of the project and its justification. The justification describes the necessary information from a business standpoint to determine whether or not the project is worth the required investment. Justification describes one or more of the following factors:
· Market demand (e.g., a car company authorizing a project to build more fuel-efficient cars in response to gasoline shortages)
· Organizational need (e.g., a training company authorizing a project to create a new course to increase its revenues)
· Customer request (e.g., an electric utility authorizing a project to build a new substation to serve a new industrial park)
· Technological advance (e.g., an electronics firm authorizing a new project to develop a faster, cheaper and smaller laptop after advances in computer memory and electronics technology)
· Legal requirement (e.g., a paint manufacturer authorizing a project to establish guidelines for handling toxic materials)
· Ecological impacts (e.g., a company authorizing a project to lessen its environmental impact)
· Social need (e.g., a nongovernmental organization in a developing country authorizing a project to provide potable water systems, latrines and sanitation education to communities suffering from high rates of cholera).
These factors may also be called incentives, opportunities or business requirements. The basic point of all these factors is that management should decide what the response should be to them, and what projects should be authorized and fixed in the Charter.>
<This section describes the measurable project objectives and related success criteria:
· Objective is something toward which work is to be directed, a strategic position to be attained, a purpose to be achieved, a result to be obtained, a product to be produced or a service to be performed.
· Criteria are the standards, rules or tests on which a judgment or decision can be based or by which a product, service, result or process can be evaluated.>
<This section documents the requirements that satisfy the needs, wishes and expectations of the Customer, Sponsor and other project participants. Requirements are the certain conditions or capabilities that must be met or possessed by a system, product, service, result or component to satisfy a contract, standards, specifications or other formally imposed documents.
Requirements include the quantified and documented needs, wants and expectations of the Sponsor, Customer and other stakeholders of the project. In the phase of the Project Charter development, the requirements are usually less concrete; they becomes more concrete during the subsequent processes according to the gradual elaboration of the project.
Please note that the Project Charter contains high-level requirements only. The complete list of requirements should be presented in the Requirements Traceability Matrix.>
<This section provides a general description of the products or services that the project is supposed to produce; there is a brief description of the business need, a very general description of the product and an initial strategic plan.>
<This section describes the high-level risks and also provides a brief description of the project risk management implementation and the risk tolerance levels of the project Sponsor and Customer.
Please note that the Project Charter contains high-level risks only. The complete list of risks should be presented in the Risk Register.>
<This section contains an aggregate schedule of works showing the dates of the main milestones. The Customer or performing organization can preset the milestones and the required dates of their execution. These dates can be identified as constraints on the terms. Use the following table.
Please note that the Project Charter contains high-level milestones only. The complete list of milestones should be presented in the Milestone List.>
|<Title of the milestone>|
<This section contains formal periodic restrictions on expenditures provided in the project or specified in the Agreement on project implementation.
Please note that the Project Charter contains summary budget only. The itemized budget should be presented in the Cost Baseline.>
<This section contains the list of individuals, groups or organizations who may affect, be affected by or perceive itself to be affected by a decision, activity or outcome of a project.
Please note that only main stakeholders are specified in the Project Charter. The complete list of stakeholders should be presented in the Stakeholder Register.>
|Full Name||Position/Organization||Role in the Project||Telephone/E-mail|
|<Full name of the stakeholder>||<Position of the stakeholder and organization name>||<What kind of work is performed by the stakeholder in the project>||<Key contact information of the stakeholder >|
<This section specifies what constitutes project success, who decides the project is successful and who signs off on the project. This section also identifies the acceptance criteria, including performance requirements and essential conditions that must be satisfied before the acceptance of the project deliverable.>
<This section specifies what conditions need to be met in order to close or to cancel the project or phase (e.g., documented approvals, completed documents, completed deliverables).>
A Project Manager is identified and assigned as early in the project as is feasible, preferably while the project charter is being developed and always prior to the start of planning. It is recommended that the Project Manager participate in the development of the Project Charter because this document provides him/her with the authority to use the organization assets to complete the project and responsibility for the project objectives achievement.>
<This section contains all appendixes to the document. In the absence of appendixes, this section is excluded.>
<Attention! Fill in the Quick Parts and update the Table of Contents before publishing the document.>