!""#$%&'%( ** + *, -./0'1( 23%3$'&'%( 4,!56 -'.78 By Date
: Arwan 1801693691 : 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 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
91/:' /; -./0'1( 23%3$'&'%( !"#$% '( ()$*" $+ ,-$.")/ 01213"4"2/5 ! Project objectives o Corporate assets Standardization o Creating and Implementation Assets Upgrade Documents Assets Standardization for 2000 Employee o o Timeline 9 months
!
Goals o o o o
!
Upgrade 2000 employee assets Standardization hardware assets Upgrade timeline not more than 9 months Inventory assets
Tasks o o o o
Implementation and Deployment Asset Management and Inventory Grouping Assets Upgrade Assets with Corporate Standardization Documentation and Reporting
!
Resources o Project Manager, as manage all project details Technical Consultant, technical lead for whole project o o System Engineer (Roll-Out Engineer), as engineer to upgrade employee assets, commonly do visit o Technical Writer, help documentation and reporting Contact Center, as single point of contact from user to asset upgrade team o while upgrade process
!
Budget
!"
$%%&'% (')*+),-.)'-" * /"%'
6 :
71-8%1-" +$- 9*3-18" ,-$.")/ 01213"- +$- A 4$2/B C6;0 D 4$2/BE
F J ?
!
0'1
2,-3&
4"')5 2,-3&
:;;; 6
<=>?@;;;@;;; <=>A;@;;;@;;;
<=> <=>
6;@;;;@;;;@;;; A;@;;;@;;;
GH(/"4 I23'2""- +$- A 4$2/B C?0 D 0$2/BE K")B2')1# L-'/"- +$- A 4$2/B C?0 D 0$2/BE
6; 6
<=>J?@;;;@;;; <=>J?@;;;@;;;
<=> <=>
J?;@;;;@;;; J?@;;;@;;;
M$2/1)/ M"2/"- +$- A 4$2/B C?0 D 4$2/BE K$/1# M$(/
:
<=>J?@;;;@;;;
<=> <=>
A;@;;;@;;; 6;@NO?@;;;@;;;
Schedule o o o
Assets Inventory Upgrade Hardware Evaluation and Fine Tuning
-./0'1( <'=>#.'&'%( ?/@@'1(#/% !
Asset Inventory Tools o Collect and discovery current hardware, network and software Support create reporting assets o o Automatic update asset information
!
Assets Hardware Standardization Hard Disk : OS 100 GB, Data 200 GB o o RAM : 4 GB o CPU : 1 processor, 2-core : 1 Gbe o Network o Software : Corporate allowed Apps
-./0'1( 23%3$'&'%( 91/:' Project Charter Project Tittle: Corporate Assets Standardization 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)
91/:' /. A/.B 3%C ,#&'@#%' DAE9F Project Timeline
WBS
