Project Deliverable 6: Final Project Plan

1

Running Head: PROJECT INTRODUCTION

2

PROJECT INTRODUCTION

Project Introduction

As the Chief Information Officer for an innovative internet-based business, the CEO requested that I design an appropriate project plan for integrating with a global corporation. Presented here is the organization's project introduction, which describes each of the company's priorities individually. In an executive leadership meeting, its executives decided it would be better to merge all its systems, such as infrastructure and databases, with a global company of comparable size.

This is a project plan for information technology preparation for the corporate merger that will be completed within the next 60 days. The chief executive officer will have the final say regarding the completion of the plan. Due to the merger of two smaller companies under one roof, the company will expand from one story to three stories within six months. The infrastructure will need to be rebuilt to accommodate the company's increased needs. To tailor information technology to meet organizational needs, all hardware and software must be changed. Currently, the firm uses operational systems and relational databases, but it is interested in warehousing.

In addition to delivering the solution as a cloud-based service, the project strategy entails merging technologies from multiple providers and applying best practices. As part of the company's expansion strategy, 40 inexperienced individuals will be hired to deploy cloud and virtualization technologies with appropriate security measures. Using a project management approach, the project plan includes the project name, project manager name, deliverables, scope statement, creation date, and completion date, among other helpful information.

Project management approach

The Project Plan and its Subsidiary Management Plans state that the Project Manager is accountable for overseeing and executing this Project. Project team members will include the coding group, quality assurance/quality control group, technical writing group, and testing group. All stakeholders will coordinate with the project manager to plan the Project. All project and subsidiary management plans will be reviewed and approved by the project sponsor. The project sponsor will also make all financing decisions. Whenever the project sponsor delegated approval authority to the project manager, the project manager and project sponsor must always agree and approve the delegation.

As part of the Project, a matrix-style organizational structure will be used with team members from each firm reporting to their respective corporate management. Team members from each company will be reporting to their respective organization's management as part of the Project.

Project Scope

This Project's scope ("Information Technology Project Management," 2021) includes the planning, designing, developing, testing, and migrating of the organization's information technology infrastructure. Software and hardware standards and a few other project charter specifications will be met or exceeded at this new facility. Besides completing all paperwork, manuals, and training aids for the program, this Project's scope includes completing all paperwork, manuals, and teaching aids used for the program. After successful implementation of the information technology requirements and documentation package and its distribution to the organization for use, the Project will be completed.

The Project will be handled exclusively in-house, and no part of it will be contracted out. No changes will be made to requirements for operating systems capable of executing the resources, new software, or revisions are included in the project scope.

Schedule and Work Breakdown Structure

As part of the Information Technology Project, the Work Breakdown Structure (WBS) comprises labor packages with a maximum of 40 hours of work and a minimum of 4 hours in length. Communication between members of the project team and stakeholders, along with input from functional managers and previous research, was used to create work packages. All work packages for the Project are defined in the WBS Dictionary. All tasks, resources, and deliverables are covered in these definitions. The WBS Dictionary defines each work package in the WBS, which aids in resource planning, task completion, and verifying deliverables fulfill project requirements ("Information Technology Project Management," 2021).

The project schedule was created using the work breakdown structure (WBS) and the Project Charter, with participation from all project team members. The schedule was finished, authorized, and baselined after being reviewed by the Project Sponsor. The Information Technology Project Manager will keep the schedule as an MS Project Gantt Chart. Any suggested schedule modifications will be subject to TSI's change control procedure. If specified boundary constraints are likely to be breached, the project manager will file a modification request. The Project Manager and team will assess the change's impact on the schedule, cost, resources, scope, and hazards. If the consequences are judged to be greater than the boundary conditions, the modification will be sent to the Project Sponsor for evaluation and approval. The information technology boundary criteria are CPI less than 0.8 or higher than 1.2 and SPI less than 0.8 or greater than 1.2.

If the Project Sponsor approves the change, it will be put into use by the Project Manager, who will update the schedule and related (paperwork that proves or supports something), as well as communicate the change to all (people who are interested in a project or business) in line with the Change Control Process.

The project manager will be in charge of the project from beginning to end/result.

References

Information Technology Project Management. (2021). Retrieved 14 October 2021, from https://books.google.co.ke/books?hl=en&lr=&id=mPeoBAAAQBAJ&oi=fnd&pg=PR7&dq=information+technology+project&ots=FNmuWuWU3h&sig=0DpBIIQMuJEbtrLiqbK_dTYCBaA&redir_esc=y#v=onepage&q=information%20technology%20project&f=false

Mitchell, V. L. (2006). Knowledge integration and information technology project performance. Mis Quarterly, 919-939.