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.
Business Requirements
Reference number:
Document Control
Change Record
|
Date |
Author |
Version |
Change Reference |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Reviewers
|
Name |
Position |
|
|
|
|
|
|
|
|
|
|
|
|
Table of Contents
2Document Control
1 Business Requirements 4
1.1 Project Overview 4
1.2 Background including current process 4
1.3 Scope 4
1.3.1 Scope of Project 4
1.3.2 Constraints and Assumptions 5
1.3.3 Risks 5
1.3.4 Scope Control 5
1.3.5 Relationship to Other Systems/Projects 5
1.3.6 Definition of Terms (if applicable) 5
1 Business Requirements
1.1 Project Overview
Provide a short, yet complete, overview of the project.
1.2 Background including current process
Describe the background to the project, (same section may be reused in the Quality Plan) include:
This project is
The project goal is to
The IT role for this project is
1.3 Scope
1.3.1 Scope of Project
The scope of this project includes a number of areas. For each area, there should be a corresponding strategy for incorporating these areas into the overall project.
Applications In order to meet the target production date, only these applications will be implemented:
Sites These sites are considered part of the implementation:
Process Re-engineering Re-engineering will
Customization Customizations will be limited to
Interfaces the interfaces included are:
Architecture Application and Technical Architecture will
Conversion Only the following data and volume will be considered for conversion:
Testing Testing will include only
Funding Project funding is limited to
Training Training will be
Education Education will include
1.3.2 Constraints and Assumptions
The following constraints have been identified:
The following assumptions have been made in defining the scope, objectives and approach:
1.3.3 Risks
The following risks have been identified as possibly affecting the project during its progression:
1.3.4 Scope Control
The control of changes to the scope identified in this document will be managed through the Change Control, with business owner representative approval for any changes that affect cost or timeline for the project.
1.3.5 Relationship to Other Systems/Projects
It is the responsibility of the business unit to inform IT of other business initiatives that may impact the project. The following are known business initiatives:
1.3.6 Definition of Terms (if applicable)
List any definitions that will be used throughout the duration of the project.
5
Job Analysis Interview Protocol – Job Incumbent (Employee)
Task/Working Conditions Meeting With Job Incumbent (Employee)
Subject Matter Expert (SME)
30 minutes
Job industry:
Location of interview (for example, phone, in person):
Job title of SME interviewed:
Date:
Time:
Note to interviewer: There are required questions that you should try to get through as well as additional questions as time permits. Read the protocol before beginning the interview to familiarize yourself with the questions. Probing questions are provided if needed. Normally, employee interviews will focus more on tasks and supervisor interviews will focus more on KSAOs, but for purposes of this assignment both are included to give you a more complete picture of the job in an efficient time to learn about job analysis first-hand. Normally, these interviews would take 45–60 minutes so decide ahead of time which optional questions you would like to ask if time permits. Optional questions are labeled as such in the protocol. Be respectful of the interviewer’s time and pace yourself to cover at a minimum the tasks, KSAOs, working conditions, and performance. At the end of the interview, thank the SME for his or her time and ask if he would be willing to participate in the next assignment (either a 10–15-minute survey or a 30-minute job observation). If willing, this will save you a step for the next assignment.
Introduction and Overview
· Good morning/afternoon. My name is ______________ and I am a graduate student at Capella University.
· This interview is part of a course assignment on job analysis.
· You have been selected to participate in this interview for approximately 30 minutes to provide your perspectives on what you do on the job and characteristics of successful employees in this position. Your responses will be confidential (I will not report your name or the name of your company) and you may stop the interview at any time.
· We will discuss your tasks and experiences as a [name of the job].
· Thank you for agreeing to participate in this session. Do you give your consent to proceed with the interview?
· Do you have any questions before we get started?
Background
Tell me about your current job, how long you have worked in this role, and how long you have worked in the _____________ industry.
Tasks/Activities
· In a typical week, what are the primary tasks or activities that you perform on the job?
· What tools, equipment, or resources do you use on the job?
Knowledge, Skills, Abilities, and Other Characteristics for Success
· What knowledge, skills, or abilities, if any, do employees in this role need to have on the first day of the job (before any job training)?
· Think of the most/least effective employees in this role. What separates the best employees from the rest? Probing questions you can choose from:
· How are their skills different?
· Is it something they bring into the job with them (personality)?
· How do they differ from other employees in attitude and teamwork?
· What separates the worst employees from the rest? Which types of employees are least likely to succeed on the job?
Work Environment (Ask at Least One of These Questions)
· How often can you take breaks? Are they scheduled breaks?
· Describe the environmental conditions of the job (noise level/distractions, shifts (for example, number of hours, times, and frequency of shift rotation)
Performance
· What performance goals or standards are there for employees in this job? What does your supervisor evaluate you on in terms of your performance?
Questions if Time Permits (Select Any of the Following)
Challenges
· What types of issues or challenges do you typically handle on the job?
· What types of skills or abilities are needed to handle these challenges?
· Which situations are more challenging to resolve than others? Why – what is involved?
Job Fit
· What do you enjoy most about this job?
· What do you like least about this job?
· What did you wish you knew about the job before you entered into this role?
Decision Making
· What types of issues or situations would require you to go to a supervisor or coworker for assistance?
· What percent of issues do you typically handle on your own versus obtain assistance from others?
Critical Incidents
Describe a situation in which an employee in this role was particularly effective .
a. Give a specific example.
b. What was the situation?
c. What did they do specifically?
d. What was the result?
e. What made this behavior particularly effective that set the employee apart from others?
Describe a situation in which an employee in this role was ineffective.
a. Give a specific example.
b. What was the situation?
c. What did they do specifically?
d. What was the result?
e. What would a more effective employee have done instead?
Turnover
· What are the most common reasons people leave this job?
1
3
Get help from top-rated tutors in any subject.
Efficiently complete your homework and academic assignments by getting help from the experts at homeworkarchive.com