Scenario The project manager for GDS is in the process of developing the Project Scope Statement for the PMO Cloud Implementation Project. You were chosen to assist the project manager in creating the schedule and updating the Project Scope Statement. Your first duty in preparing the schedule is to create the WBS in outline format, identifying activities and tasks to complete the project. After validating the project tasks to develop the WBS in outline format, you will transfer the WBS outline to your Project Management Information System (PMIS) software, Microsoft Project to establish Gantt chart and project milestones. The software tool Microsoft Project will make it easier for the project manager to monitor and control each phase of the project. High- level, tasks for this project include, but not limited to the following: Project Management * Local and Online Configuration Unit and Integrated Testing + Client and Web application training Develop User Manuals * Software Deployment WORK BREAKDOWN STRUCTURE Project Name Project Manager The Decomposition Process: 1. Use a top down approach to identify the major components of work to be accomplished. 2. Break each major component down to an appropriate level of detail. 3. Name each activity task with a verb and a noun to describe the work and the tangible result. Example: Install Hardware Creating an outline will help you with indenting outline levels when you are ready to enter data in Microsoft Project 1. Level 1 1.1. Level 2 1.1.1. Level 3 Level 1 Level 2 Level 3 1 (Project 1.1 Deliverable 1 1.1.1 Task Name) 1.1.2 Task 1.1.3 Task 1.2 Deliverable 2 1.2.1 Task 1.2.2 Task 1.2.3 Task 1.3 Deliverable 3 1.3.1 Task 1.3.2 Task 1.3.3 Task 1.4 Deliverable 4 1.4.1 Task 1.4.2 Task 1.4.3 Task 1.5 Deliverable 5 1.5.1 Task 1.5.2 Task 1.5.3 TaskProject Scope Statement Note: Any work not explicitly included in the Project Scope Statement is implicitly excluded from the project. Project Name Cloud Implementation Prepared By Neil Doe Date 11/08/2015 Version History (insert rows as needed): Version Date Comments 1.0 11/8/2015 Initial Document