Project Kick Off_HAI

8/10/2019 Project Kick Off_HAI

http://slidepdf.com/reader/full/project-kick-offhai 1/33

<CLIENT>

Project Name

Kick-off Meeting

Month DD, YYYY



2

Agenda

• Project Overview

• Approach and Timeline

• Project Team

• Project Repository

• Meetings and Logistics



3

Project Overview



4

Background and Business Drivers

• Changes mandated for the insurance industry due to the Affordable Care

Act, otherwise known as Healthcare Reform, require a significantly greater

understanding of their financial implications and the ability to respond

rapidly.

• Ability needed to rapidly model potential changes to its business model and

analyze the financial impact as part of the decision-making process.

• Need for an effective set of tools for analyzing costs, cost allocations andtheir drivers, and a consistent methodology as enabled by Hyperion

Profitability & Cost Management.

• SNAP mainframe system used for cost allocation management is at the end

of its lifecycle

• Desire to standardize its system with other <Client> Association members.• <Client> engages in a lengthy and challenging Planning & Budgeting

process that requires significant manual manipulations of data from multiple

external systems



5

Guiding Principles

• Business Driven – all decisions on changes in scope, project duration,

project resources and cost will be based on <Client> business strategies

and objectives.

• Enterprise Wide Design – any decisions regarding functional requirements

by users, technical solution designs and technical architecture will be based

on company-wide requirements.

• Minimal Customizations –

the use of customizations as a solution forfunctional gaps identified during the requirements definition phase will be

minimized. Application configuration and manual work-arounds will be used

were feasible.

• Quality Engineered End-to-End Processes – all business requirements,

technical solutions and application testing should be defined and viewed in

the context of a horizontal business process with a distinct start and end.

• Commitment to Quality – industry standard efforts will be used to monitor

and ensure quality.



6

Scope Area Inclusions Exclusions

Applications/Functions

Oracle EPM 11.1.2 Phase I Products• Hyperion Planning Plus

• Hyperion Workforce Planning

• Hyperion Profitability & Cost

Management

• Financial Data Quality Management

Oracle EPM Components

• EPM Essbase Plus

• Hyperion Web Analysis

• Weblogic Server Standard Edition

• Foundation Services

• EPM Architect

• Hyperion Shared Services

• Hyperion Administration Services• SmartView

• Financial Reporting Services

Oracle eBusiness / Peoplesoft Applications

Hyperion Financial

Management

Hyperion Strategic Finance

Application Scope



Current State Data Flow - Planning







Project Approach and Timeline



Project Approach

Define Design Build SupportTest/

Train



Key Activities

Activity Task

Infrastructure • Design technical architecture• Provision hardware, Software, and establish connectivity

Define Phase • Confirm Scope & Approach

• Refine Project Plans

• Data Cleansing (<Client>)

Design Phase • Develop detailed application design

• Develop detailed training plan (<Client>)

Application Build • Build Metadata/Dimensions

• Build FDM integrations

• Build Web Forms

• Build Calculations

• Build Reports

• Build Security

User Acceptance Testing (UAT)• Test Execution

• Issue Resolution

• Data Validation (<Client>)

End User Training (EUT) • Train-the-Trainer (TITAN)

• Develop materials and train users (<Client>)

Production Readiness • Establish a service support organization

• Establish a team for service delivery (enhancements)



Project Timeline

Project

Phase Activity

Month

Mar

‟11

Apr

‟11

May

‟11

Jun

‟11

Jul

‟11

Aug

‟11

Sep

„11

ALL Phases

Project

Management

Ongoing project oversight

Phase 1 – Hyperion Planning, Workforce Planning, Profitability, & Cost Management, and FDM

SolutionsDefine &

Design

Requirements DefinitionSolution Design

Solution

Build

Application Configuration

& Build Data Interfaces

UAT &

Validation

User Acceptance Testing & Validation

Transition End user training

Establish Production System

Migration Data

Production

Support

Establish support infrastructure

Resolve application issues



Project Milestones

Phase I Milestones Start Complete

Define Solution 28-Feb-11 11-Apr-11

Technical Design 11-Apr-11 12-May-11

Hyperion Build

- Planning 09-May-11 02-Jun-11

-Workforce Planning 16-May-11 17-Jun-11

- Financial Data Quality Management 02-May-11 17-Jun-11

- Hyperion Profitability & Cost Management 16-May-11 24-Jun-11

Build Test System 06-Jun-11 15-Jul-11

System Integration & Acceptance Testing 16-Jul-11 29-Jul-11Build Production System 08-Aug-11 12-Aug-11

Production System Readiness 19-Aug-11 05-Sep-11

Parallel Processing Period (as needed) 05-Sep-11 01-Jan-12



Project Team



Business Units and

Operations

Core business process redesign,

change management, training

Communications and

Change Management

Corporate message, image,

goals, standard communications

Information Technology

Team

Systems standards, integration,

feasibility, risk, resource planning

Application Subject

Matter Experts

Knowledge of process redesign,

Web technologies, legacy integration

and project management / planning

Executive Sponsorship /

Steering Team

Business vision and project

empowerment

Leadership Team Composition and Roles

Business vision and project

empowerment

Team Leadership



Project Team Organization

Insert PTO Diagram



Project Responsibilities

Steering Committee

• Provides key direction for the project

• Approves project change request and scope changes

• Resolves strategic issues conflicts

• Communicate, approve and manage expectations and success

indicators

• Meets on a regular basis, based on project milestones to discuss

– Status

– Decisions

– Open Issues

– Key Risks



Project Roles and Responsibilities

Project Manager

• Develop and maintain the master project plan

• Manage and coordinate required staffing and assignments with all

project resources

• Manage both on site and off site resources

• Work with senior management for all change management issues

• Facilitate and track task progress against percent completion on

detailed work plan

• Deliver status reports to all involved resources



20

Project Roles and Responsibilities

Work Stream Leads / Members

• Define business requirements for each functional area

• Participate in design and setup decisions

• Define data conversion plan and perform validation testing

• Receive training on new and changed functionality

• Resolve business process decisions

• Assist in the development of test scripts and conduct/approve all

testing certifications

• Will need to devote higher level of time commitment during time

intensive periods such as testing and training



21

Project Responsibilities

TITAN Consultants

• Partner with Work Stream Leads

• Conduct process modeling workshops and document future model

business requirements and recommend best practice process

design

• Configure the Hyperion applications

• Create functional specifications for all interfaces and development

needs

• Define testing scenarios and support user testing

• Oversee the functional conversion to production

• Knowledge transfer to “super -users”



22

Oracle OnDemand

Host and manage the technical application components, including:

• Database Administration

• Database & Application Patching

• Hyperion System Administration

• Application Refreshes

• System Backups

• Infrastructure and Database Security (does not include application)

• Infrastructure Support

• Database, System, and Network monitoring



23

Project Meetings and Logistics



24

Project Repository

• The shared directory is:

I:\Corporate Projects\Active Projects\Hyperion (1104100)

• All project deliverables will be maintained in the repository

• Deliverables are created and owned by the team leaders

• Each person must

submit his/her ownaccess request.

• Guide lines and

common sense for

Confidential

information mustbe followed



25

Weekly Status Meeting

• Occurrence: Weekly, <Date> at <Time>

• Facilitator: <Name>

• Participants: Team Leads, Project Managers

• Objectives:

– Communicate project tasks status from team leads to project managers – Resolve team escalated issues

– Two week outlook review



26

Workstream Team Meetings

• Occurrence:

– Planning – Monday 2:30 – 3:30pm

– HPCM – Monday – 3:30 – 4:30pm

– Technical / FDM – 1 pm

• Facilitator: Workstream Leaders

• Participants: Team Members

• Objectives:

– Ensure project tasks and activities are on target

– Resolve issues/roadblocks



27

Steering Team Meeting

• Occurrence: <Frequency> as scheduled

– (1 hour duration, based on milestones)

• Facilitators: Project Manager

• Participants: Project Managers, Steering Committee

Members & Executive Sponsors

• Objectives:

– Communicate overall project status

– Discuss key project risks

– Resolve issues/roadblocks requiring executive attention – Ensure on-track status for meeting strategic objectives`



28

Issue Log

• No issue is too small

• All issues will be assigned to an owner

• All issues require timely resolution



29

Issue Resolution

1. Raise and Capture

– All team members can raise issues.

– Submit your issue to the Joe Ingermanson and Peter Nosek

2. Investigate the Issue

– PM will assign the issue to an owner to investigate

3. Recommend and Resolve

– Owner will recommend action

– All closed issues require resolution

4. Escalation (to Steering Team) – Issues affecting scope and/or budget

– Issues affecting project schedule

– Disagreement regarding action or disposition of an issue.



30

Critical Success Factors

Strong executive sponsorship and steering committee support of the

project mission and project team

Adequate project staffing for the expected goals and timeline to be

met

Clear roles and responsibilities defined for the project in order to

assure accountability, ownership, and quality

A defined and maintained project infrastructure throughout the

project duration

A thorough understanding of known project risks and assumptions

throughout the executive committee and project team

Timely approval of deliverables by <Client>‟s Project Sponsor



31

Project Name Contest

Your chance to make a name for ourproject!

Submit your suggestions for a

project name to <Client PM> The project leadership will

anonymously select the name

A prize goes to the winner!



32

Q & A



CONTACT US

North America

+1 888 430 9252

EMEA +44 870 770 9842

Asia Pacific

+65 6749 1788

t t p a r t n e r s . c o m

Documents

Project Kick Off_HAI