Assignment II - IT Project Management LTA Per.3

Download as pdf or txt
Download as pdf or txt
You are on page 1of 4

Assignment

II – IT Project Management LTA-1 Per.3


By : Arwan 1801693691
Date : 26 September 2017

OPENING CASE
Kim Nguyen was leading a meeting to create the work breakdown structure (WBS) for her
company’s IT upgrade project. This project was necessary because of several high- priority,
Internet-based applications the company was developing. The IT upgrade project involved
creating and implementing a plan to make all employees’ IT assets meet new corporate
standards within nine months. These standards specified the minimum requirements for each
desktop or laptop computer, including the type of processor, amount of memory, hard disk
size, type of network connection, and software. Kim knew that to perform the upgrades, the
project team would first have to create a detailed inventory of all the current hardware,
networks, and software in the entire company of 2,000 employees.

Kim had worked with other stakeholders to develop a project charter and initial scope
statement. The project charter included rough cost and schedule estimates for the project
and signatures of key stakeholders; the initial scope statement provided a start in defining the
hardware, software, and network requirements as well as other information related to the
project scope. Kim called a meeting with her project team and other stakeholders to further
define the scope of the project. She wanted to get everyone’s ideas on what the project
involved, who would do what, and how they could avoid scope creep. The company’s new
CEO, Walter Schmidt, was known for keeping a close eye on major projects. The company
had started using a new project management information system that let everyone know the
status of projects at a detailed and high level. Kim knew that a good WBS was the foundation
for scope, time, and cost performance, but she had never led a team in creating one or allocating
costs based on a WBS. Where should she begin?

Project Scope of Management


Project scope of management will consist of several processes:
1. Scope of Management
2. Project Requirement Collection
3. Define Scope
4. Project Working Breakdown Structure (WBS)
5. Validation and Controlling Scope

Scope of Project Management


Below is scope of Project Management:
Ø Project objectives
o Corporate assets Standardization
o Creating and Implementation Assets Upgrade Documents
o Assets Standardization for 2000 Employee
o Timeline 9 months
Ø Goals
o Upgrade 2000 employee assets
o Standardization hardware assets
o Upgrade timeline not more than 9 months
o Inventory assets

Ø Tasks
o Implementation and Deployment Asset Management and Inventory
o Grouping Assets
o Upgrade Assets with Corporate Standardization
o Documentation and Reporting

Ø Resources
o Project Manager, as manage all project details
o Technical Consultant, technical lead for whole project
o System Engineer (Roll-Out Engineer), as engineer to upgrade employee
assets, commonly do visit
o Technical Writer, help documentation and reporting
o Contact Center, as single point of contact from user to asset upgrade team
while upgrade process

Ø Budget
No Assets Standarization Cost Qty Price Total Price
1 Hardware for upgrade 2000 IDR5,000,000 IDR 10,000,000,000
2 Project Manager for 9 month (10M / month) 1 IDR90,000,000 IDR 90,000,000
3 System Engineer for 9 month (5M / Month) 10 IDR45,000,000 IDR 450,000,000
4 Technical Writer for 9 month (5M / Month) 1 IDR45,000,000 IDR 45,000,000
5 Contact Center for 9 month (5M / month) 2 IDR45,000,000 IDR 90,000,000
Total Cost IDR 10,675,000,000

Ø Schedule
o Assets Inventory
o Upgrade Hardware
o Evaluation and Fine Tuning

Project Requirement Collection


Ø Asset Inventory Tools
o Collect and discovery current hardware, network and software
o Support create reporting assets
o Automatic update asset information

Ø Assets Hardware Standardization


o Hard Disk : OS 100 GB, Data 200 GB
o RAM : 4 GB
o CPU : 1 processor, 2-core
o Network : 1 Gbe
o Software : Corporate allowed Apps
Project Management Scope
Project Charter
Project Tittle: Corporate Assets Standardization
Project Start Date: October 1 2017 Project Finish: June 30 2017
Key Schedule and Milestone:
• Asset Inventory
• Hardware and Software Acquisition
• Roll-out Upgrade
• Documentation and Report
Budget Information: 10B for Hardware and 675M for Man Power
Project Manager: Arwan, email: [email protected]
Project Objective:
• Corporate assets Standardization
• Creating and Implementation Assets Upgrade Documents
• Assets Standardization for 2000 Employee
• Timeline 9 months
Main Project Success Criteria:
• All Corporate assets already (Hardware and Software) are using corporate standard
• Project done in 9 months period
• Minimal downtime for user
• Enhancement user productivity
Approach:
• Assets Inventory
• Roll-out
• Upgrade Hardware
• Evaluation and Fine Tuning
Roles and Responsible
Name Role Responsible
Arwan Project Manager Project Monitoring and Scheduling
Mr. Harjito Project Owner / CEO Project Sponsor and Owner
MR. A Technical Consultant Technical planning and execute project
MR. B Technical Writer Technical documentation and documentation
Roll-out Engineer System Engineer Roll-out upgrade

Sign off – (Signature)

(ARWAN) (MR. HARJITO) (MR.A) (MR.B)


Scope or Work and Timeline (WBS)
Project Timeline

WBS

You might also like