Using the attached Case Study follow the below guidelines to complete the attached Template

A.  Write a problem statement that defines the purpose of the requested project for the chosen case study in the “Problem Statement” section of the “Project Proposal Template” attachment. The problem statement needs to include the project’s difficulty, the current business process, possible system changes, and the consequences of not completing the project.

 The problem statement defines the purpose of the requested project for the chosen case study and contains all of the following: the project’s difficulty, the current business process, possible system changes, and the consequences of not completing the project. 

B.  Write a scope statement that includes a make-or-buy analysis, a recommended solution, and a high-level overview of the expected work to complete the project for the chosen case study in the “Scope Statement” section of the “Project Proposal Template” attachment.

 The scope statement includes a make-or-buy analysis, a recommended solution, and a high-level description of the work tasks. 

C.  Explain how three criteria for project success will be met for the chosen case study in the “Project Success Criteria” section of the “Project Proposal Template” attachment.

 The explanation includes 3 success criteria and includes how each provided success criterion will be achieved, and all of the provided success criteria are accurately based on the chosen case study. 

D.  Create a work-breakdown structure (WBS) for the chosen case study by completing the table in the “Work Breakdown Structure (WBS)” section of the “Project Proposal Template” attachment. The WBS needs to include logical human resource requirements, measurable project deliverables, and a minimum of 25 subtasks across a minimum of 4 work tasks.

 The WBS for the chosen case study includes logical human resource requirements, measurable project deliverables, and a minimum of 25 subtasks across a minimum of 4 work tasks. 

E.  Justify the use of five tools and techniques from two or more Project Management Body of Knowledge (PMBOK) knowledge areas that will be used to manage the project for the chosen case study. Enter this information in the “Tools & Techniques” section of the “Project Proposal Template” attachment.

 The justification of the use of all 5 tools and techniques is based on the chosen case study, and the tools and techniques are from 2 or more PMBOK knowledge areas. 

F.  Acknowledge sources, using in-text citations and references, for content that is quoted, paraphrased, or summarized.

 The submission includes in-text citations for sources that are properly quoted, paraphrased, or summarized and a reference list that accurately identifies the author, date, title, and source location as available. 

G.  Demonstrate professional communication in the content and presentation of your submission.

 Content reflects attention to detail, is organized, and focuses on the main ideas as prescribed in the task or chosen by the candidate. Terminology is pertinent, is used correctly, and effectively conveys the intended meaning. Mechanics, usage, and grammar promote accurate interpretation and understanding.