Review the Garage Apartment Project case [ The Garage Apartment Project covers building a two-car garage with an apartment/office on the second floor on your existing lot in accordance with applicable building codes. Use the Project Charter Template [ to define the purpose, justification, assumptions, constraints, milestone schedule and budget, risks, and deliverables for the project (assignment requirements are below). Use the information in the case to frame the project. Assignment Requirements The assignment should be completed in M3 Word using the Project Charter Template [#'. Complete all the sections to represent the charter for the Garage Apartment Projact. 1. Write a comprehensive and understandable statement of the overall project justification and description. 2. State-specific management objectives for the project in scope, time, cost, quality, and risk. 3. Develop a description of known assumptions. 4. Develop a description of known constraints. 5. Specify an expectad completion time and high-level budget. 6. Specify the primary external stakeholder roles/responsibilities. EXECUTIVE SUMMARY The executive summary should be a high-level summary of what issues or problems the project wae 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(z) of the charter. PROJECT PURPOSE/JUSTIFICATION 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. Business Need/Case Discuss the logic for the Business Need/Case (market demand, organizational need, customer request, technological advance, legal requirement, ecological impacts, social need, etc.). This section should also include the intended effects of the business case (Le., cost savings, process improvement, new product development, ete.). Business Objectives This section should list the Business Objectives for the project which should support the organizational strategic plan. PROJECT DESCRIPTION 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. As the project moves forward the details will be developed, but for the project charter, high-level information is what should be provided. Project Objectives and Success Criteria Objectives should be SMART: Specific, Measurable, Aftainable, Realistic, and Time-bound. The project manager must be able to track these objectives in order to determine if the project is on the path to success. Vague, confusing, and unrealistic objectives make it difficult to measure progress and success. Requirements The project team should develop a list of all high-level project requirements. These requirements are clear puidelines within which the project must conform and may be a result of input from the project sponsor, customer, stakeholders. or the project team. Constraints Constraints are restrictions or limitations that the project manager must deal with pertaining to people, money, time, or equipment. It 1s the project manager's role to balance these constraints with availzble resources in order to ensure project success. Assumptions The project team must identify the assumptions they will be working under as the project goes forward. These assumptions are what the project manager/team expects to have or be made available without anyone specifically stating so. Preliminary Scope Statement The preliminary scope statement 15 a general paragraph which hllj_hm'ihts what the project will include, any high-level resource or requirement descriptions, what will constitute completion of the project. This prelimmary scope statement 15 exactly that: preliminary. All o rmation will be expanded upon in greater detail as the project moves forward and undergoes progressive elaboration. Risks All projects have some form of risk attached. This section should provide a list of high-level rigks that the project team has determined apply to this project. 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. SUMMARY MILESTONE SCHEDULE 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. SUMMARY BUDGET 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. PROJECT APPROVAL REQUIREMENTS 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. PROJECT MANAGER This section explicitly states who is assigned as the PM, their responsibility, and authority level. Depending on the organization and scope of the project, the project manager may have varying levels of responsibility and authority for personnel, project expenditures, and scheduling