Fluent Essays

The project will address client’s needs to upgrade their 3 existing legacy data centers and migrate eligible applications to the Cloud: Total of 3 primary data centers (2 for Production and 1 for Disaster Recovery) All 3 data centers share redundant WAN circuits (2 MPLS and 1 Point-2Point) for users and data traffic Client has a total of 145 enterprise applications and 1350 servers: 450 Windows Servers 550 Unix Servers 350 ESX, VMWare, and legacy AIX servers Allowed project budget is $1.5 Million with a $150K for contengecies The client is open to the top 3 Cloud providers (AWS, Azure, and Google Cloud) You have the ability to assemble your team Stakeholders are also open to your specific and project needs (define their roles and responsibilities as you see them fit) All 3 Data centers are in the United States – the DR DC must be on a different State for recovery purposes Assignment Week 4 – Scope and Schedule: At the end of week 4, you are to finalize the initial approved scope from week one an d start building the project schedule. In this week, you are also to work on building the project Work-Breakdown Str ucture (WBS). Project scope and schedule will include the following components: Finalized project scope Project requirements – in more details WBS structure Developed project schedule Identify key milestones and deliverables Outline project resources and assign them to tasks accordingly. Stakeholder engagement – communication plan NOTE: I have added project guide and work I have done so far, need help with rest of the sections in week4 and Feel free to edit the content Course : :Project Management Course Project Overview: This course project introduces an opportunity to explore all the project stages (from inception to closing) facilitated by the well-known Project Management Group Processes (initiation, planning, execution, monitoring and control, an d closure) as outlined in the PMBOK® Guide. Two Project Options: Data Center Transformation – to complete a migration strategy/plan to complete the following two tasks: On-Premise Transformation Infrastructure And Application Migration to The Cloud Pick your own project: Students will have the option to also choose their own project – project scope will need to be approved by the course instructor As you progress through the weekly materials in the course, you will apply the key principles and knowledge areas ( Scope, cost, schedule, quality, resources, risk management, procurement, communication, and stakeholder managem ent) to your project. You will use Microsoft Project software to track the entire project management plan (PMP), dev elop the schedule, and track the overall progress of the project. As the project manager (PM) for a medium-scale pro ject, you will apply fundamental principles and best practices to conduct your project from inception to closing. Eac h assignment provides further detail. Known Scope: The project will address client’s needs to upgrade their 3 existing legacy data centers and migrate eligible applicatio ns to the Cloud: Total of 3 primary data centers (2 for Production and 1 for Disaster Recovery) All 3 data centers share redundant WAN circuits (2 MPLS and 1 Point-2Point) for users and data traffic Client has a total of 145 enterprise applications and 1350 servers: 450 Windows Servers 550 Unix Servers 350 ESX, VMWare, and legacy AIX servers Allowed project budget is $1.5 Million with a $150K for contengecies The client is open to the top 3 Cloud providers (AWS, Azure, and Google Cloud) You have the ability to assemble your team Stakeholders are also open to your specific and project needs (define their roles and responsibilities as you see them fit) All 3 Data centers are in the United States – the DR DC must be on a different State for recovery purposes Requirements: Meet the weekly assignments’ requirements (total of 4 assignments to complete the entire project) within the 8 week s duration of the course. You will be assigned as the main PM for the project, where you will own the entire project Your course instructor will act at the project sponsor – can address all your questions and concerns and will provide you feedback during the weekly assignments submissions. The project will include internal and external stakeholders, vendors, team members, and contractors. A well-defined project charter must be approved by course instructor by end of week one. Your final project management plan as well as the weekly submissions must adhere to the following formatting requ irements: APA version 7 is the required format for the entire paper. Turnitin tool Weekly Assignment - Structure: Week 2 - Project Charter: At the end of week 2, you are to create and submit the project charter. This is the first offi cial document to be reviewed and approved by the project sponsor. Project charter will include the following compo nents: High-level project scope High-level project requirements Business needs Early estimation and forecasted cost Stakeholder analysis (roles and responsibilities) High-level Communication plan High-Level Resource plan Early risk indications Week 4 – Scope and Schedule: At the end of week 4, you are to finalize the initial approved scope from week one an d start building the project schedule. In this week, you are also to work on building the project Work-Breakdown Str ucture (WBS). Project scope and schedule will include the following components: Finalized project scope Project requirements – in more details WBS structure Developed project schedule Identify key milestones and deliverables Outline project resources and assign them to tasks accordingly. Stakeholder engagement – communication plan Week 6 – Budget and Risk Management: At the end of week 6, you are to finalize the overall project cost and clearl y document project risks gathered throughout the project. As part of risk management plan, you are expected to shar e a risk response plan. Project cost and risk management plans will include the following components: Overall project budget (utilizing EVM – share current and forecasted project status) Project requirements – updated Cost management plan – outlining contingency plan for project changes Detailed risk management plan Risk response plan Risk mitigation plan Change management process How project RAID (Risk, Assumption, Issues, and Dependencies) will be managed Stakeholder engagement – communication plan Week 8 – Quality and Project Closure: At the end of week 8, you are to finalize the overall project management plan (PMP). In this week, you are to integrate all previously submitted components incorporated with instructor (project sponsor) feedback into a single project management plan. Project management plan will include the following comp onents: Project quality management plan to include an updated scope, cost, schedule, communication, risk, resources, procur ement, and quality) Updated changes – Change Request (if any) Project requirements – updated Stakeholder register – updated How project RAID (Risk, Assumption, Issues, and Dependencies) Document project lessons-learned Project sponsor approval of the key project deliverables For the project submission: Students can use MS project (if they have access to it) or MS Excel, Word documents, and any other free related soft ware they are able to access as long as they meet the assignment’s scoring rubrics/guidelines. Project: scope of project Date: 09/19/2021 Project Management-GE 5103 Cloud Migration (Private cloud to AWS)  Week4_Scope and Schedule Finalized Scope: The main purpose of this project is to transfer the data from one cloud to another of high availability and performance of project, so that we can secure the confidential files with access controls, the data storage, servers, network infrastructure, and security elements such as firewalls, setting up VPNs for project access everything can be done with in a data center, so far we do have 3 data centers as 2 for production and one for disaster recovery , so if any disaster occurs then the data can be recovered from disaster recovery center without any application delays.  Requirements: Describe Work Breakdown Structure: You can use this for reference Resource Duration Responsibility Budget Planned Start Date Planned End Date Project Manager 4mnths Manage the project $275 10/01/2021 01/31/2022 Software Engineer 4mnths Develop the code and maintain $250 10/01/2021 01/31/2022 Hardware Engineer 1mnth Set up hardware $125 01/01/2022 01/31/2022 Test Engineer 1mnth 1.Quality check of the product 2. Test if the product passes all safety and quality standard $125 01/01/2022 01/31/2022 Logistic Manager 4mnths Supply and maintain warehouse material during the project and procurement shipping $700k 10/01/2022 01/01/2022 Develop Project Schedule: Resource Month1 Month2 Month3 Month4 Project Manager Assigning all the task to the team And kick off the project Checking every 15days for progress Review the progress made till date and add new features if required Go through the project and identify if any missing features and deliver the product to clients. Software Engineer Develop the working simulation. Run, test and complete the simulation HW and SW team to collaborate Enhancements based on the hardware design; complete working s/w based on the working h/w Fix the bugs identified by the QA and retest in lower environments and deliver error free software Hardware Engineer Develop the working simulation and decide on Hardware paths needed for the device Runs, test and complete the simulation Check for any updates required for the hardware and add additional capacity if required Set up required hardware for final product and maintain. Test Engineer NA Collects the list of supplies for procuring the hardware parts Order and purchase the parts Complete Regression, sandbox testing and write unit cases at each stage Logistic Manager NA NA Review the work made till date and give a sample demo to stake holders Demo the final output and deliver to clients. Key Milestones and Deliverables: Identify key milestones in the project and explain why? Hello Class- This is a very rough draft of the assignment. I have broken down each section and potential opportunities for you. This is not all inclusive as you can be creative but you must meet the deliverables of this assignment. Scope and Schedule: At the end of week 4, you are to finalize the initially approved scope from week two and start building the project schedule. In this week, you are also to work on building the project Work-Breakdown Structure (WBS). Project scope and schedule will include the following components: - Finalized project scope - Project requirements – in more details - WBS structure - Developed project schedule - Identify key milestones and deliverables - Outline project resources and assign them to tasks accordingly. - Stakeholder engagement – communication plan Make sure that there is a heading for each section. Title Page – Name, date, etc · Finalized Project Scope: Chapter 7 Scope Planning, I just want a summary of what your final scope is. · Project Requirements – Details · WBS Structure- (Week 3) Chapter 7 Video, How to construct a WBS? · · Developed Project Schedule – Chapter 8 Video – Develop Project Schedule, Chapter 8 Reading Scheduling Projects – May ways to show schedule just pick one. Develop Project Schedule Once you have an estimated duration for each activity in the network must determine (based on durations and sequence) whether the project can be realistically finished by the required completion time. · In order to do this, the contractor should estimate the duration of each activity. · He or she should establish an overall window of time for the project. Develop a project schedule that provides a timetable for each activity and shows: · The earliest times (or dates) at which each activity can start and finish, based on the project estimated start time (or date) · The latest times (or dates) by which each activity must start and finish in order to complete the project by its required completion time (or date) · Incorporate Changes into Schedule · Throughout a project, changes may occur that impact the schedule. · Changes might be initiated by the customer or the project team, or they might be the result of an unanticipated occurrence. · Changes requested early in the project may have less of an impact on schedule and budget than those requested later in the project. · When the customer requests a change, the contractor or project team should estimate the impact on the project schedule and budget and then obtain customer approval before proceeding. · If the customer approves the proposed revisions to the project schedule and budget, then any additional activities, revised estimated durations, and revised estimated resources and associated costs should be incorporated into the project schedule and budget. · With respect to the project schedule, changes can result in the addition or deletion of activities, re-sequencing of activities, changes to estimated durations for specific activities, or a new required completion time for the project. · · Identify key milestones and deliverables – Write up your key or show them on your graph and point them out. Discuss in a summary what they are. · Outline project resources and assign them to tasks accordingly · · · · · · · Stakeholder engagement- communication plan · 6-2aCreating a Stakeholder Engagement Assessment Matrix · Project teams create a  stakeholder engagement plan  to define how they will effectively engage stakeholders in planning and performing the project based on the analysis of the stakeholders’ needs, wants, and impacts. A primary tool used in this plan is the  stakeholder engagement assessment matrix . This matrix typically includes a first column showing the stakeholders. For each stakeholder, additional columns may represent how much they are currently supporting or opposing the project, where you would like them to be, barriers to their changing, and strategies you may employ to move them. Strategies for powerful and supporting stakeholders may include accepting their ideas, compromising, or offering them trade-offs, while strategies for opponents might entail doing the minimum possible or fighting their demnds. It is not uncommon to think that the best one can do with opposing stakeholders is to help move them to a neutral position, while those who are unaware of or neutral toward the project may be turned into supporters. · Exhibit 6.5 identifies both the current and target positions of the stakeholder groups. The greater the change in position, the greater the risk and the greater the engagement effort required. Student Services had a relatively unimportant position in the old system but would be critical to the new modularized operation. Significant expenditure was anticipated in this area. It is of interest to note that the initial analysis (see  Exhibit 6.4 ) had identified this group as “other stakeholder.” As the nature and impact of changes become clearer, they can alter the relative importance of different groups. Stakeholder positions and stakeholder strategies must be reevaluated throughout the project. · Exhibit 6.5 · Modular Courses—Stakeholder Engagement Assessment Matrix STAKEHOLDER CURRENT POSITION TARGET POSITION BARRIERS TO CHANGE STRATEGY Vice Chancellor Leading Leading Competing day-to-day priorities Ensure engagement is ‘efficient’ and effective. Consider extending role of deputy Chancellor to cover for some day-to-day activities. Deans of Faculty Resistant Neutral, Supportive, or Leading Some Deans more powerful than others (relates to student numbers and academic ratings). ‘Power owners’ are very influential. Consider each Dean’s WIIFT individually. Consider strategies for individuals as well as the group. Academic Registrar (AR) Supportive Leading Competing day-to-day priorities—lack of leadership skills. Engage deputy, provide skills and mentorship. Lecturers Unaware to neutral Neutral or supportive Very large group with veto power through unionized actions. Involve HR and legal department to evaluate  · © 2018 Cengage®. May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part, except for use as per mitted in a license distributed with a certain product or service or otherwise on a password -protected website or school -approved learning m anagement system for classroom use. IS Example: Resource Requirements © 2018 Cengage®. May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part, except for use as per mitted in a license distributed with a certain product or service or otherwise on a password -protected website or school -approved learning m anagement system for classroom use. IS Example: Responsibility Assignment Matrix