PMX 470 – Spring 2010 Team “Cloud 9” Mete, Maíra, Conrad, Heather, & Shashi Relocation of Cloud 9’s company headquarters

5/22/2010 Table of Contents Project Scope Statement –Vision –Business Need –Project Description –Project Deliverables –Project Objectives –Assumptions –Constraints –High Level Risks –Approval Signatures

Table of Contents (cont’d) Stakeholder Analysis Project Lifecycle Work Breakdown Structure (WBS) Cost Baseline Schedule Baseline Communications Management Plan Responsibility Assignment Matrix Risk Types Risk Response Plan 5/22/2010

Project Scope Statement Our Vision Cloud 9 is a Business Solutions software design company. We plan to relocate our headquarters from San Francisco to San Jose in /22/2010

Project Scope Statement (cont’d) 5/22/2010 Business Need The relocation project needs to ensure a smooth transition for customers and employees to the new headquarters.

Project Scope Statement (cont’d) Project Description The Cloud 9 Headquarters relocation project will focus on the physical movement of office supplies, tools, and property while ensuring that high employee satisfaction is maintained 5/22/2010

Project Scope Statement (cont’d) Project Deliverables 5/22/2010 This project should:This project will NOT: - Only responsible for moving of office equipments (hardware, office supplies) - search and decide the new location is not in the scope. - Maintain employee satisfaction through communication and engagement throughout the process. - Move the existing cubicles and will NOT design/build the new office cubicles.

Project Scope Statement (cont’d) Project Objectives 5/22/2010 ObjectiveCriteria for Evaluation Maintain employee satisfaction throughout transition.We will conduct an employee satisfaction survey at the end of the project and hold a lessons learned session with the project team after results are in. Oversee network set up at new office locationTelephony and desktop networks are ready for use on Monday, March 28 at 9am Documentation and communication of new office layoutMovers and employees are able to report to new office location without significant loss of productivity. Completion of actual move without interruption of operations Minimal downtime is expected (as employees unpack their personal desks), however a company sponsored “moving day” is not possible so as to avoid service interruptions to our customers. Resolution of post-move issues in a timely mannerAll issues reported over the course of the moving weekend and in the week after the move must be acknowledged and a path forward identified within 24 hours of reporting.

Project Scope Statement (cont’d) Assumptions Employees will be given 2 boxes to pack their personal belongings. The company operates 9AM-5PM PST Mon-Fri. Employees shall upload all local information to servers The current servers will be synchronized with the new servers in the new location Employees shall have new desktops at the SJ office. The current employee desktops shall be returned to leasing company. Lease of SJ office shall be available by 02/01/11. 5/22/2010

Project Scope Statement (cont’d) Constraints The budget for the project is $1.4 million. The employee badge access to SF office shall expire on 04/01/11. 5/22/2010

Project Scope Statement (cont’d) High Level Risks 5/22/2010 Risk DescriptionTrigger Impact - Cost, Scope, Time (C,S,T) Natural disasterEarthquake, severe weather delaying move C,T Delay in networking completion Vendor issues (payment, resourcing) C, T Re-definition of scopeMissed requirementsS,C,T

Project Scope Statement (cont’d) Approval Signatures 5/22/2010

Stakeholder Analysis Stakeholder NameNeeds or Expectations Customers  Need to be notified of new office location and contact information  Expect to be able to contact their product manager without interruption of service Cloud 9 Employees  Need to be informed of move progress and expectations  Need to be given direction as to when to pack, where to report, etc for Day 1 in office  Expect to have the same level of employee “perks” at the new location. Cloud 9 Management  Expects the project to implement on time and within the $1.4M budget.  Expects to be kept informed of the project status through the lifecycle. 5/22/2010

Stakeholder Analysis (cont’d) Stakeholder NameNeeds or Expectations Local Merchant/Vendors  Expect to lose business (in ) but gain business (in ).  Need to be informed and consulted in to ensure that employees and vendors share in the relocation benefits. City Governments (San Francisco/San Jose)  will be losing tax revenue, however will be gaining revenue.  expects to receive the proper paperwork in preparation for the move (licensing, etc.) Vendors  To have clear expectations laid out prior to anticipated start date (ie movers need moving plan well in advance of moving date.  Networking contractor expect to have floor plans and timelines documented before engagement in network set up. 5/22/2010