Make a project charter about mobile application store

V. II. Executive Summary The executive summary should be a high-level summary of what issues or problems the project was created to correct. Typically, the executive summary also provides the background information and general statements regarding the project's purpose or justification which will be covered in more detail in the appropriate section(s) of the charter. Project Deliverables This section should list all of the deliverables that the customer, project sponsor, or stakeholders require upon the successful completion of the project. Every effort must be made to ensure this list includes all deliverables and project sponsor approval must be required for adding additional deliverables in order to avoid scope creep. VI. High Level Milestones This section provides an estimated schedule of all high-level project milestones. It is understood that this is an estimate and will surely change as the project moves forward and the tasks and milestones and their associated requirements are more clearly defined II. Project Purpose A. Background This section describes the purpose and justification of the project in the form of business case and objectives. The business case should provide the reasoning behind the need for this project as it relates to a function of the business. B. Business Need This section describes the purpose and justification of the project in the form of business case and objectives. The business case should provide the reasoning behind the need for this project as it relates to a function of the business. C. Business Objectives This section describes the purpose and justification of the project in the form of business case and objectives. The business case should provide the reasoning behind the need for this project as it relates to a function of the business VII. Cost Components The summary budget should contain general cost components and their planned costs. As the project moves forward these costs may change as all tasks and requirements become clearer. Any changes must be communicated by the project manager. VIII. Project Organization A. Table of Organization B. Roles and Responsibilities III. Project Description A. Project Objectives This section provides a high-level description of the project. This description should not contain too much detail but should provide general information about what the project is, how it will be done, and what it is intended to accomplish. Also, the organization must understand when the project has reached a successful completion. These criteria must be clear and should be accepted by whoever will sign-off on the project's closeout. Once signed-off by the authorized person, the project is deemed approved and is successful as long as it has met all of the agreed upon requirements B. Requirements c. Constraints D. Assumptions E. In Scope F. Out of Scope IV. Risks All projects have some form of risk attached. This section should provide a list of high-level risks that the project team has determined apply to this project