5 Sole Supplier of U.S. Navy Aircraft Carriers One of Two Builders Constructing Virginia Class...

Post on 17-Dec-2015

221 views 1 download

Tags:

Transcript of 5 Sole Supplier of U.S. Navy Aircraft Carriers One of Two Builders Constructing Virginia Class...

Anaheim, CA | February 2-5, 2014

Jenni Connolly, PMPSenior Project ManagerHuntington Ingalls-Newport News Shipbuilding

Resource Management in Project Server – From Idea to Deployment in 9 Months

PC216

AgendaIntroductionsOrganizational Background Business RequirementsSolution ApproachDeployment ApproachReportingLessons LearnedWhat’s Next?Q & A

Presenters

Jenni Connolly, PMP, MBASenior Project ManagerNewport News Shipbuilding

Rob HirschmannPartnerProjility, Inc.

Need image

5

Newport News Shipbuilding• Sole Supplier of U.S. Navy Aircraft Carriers

• One of Two Builders Constructing Virginia Class Nuclear Submarines

• Exclusive Provider of Refueling Services for Nuclear-Powered Aircraft Carriers

• Largest Non-Governmental Provider of Fleet Maintenance Services to the Navy

• Largest Industrial Employer in Virginia – More Than 23,000 Employees

• Home of one of the Western Hemisphere’s Largest Dry Docks and Cranes

• Founded in 1886

BeforeNo visibly across the organization

Multiple disconnected systems

Competing Priorities

How it all startedThe MS Project Server decision

“We’ve never done this before”

An integration partner is key

Requirements

The Requirements

PaLM

Portfolio and Labor ManagementPutting Portfolio and Labor Management in the “palm” of your hand!

The Requirements

The RequirementsDemand ManagementPrioritiesSkill setsTrue demand vs. inflated estimates

Resource ManagementPrioritiesRealistic, real-time view (who, what, when)Skill Sets

Project ManagementPrioritiesView across projectsShare the pain wealth

The RequirementsIn picking a partnerAccess to MicrosoftEstablished/Stable CompanyStrict Security requirementsCulturally CompatibleEngage, Work, LeaveBroad knowledge/multi dimensionalEnd to end integrationNo Custom CodeEvidence of what would be delivered

The Solution

The SolutionTime to ImplementNine months – 24 Project Managers –52 Resource Managers – 374 Individual Contributors

Partner Engagement Encourage client self-sufficiency as early as possibleReduce riskDrive measured adoptionSpeed to Market

PaLM Data Maintenan

ce

Demand Managem

ent

Portfolio Managem

ent

Project Initialization and Staffing

Delivery Managem

ent

The Solution Wins

Table?

Use 5 strategic impact questions to evaluate projects and create weekly published priority across whole organization

Clear Priorities

Every Resource in IT is loaded 100% so we can see their entire workload, accounting for leave time and misc work

View across projects

Each Resource is assigned a Primary Demand role which equates to their primary skill set

Skills Analysis

One click to import project estimate from Excel to Resource Plan

Estimate Import

Move a function everyone relies on into your Project Server process

Block Point Release Report

The Solution Challenges

Table?

Importing actual hours worked from our company timekeeping software proved to be a lot of effort with no real value.

Actual Time

Needed to eliminate tool redundancy, and strive towards a seamless automated process. Several tools where eliminated but we have more work to do.

Multiple Tools in the Lifecycle

Needed to track all the work that was approved but didn’t have a real person assigned

Tracking Unmet Demand

The SolutionDemand Management RolesGeneric Demand Resources

The Solution Adoption

Table?

Lots of hand holding, documentation and on-on-one guidance

Huge Cultural Change for some

Asked for by middle management - Mandated by upper management but driven and implemented at the lowest levels.

Involvement at all levels

Find that key element that everyone depends on – for us it was the BPR report

Motivation for adoption

Deployment Approach

Implementation RoadmapMulti-Phased Approach

Goals• Encourage client self-sufficiency as early

as possible• Reduce risk• Drive measured adoption

POC & PILOT BROAD ROLLOUT

The Schedule

Approach DetailsEncourage Self Sufficiency

Reporting

ReportingTimingUnderstand the tool and the reports will follow

Excel ServicesPrioritiesResource ManagementDemand Management (Backlog)Block Point Release

Project January February MarchA12345 - Windows 7 Roll-Out 253.0 - -

Priority (6) | ITR (A12345) Windows 8 Roll-Out 253.0 Named Resource

Smith; Joe 105.0 105.0 141.0 Brown; Mary 72.0 105.0 140.0 Jones; Kevin 72.0 105.0 140.0

Unmet Demand

Systems Engineer.Microsoft 4.0 4.0 2.0

Lessons Learned

Lessons LearnedInclude the thing that everyone relies onNNS Block Point Release report

Don’t force the system to do unnatural actsActuals feed

TrainingProject Managers needed more training than expected

Lessons LearnedUser CommunicationsProject Server facilitates better communication, it doesn’t replace it!

Resource ManagementDon’t go overboard with generic resources!

Non-Project TimeNeed to view all work to understand any of it.

Lessons LearnedReportingBuild reports you will use!

Systems IntegrationEnsure integration is well understood from a business perspective.

Portfolio AnalysisRemember this is advanced functionality that requires a solid PM foundation to apply.

Next Steps

Next stepsProject WorkspacesIntegration with TFSIntegration with HPSMCustom Estimating tool integrationUpgrade! 2013? 2014?

MyPC fill out evaluations & win prizes!

Fill out session evaluations by logging into MyPC on your laptop or mobile device.

Evaluation prizes daily! Claim your prize at the Registration Desk on Level 1.

www.msprojectconference.com

After the event, over 100 hours of resources; including all of the PPT decks and session videos will be available.

© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.