BusinessCase/Benefits Pre-assigned Resources StakeholdersList (impacted, have interested on your projects) Name Title Role/Responsibility SummaryMilestoneSchedule Description DueDateDesign training material, update process documents Testing Create Test Cases & Test Scripts with traceability to requirements 2_4 weeks Conduct UAT 12 weeks Conduct Regression Test Go Live, Lessons Learned, Closing Create Cutover plan 12 weeks Execute Cutover 1 week Go-Live (technical & business) 1 week Hypercare (transition to sustainment) ProjeCt CIOSlng SummaryBUdEEt Resources, time, and vendor costs comprise the bulk of the project's financial requirements.For the fiscal years 2023 and 2024, respectively, budgets of XXX$ and XX$ have been set aside. Assumptions Constraints The following presumptions are the foundation of . Before project XXX can go live, this project this project: will. The business is devoted to creating a website that is organization and customer-centered. High-Level Technical Risks: If the new chat box system doesn't integrate smoothly with PrleCtRi5k5 the existing systems and processes, there can be delays and additional costs.Technical compatibility issues may arise if the chat box system is not designed to work with the current hardware, software, or network infrastructure. It's possible that the new chat box technology won't function as well as anticipated or won't be able to handle a lot of user activityRisks of Customer Adoption:Lack of acceptance and decreased efficacy of the new chat box system may be caused by employee and customer reluctanceBecause customers and staff might not fully understand the benefits of the new system, it might be difficult to promote and encourage its use.Customers and employees who are not tech savvy may find it challenging to use the new SuccessCriteria chat box system. Data risks: Sensitive customer data may be exchanged and stored during installation in a way that exposes it to security breaches. There could be risk if sensitive client data is not handled properly and safely. The quality and accuracy of client data may be affected during the deployment process, leading to erroneous data being retained and used. The project is finished on schedule and within budget. Performance and scalability of the chat box system, as well as technical compatibility and integration simplicity, are all important components of technical success.Success in protecting remote data access, transitioning to hybrid work, and managing distant staff.A high adoption rate, great benefit communication, and an easy-to-use user interface are success factors for consumer adoptionBusiness success: Bettering the client experience, increasing output and efficiency, and generating a positive return on investment (ROI). Undo Clipboard Font Alignment Number Styles Cells Editing Analysis Sensitivity B5 viX fx 1.1.2 A B C D E F G H WBS DICTIONARY PROJECT FULL PROJECT NAME: PROJECT No: MANAGER: W N ESTIMATED ESTIMATED RESPONSIBLE DEPENDANCIES RESOURCE REQUIREMENTS ID WBS ID DETAILED DESCRIPTION DURATION COST PARTY/PERSON (WBS ID) (Human and Physical) 4 (optional) (optional) UT 1 1.1.2 N W A 10 11 7 12Working INDIVIDUALY, develop a Preliminary WBS and its Dictionary, using MS-Project, that illustrates the possible structure of the project work hierarchy, starting from general concepts level down to detailed Work Packages, that you recommend at this stage for your project. The WBS shall include the deliverables you initially identified in your charter/preliminary scope document, with emphasis on specific project tasks (not generic development tasks). You may include additional ones as you judge necessary. Remember that you do not have the complete details of the project at this point, so do not attempt to infer what these would be - use only the information you have to develop a preliminary list of work in the form of a WBS. A subsequent assignment will ask you to refine these or add more activities. A. The Initial WBS Deliverable Content 1. THE FILE NAME of the submitted assignment must appear at the top level of your WBS 2. Show at least 3 work detail levels in MOST of the areas of your WBS; (i.e. Major Work Level and 2 additional sub-task levels). 3. Additionally, you will need to include appropriate project management tasks, such as team meetings, training and testing tasks in all appropriate areas of the WBS for this particular case study. 4. Include all the features you have learned in class about WBS including code numbering. 5. Show manageable tasks at the Work Package level 6. Prepare only the WBS in MS Excel. That will include full list of activities, resource loadings, costing, etc. 7. Please ignore Part 2 of the case problem for now, other than the WBS part. 8. Think as a Project Manager about what work your team should do, without getting distracted with the technology solution. You do not know how the technology components will all be at this point B. Simple WBS Dictionary Content 1. Prepare a WBS Dictionary, for the WBS created in part A, for your project. Use the template provided with this assignment and complete all fields. (Estimated Duration and Estimated Cost are OPTIONAL) 2. There should be at least 15 tasks in your WBS Dictionary, selected from various parts of your project. These must be tasks specific to the project, not generic tasks. 3. For example: . Example: 5.2.4 Product Testing . Products will be scheduled for testing in 6 stages as defined within the corporate quality assurance manual. The product quality assurance team will be the lead for this set of tests