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

Slides:



Advertisements
Similar presentations
Project Management Concepts
Advertisements

A Short Course in Project Management
Roadmap for Sourcing Decision Review Board (DRB)
3-1 © Prentice Hall, 2004 Chapter 3: Managing the Object-Oriented Information Systems Project Object-Oriented Systems Analysis and Design Joey F. George,
© 2005 by Prentice Hall Chapter 3 Managing the Information Systems Project Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F.
© 2008 by Prentice Hall 3-1 ITCS311 Systems Analysis and Design Dr. Taher Homeed Feb 2010 Department of Computer Science College of IT University of Bahrain.
Evaluation and Reporting ENTC 4060 Project Scheduling.
Chapter 3 Project Initiation
ClosingExecuting/ Controlling ControllingPlanningInitiatingOpportunityAssessment Client AcceptancePlanning ApprovalInitiating ApprovalOpportunity Assessment.
Introduction to Project Management Avneet Mathur
Project Integration Management Sections of this presentation were adapted from A Guide to the Project Management Body of Knowledge 4 th Edition, Project.
Chapter 5: Project Scope Management
Project Management Session 7
Chapter 3: The Project Management Process Groups
Chapter 5: Project Scope Management
IS&T Project Management: Project Management 101 June, 2006.
Chapter 3 Project Initiation. The stages of a project  Project concept  Project proposal request  Project proposal  Project green light  Project.
IS&T Project Management: How to Engage the Customer September 27, 2005.
Project Scope Management
By: Muhammad Raza Ali Khan
© 2006 ITT Educational Services Inc. System Analysis for Software Engineers: Unit 5 Slide 1 Chapter 3 Managing the Information Systems Project.
Chapter 3 : Managing the Information Systems Project.
 A project is “a unique endeavor to produce a set of deliverables within clearly specified time, cost and quality constraints”
SA Capstone Requirements and Design Week 10 SYST Winter 2013 Instructors: Jerry Kotuba & Joe Varrasso.
Project Management Process Overview
Edward B. Farkas, Managing Director, Project Management Practice
9 Closing the Project Teaching Strategies
Server Virtualization: Navy Network Operations Centers
1 Our Expertise and Commitment – Driving your Success An Introduction to Transformation Offering November 18, 2013 Offices in Boston, New York and Northern.
BSBPMG503A Manage Project Time Manage Project Time Unit Guide Diploma of Project Management Qualification Code BSB51507 Unit Code BSBPMG503A.
Project Management for RIM Professionals Last Updated: 3/13/2011 Sarina Arcari, PMP VP Implementation & Product Planning Amerigroup Corporation 3/15/11.
Chapter 4 The Project. 2 Learning Objectives Third phase starts after a contract is drawn up and ends when the project objective is accomplished; final.
© 2015 Cengage Learning. All Rights Reserved. May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part.
Recap from last week Understand organizations, including the four frames, organizational structures. Explain why stakeholder management and top management.
IT 499 Bachelor Capstone Week 8. Adgenda Administrative Review UNIT Seven UNIT Eight Project UNIT Nine Preview Project Status Summary.
Next Doc Project Team: xxxxx Spring TitlePage Scope Statement Mission Statement3 Business Need4 Project Description5-6 Project Lifecycle Approach7.
PMX 470 – Spring 2010 Team “Cloud 9” Mete, Maíra, Conrad, Heather, & Shashi Relocation of Cloud 9’s company headquarters.
BIS 360 – Lecture Two Ch. 3: Managing the IS Project.
PMX 470 – Spring 2010 Team “Cloud 9” Mete, Maíra, Conrad, Heather, & Shashi Relocation of Cloud 9’s company headquarters.
Project Status Report Presenter Name Presentation Date.
© 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S.
PMX 470 – Spring 2010 Team “Cloud 9” Mete, Maíra, Conrad, Heather, & Shashi Relocation of Cloud 9’s company headquarters.
X470 Project Management EDP Summer 2007 Team #6: Albert Brown Alex Munoz Chris Yeh Daniele Pfeifer Lia Bruno Slava Balashov.
PMX 470 – Spring 2010 Team “Cloud 9” Mete, Maíra, Conrad, Heather, & Shashi Relocation of Cloud 9’s company headquarters.
© Mahindra Satyam 2009 Configuration Management QMS Training.
Project Kick-off Meeting Presented By: > > > > Office of the Chief Information Officer.
IT 499 Bachelor Capstone Week 4. Adgenda Administrative Review UNIT Four UNIT Five Project UNIT Six Preview Project Status Summary.
Develop Project Charter
Project Management Process Transition & Closure Project Management Process Project Description Team Mission/ Assignment Major Milestones Boundaries Team.
PMX 470 – Spring 2010 Team “Cloud 9” Mete, Maíra, Conrad, Heather, & Shashi Relocation of Cloud 9’s company headquarters.
Topic 5 Initiating a project
Innovation Software Corporation's Cultural Awareness Training Program Presentation by:
Chapter 3 Managing the Information Systems Project
SOLUTION What kind of plan do we need? How will we know if the work is on track to be done? How quickly can we get this done? How long will this work take.
Innovation Software Corporation's Cultural Awareness Training Program Presentation by:
PMX 470 – Spring 2010 Team “Cloud 9” Mete, Maíra, Conrad, Heather, & Shashi Relocation of Cloud 9’s company headquarters.
Planning & Scheduling a Production Activity BRITA LYONS HEGARTY, MARKET KNOWHOW 16 TH NOVEMBER 2015 TRADEIT: SMART USE OF ITWORKSHOP.
HCIS 410 Read, Lead, Succeed/Uophelpdotcom For more course tutorials visit
Information Technology Project Management, Seventh Edition.
IS&T Project Reviews September 9, Project Review Overview Facilitative approach that actively engages a number of key project staff and senior IS&T.
Dr. Gerry Firmansyah CID Business Continuity and Disaster Recovery Planning for IT (W-XI)
Project Management PTM721S
Office 365 Security Assessment Workshop
Systems Analysis and Design in a Changing World, 4th Edition
Project Management Lifecycle Phases
Hyper-V Cloud Proof of Concept Kickoff Meeting <Customer Name>
Project Overview.
{Project Name} Organizational Chart, Roles and Responsibilities
Presentation transcript:

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 Background & Scope Stakeholder Analysis Communications Management Plan Work Breakdown Structure (WBS) Responsibility Assignment Matrix Cost Baseline Schedule Baseline Risk Types Risk Response Plan

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 Business Need The relocation project needs to ensure a smooth transition for customers and employees to the new headquarters. 5/22/2010

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.

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.

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

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

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

Communication Plan Placeholder

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

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

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

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

Cost Baseline Summary Phase Phase Duration (days) Total – All tasks (days) Daily RatePhase Cost 1 - Planning55285$800.00$228, Preparation , Implementation , Post- Implementation ,600 Project Totals145693$800.00$554,400.00

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

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?

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

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

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

Time for your questions…