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

2. 5/22/2010 Table of Contents Project Background & Scope Stakeholder Analysis Communications Management Plan Work Breakdown Structure (WBS) Responsibility Assignment Matrix Cost Baseline Schedule Baseline Risk Types Risk Response Plan

3. Project Background Purpose Cloud 9 is a Business Solutions software design company. We plan to relocate our headquarters from San Francisco to San Jose in 2011. Business Need The relocation project needs to ensure a smooth transition for customers and employees to the new headquarters. 5/22/2010

4. 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 This project should:This project will NOT: - Responsible for moving of office equipment (office appliances, 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.

5. 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 location Telephony and desktop networks are ready for use on Monday, March 28 at 9am Documentation and communication of new office layout Movers 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 manner All 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.

6. Assumptions 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 will receive new desktops at the SJ office. The current employee desktops shall be returned to leasing company. Employees will be given 2 boxes to pack their personal belongings. Lease of SJ office shall be available by 02/01/11. 5/22/2010

7. 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

8. 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

9. Stakeholder Analysis (cont’d) Stakeholder NameNeeds or Expectations Local Merchants (Restaurants, etc)  Expect to lose business (in SF ) but gain business (in SJ).  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 (Movers, etc.)  To have clear expectations laid out prior to anticipated start date (i.e. 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

10. Communication Plan Placeholder

11. Work Breakdown Structure (High Level) Headquarters Relocation Planning ProcurementInfrastructure Human Resources FinanceOffice Layout Preparation/Testi ng InstallationLogistics Employee Satisfaction Issue Management Marketing Implementation Command Center Relocation Post- Implementation CelebrationProject Closure

12. Work Breakdown Structure (Detail) WBS IDWBS SectionWBS SubsectionWBS Description 1.1.1PlanningProcurementVendor management 1.1.2PlanningProcurementContract Management 1.2.3PlanningInfrastructureServers and File Migration 1.2.4PlanningInfrastructureTelephony 1.3.1PlanningHuman ResourcesEmployee Lists 1.4.1PlanningOffice LayoutBlueprints 1.4.2PlanningOffice LayoutDesk requirements 1.4.4PlanningOffice LayoutPublic space planning 2.1.1PreparationInstallationInstallation period 2.1.4PreparationInstallationNetwork testing 2.1.5PreparationInstallationTelephony 2.2.3PreparationLogisticsData security planning 2.2.6PreparationLogisticsBox distribution 2.3.1PreparationEmployee SatisfactionCommunication Plan 2.3.6PreparationEmployee SatisfactionEmployee Survey 2.3.12PreparationEmployee SatisfactionEmployee Perks 2.4.1PreparationIssue ManagementPlaybook definition 2.4.3PreparationIssue ManagementIssue Management Process 2.4.7PreparationIssue ManagementCommand Center Planning 2.5.1PreparationMarketingIndustry Materials updates 3.1.1ImplementationCommand CenterCommand Center Implementation

13. Responsibility Assignment Matrix WBS Deliverables Sponsor ProjectMgr PurchaseMgr HRMgrITMgr MarketingMgr SecurityMgr Planning -Draft contracts -Copies of lease agreements -New office blueprints -Proposed office setup / layout -Employees list -Contract workers list (movers, network installers, etc.) AAAAAAAAAAAA RCCCRRRCCCRR CICI ICCICC III Preparation -Company business documents -Installation period definition -Moving plan with moving company -Data security plan -Issue management process document - Data files migration plan from current servers to new servers -Command center (war room )location -Command center schedule -New Business cards AAAAAAAAAAAAAAAAAA RCCRCRCCRRCCRCRCCR IIIIIIIIII IIIICIIIIC RICICIIRICICII CIIIICIIII IIIIIIIIII

14. Responsibility Assignment Matrix WBS Deliverables Sponsor ProjectMgr PurchaseMgr HRMgrITMgr MarketingMgr SecurityMgr Implementation -Command center procedures - Lunch coupons & Boxes -Data security plan procedure completion -Shipment log of old desktops/ telephones AAAAAAAA CCRCCCRC IRIR IRIIRI ICRICR IIIII Post- Implementation - Project total cost - Final status report -Moving celebration Plan -Lessons learned AAARAAAR CCCCCCCC RRRRRR IIII

15. Cost Baseline Summary Phase Phase Duration (days) Total – All tasks (days) Daily RatePhase Cost 1 - Planning55285$800.00$228,000.00 2 - Preparation55321800256,800 3 - Implementation102080016,000 4 - Post- Implementation 256780053,600 Project Totals145693$800.00$554,400.00

16. Cost Baseline Example (Phase III) WBS #Phase / Tasks ListDurationDaily RateTotal Cost 3 IMPLEMENTATION (10 days) 3.1 Command Center (7 days) 3.1.1 Initiate command center procedures 1800 3.1.2 Hold status review calls 58004000 3.1.3 Close Command Center 1800 3.2 Relocation (10 days) 3.2.1 Distribute lunch coupons to employees for packing their boxes on-time 1800 3.2.2 Verify movement of boxes to new location 1800 3.2.3 Complete building walkthrough 1800 3.2.4 Ensure data security plan ( disk scrubbing, backups, etc) standards 88006400 3.2.5 Verify new building access 1800 3.2.6 Verify shipment of old desktops/telephones to leasing company 1800 T O T A L for Phase 32080016000

17. Schedule Baseline Awaiting final Schedule Baseline Shashi – –Instead of posting the actual plan into this presentation and having you read it to the class (which is not generally a preferred way to present), would you like to have a simple timeline that shows the milestones along a bar? –Then, we can post a sample of the project plan document on the slide after. –What do you think?

18. High Level Risks 5/22/2010 Risk DescriptionTrigger Impact – Cost, Scope, Time (C,S,T) Natural disaster Earthquake, severe weather delaying move C,T Delay in networking completion Vendor issues (payment, resourcing) C, T Re-definition of scope Missed requirements S,C,T

19. Risk Analysis Placeholder Mete – I need the ppt in an older version of PPT, sent you an email

20. Risk Mitigation Placeholder Mete – I need the ppt in an older version of PPT, sent you an email

21. Time for your questions…