abc inet pm plan

8/2/2019 ABC Inet Pm Plan

1/44

ABC I-Net

Sample Project Management Plan

Upgrading the ABC Intranet and

ABC Internet Infrastructures

Note: This is a real document provided by a

real project team. Names have been changed

to sanitize the document.

Last Updated: 10/09/2001

Prepared By: ABC I-Net Project Team

Version 1.9


2/44

Sample Project Management Plan DRAFT

Page: 2

Table of Contents

TABLE OF CONTENTS...................................................................................................................2

I. EXECUTIVE SUMMARY (DEFINITION) .........................................................................4

II. BENEFITS (BUSINESS REQUEST).................................................................................................5

III. SCOPE (BUSINESS CASE)..................................................................................................................6

A. In Scope .................................................................................................................................................6

B. Out of Scope..........................................................................................................................................8

C. Project Dependencies ...........................................................................................................................9

D. Project Goal and Objectives................................................................................................................9

E. Project Deliverables..............................................................................................................................9

F. Acceptance Criteria............................................................................................................................11

E. Assumptions........................................................................................................................................11

F. Constraints..........................................................................................................................................12

IV. CRITICAL SUCCESS FACTORS..........................................................................13

V. COST ESTIMATES(FINANCIAL BUSINESS CASE)...............................................14

A. Total Budgeted Costs for Hardware and Software:........................................................................14

B. Phase-I Intranet Budgeted Costs for Hardware and Software: .....................................................15

C. Phase-II Internet Budgeted Costs for Hardware and Software:....................................................15

VI. APPROACH STRATEGY .............................................................................................16

D. Technique/X Project Management ...................................................................................................17

X. WORK BREAKDOWN STRUCTURE............................................................18

IX. PROJECT PLAN..........................................................................................................................19

X. PROJECT TEAM................................................................................................................... 20

A. Organizational Breakdown Structure ..............................................................................................20

B. Project Roles and Responsibilities ....................................................................................................21

C. Project Roster .....................................................................................................................................25

XI. RISK MANAGEMENT.....................................................................................................27


3/44


Page: 3

XII. GOVERNANCE PLAN................................................................................................28

XIII.

PROJECT CONTROL STRATEGIES.........................................................29

A. Quality Assurance ..............................................................................................................................29

B. Change Control...................................................................................................................................29

C. Communications.................................................................................................................................29

D. Information Management..................................................................................................................30

XIV. APPENDIX A - INITIAL PROJECT RISK ASSESSMENT...........................32

XV. APPENDIX B COMMUNICATIONS MATRIX ...............................................42

XVI. APPROVAL SIGNATURES....................................................................................44


4/44


Page: 4

I. Executive Summary (DEFINITION)

The ABC Intranet and the ABC Internet have gone through many changes over the

course of the past year. The primary reason for making such changes is to align with I-

Nets mission statement that states that we will provide our customers with reliable,

integrated, secure and flexible I-Net solutions to meet their expanding business needs.

As a next step in keeping with this mission statement, the I-Net group determined that

there is a need to enhance the existing ABC Intranet and ABC Internet infrastructure,

policies and procedures, and security to meet current and future business needs.

More specifically, the ABC Intranet and ABC Intranet will be expanded and modified to

provide like environments through common software configurations, like processes

through standard policies and documentation (where appropriate), common security

measures, and greater capacity with added hardware.

The overall project approach will be to follow industry standard project management

practices that will break the project down into two phases:

Phase-I ABC Intranet

Phase-II ABC Internet

It should be noted that there is the potential for additional add-on phases to address theitems that have been categorized under Future Considerations (beyond phase-II). The

Future Consideration items will be reviewed and categorized accordingly as part of the

Sample Charter project. Any items that are deemed part of the Phase-I and/or Phase-II

will be incorporated through the Sample Charter project Change Control processes.


5/44


Page: 5

II. Benefits (BUSINESS REQUEST)

Upon completion of the Sample Charter Project, ABC will realize the following benefits:

An Intranet and Internet infrastructure that leverages standards for technical

configuration, technical management, and procedures to provide optimum

proficiency.

Provide an infrastructure that allows ABC business units to properly house their

Intranet and Internet applications.

Alleviate current production capacity issues.

Increased capacity (up to 100%) to accommodate ABC business units future

business growth needs.

A standardized infrastructure and procedures will allow for easier and more efficient

Intranet and Internet support.

Updated process definitions as a result of the new architecture will provide better

ease of use for users.


6/44


Page: 6

III. Scope (BUSINESS CASE)

A.In Scope

1. PHASE-I ABC Intranet

a) Enable the I-Net tool set (Actuate, Harvest, iPlanet, SiteMinder, andWebsphere) to function on the new ABC Intranet.

b) Architect, design and build the new ABC Intranet in such a way that theinfrastructure supports the following environments: DEV, INT, IMPL,

TRAIN, and PROD.

c) Migrate the following applications from the existing ABC Intranet and/orABC Internet to the new ABC Intranet:

i. Conswakoii. Technique/Xiii.State Farmersiv. U.S. News and Daily Reportv. Migrate the Visual Age Generator (VAGEN) application from

the existing ABC Intranet environment to the new ABC

Intranet environment.

d) Architect the new ABC Intranet in such a way that the ABC Internetdatabases (DB2, data warehouse, NEON, ORACLE, etc.) can be accessed

from the new ABC Intranet

e) Provide flexibility in the new ABC Intranet Production Control process toaccommodate different levels (static content and application code) of code

migration.

f) Enable domain-naming capabilities so that each Intranet application mayutilize a specific domain name (ex. usnews.ABC.com).

g) Secure the HOST system log files for the new servers and the redeployedexisting servers.

h) Implement a standard HOST configuration (see appendix A) for the newservers and the redeployed existing servers.

i) Implement a standard APPLICATION configuration (see Appendix A) forthe new servers and the redeployed existing servers.


7/44


Page: 7

j) Implement time-sync software for the new and redeployed I-Net servers.

k) Re-rack the new servers and redeployed existing servers.

l) Update appropriate ABC Intranet processes and procedures impacted byIntranet changes and necessary to support the new ABC Intranet

infrastructure (ex. shared components).

m) All exiting software applications and software tools will remain as is forthe existing ABC Intranet (servers u1ecm04 and u1ecm05) unless

otherwise noted in the Project Charter.

n) Required documentation to meet Technique/X minimum deliverablerequirements is completed.

2. PHASE-II ABC Internet

a) Scale the production Websphere Infrastructure to provide approximatelydouble the storage and processing capacity.

b) Provide additional fault tolerance and redundancy to decrease businessinterruptions due to unplanned downtime.

c) Provide migration processes (i.e. anytime migration not just scheduledSundays) for the new ABC Intranet and ABC Internet that will result in

minimal downtime.

d) Provide increased flexibility in the DEV, INT, IMPL, and TRAINenvironments to allow for a load testing environment and separate DEV

environments for each business.

e) Create a TECH environment to allow the I-Net Department to conduct anddirect research and analysis of Internet applications, fixes, tools, and

upgrades.

o) Secure the HOST system log files for the new servers and the redeployedexisting servers.

p) Implement a standard HOST configuration (see appendix A) for the newservers and the redeployed existing servers.

q) Implement a standard APPLICATION configuration (see Appendix A) forthe new servers and the redeployed existing servers.

r) Implement time-sync software for the new and redeployed I-Net servers.


8/44


Page: 8

s) Required documentation to meet Technique/X minimum deliverablerequirements is completed.

3. Future Considerations (beyond Phase-II)

a) Consolidate webservers where appropriate to maximize the new ABCIntranet and ABC Internet efficiencies while maintaining the high-level

company domains.

b) Research, analyze, and reconfigure the deployment of the u1ecm04 andu1ecm05 servers (existing ABC Intranet).

c) Secure APPLICATION log files (Apache, Websphere, and iPlanet) andHOST log files for the remaining I-Net servers.

d) Implement the Solaris v.2.8 operating system on the remaining I-Netservers.

e) Implement a base server configuration on the remaining I-Net servers.

f) Re-rack the remaining I-Net servers.

g) Use of mainframe platform within the ABC Intranet and ABC Internetinfrastructure.

B.Out of Scope

1) The research and evaluation of alternative tools as possible replacements forFront Page, Harvest and Host Publisher.

2) The infrastructure changes required eliminating single points of failure.

3) The upgrade and fail-over of the Media Surface content management tool.4) The LDAP Directory Strategy Design and Implementation.

5) Eliminate identified security weaknesses in the existing ABC Intranet and ABCInternet infrastructure.


9/44


Page: 9

C.Project Dependencies

1) The Sample Charter Project is dependent on the SiteMinder Upgrade project tomaintain compatibility and to complete final testing.

2) The Sample Charter Project is dependent on the Harvest 5.0 Upgrade project forany Production Control Processes changes.

D.Project Goal and Objectives

1) Implement fault tolerance and redundancy (no downtime for most productionmoves)

2) Implement full functions on the Intranet (security, application, multipledevelopment regions)

3) Implement doubling of I-Net capacity

4) Implement separate DEV environments for each company

5) Implement scalable infrastructure for future growth

6) Implement I-Net TECH environment for R&D

7) Establish common technical and process standards

E.Project Deliverables

The following Project Delivery Table provides a project timeline with estimated project

delivery dates for key project milestones.

Project

Deliverable 9/15 9/30 10/15 10/31 11/15 11/30 12/15 12/31 1/15 1/31 2/15 2/28 3/15 3/31 4/15 4/30

1.1 PROJECT

MANAGEMENT

Project Charter Sign-

off

10/19

Project RAF Sign-off 10/19

Project Plan 10/12


10/44


Page: 10

Project

Deliverable 9/15 9/30 10/15 10/31 11/15 11/30 12/15 12/31 1/15 1/31 2/15 2/28 3/15 3/31 4/15 4/30

Baselined

Technical Kick-offMeeting

9/18

Business Kick-off

Meeting

9/27

1.2 ANALYSIS

Hardware/Software

Negotiations

Complete

8/24

Receive Hardware 9/10

Project Phases

Defined

8/31

Business

Requirements Sign-

off

11/1

TechnicalRequirements Sign-

off

8/31

Procedure Updates

Sign-off

11/8

1.3 DESIGN

Hardware Design

Sign-off

10/2

Software Design

Sign-off

10/2

1.4 BUILD

Facilities Prep

Completed

9/25

Server Installation

Prep Completed

10/9

TECH Test

Environment Prep

Completed

11/19

Phase-I Intranet

Hardware Install

Completed

11/5

Phase-I Intranet

Software

Configuration

Completed

1/4

Phase-II Internet

Hardware Install

Completed

12/5

Phase-II InternetSoftware

Configuration

Completed

2/5

1.5

INTEGRATION/

TEST

Business Test Plans

Created

11/15

Technical Test Plans 10/26


11/44


Page: 11

Project

Deliverable 9/15 9/30 10/15 10/31 11/15 11/30 12/15 12/31 1/15 1/31 2/15 2/28 3/15 3/31 4/15 4/30

Created

User AcceptanceTesting Sign-off

1/24

Technical

Acceptance Testing

Sign-off

12/4

1.6 PRODUCTION

CUT-OVER

Phase-I Intranet

Cutover

2/14

Phase-II Internet

Cutover

3/7

Management

Reserve

4/16

F.Acceptance Criteria

The project plan takes into account a project task for sign-off on each milestone within

the project. At the time of milestone sign-off, the appropriate business stakeholder

and/or technical stakeholders will participate in the review/sign-off meeting(s).

The primary reason for this is to demonstrate project progress as well as receive

acceptance from the project stakeholders as we progress through the project timeline.

E.Assumptions

1) Users who have rights to Front Page in the existing ABC Inc. Intranetenvironment will maintain the same Front Page rights through the continued use

of the existing ABC Intranet environment.

2) Users who have access to the Host Publisher tools in the existing ABC Intranetenvironment will maintain same Host Publisher Tolls access capabilities through

the continued use of the exiting ABC Intranet environment.

3) All identified project risks are mitigated at the start of the project.

4) All scope changes will follow the Change Control Process and be approvedthrough the Executive Steering Committee as needed.


12/44


Page: 12

5) The assigned project resources are available to complete project tasks asscheduled within the project plan

6) The existing ABC Intranet will exist in its current state until a decision is made tomigrate to the new ABC Intranet.

F.Constraints

1) Assigned resources may be redirected as a result of current production issues.

2) Change Control decisions will be prioritized by impact on schedule, cost, andfeature/functionality.


13/44


Page: 13

IV. Critical Success Factors

The key elements that must be in place to ensure the success of this project are as

follows:

The facility preparation to accommodate the additional hardware and software

required for the Sample Charter project is completed by 9/14/2001.

The procurement of the necessary hardware and software components for the Sample

Charter project is secured by 9/21/2001.

The procured hardware and software required is delivered on time and as planned.

Assigned resources work activities are prioritized in such a way that project work can

be completed on time

Participation, influence and leadership from project sponsor and business project

leads including decision making, and issues resolution in a timely and effective

manner

Scope must be managed with the tightest controls. Escalated change requests must be

approved by the Executive Steering Committee

Timely and effective management of project risks

Manage within the project budget funding

Active Executive sponsorship


14/44


Page: 14

V. Cost Estimates(FINANCIAL BUSINESS CASE)

A.Total Budgeted Costs for Hardware and Software:

ar ware ervers o tware cense

Netra Netra AC200 250 280 450 420 WebSphere IPlanet Actuate Edge Server OracleTechnical Environement: 2 0 2 0 2 0 4 2 2 1

Development 1 1 1 1 0 0 3 2 3 0

Integration 0 1 2 0 0 0 4 2 0 0

Implementation 2 2 1 3 0 1 6 2 0 2

Training 0 2 1 0 0 2 2 4 0 0

Development/Training Environment: 3 6 5 4 0 3 15 10 3 2

Production Environment: 4 5 2 6 0 5 12 10 2 4

Servers needed as a Result of Repurposing

the 420s servers (used for Proxy Servers): 4 12 0 0 0 0

Subtotal Unit Count of Hardware/Software: 13 23 9 10 2 8 31 22 7 7 0

Total Count of Fortis Owned Equipment: 17 0 9 0 0 8 12 5 5 6

Net Total Unit Count of Hardware/Software

(subtotal - Fortis owned): 0 23 0 10 2 0 19 17 2 1 0

Approximate Unit Costs: $11,000 $46,000 $42,000 $6,032 $1,400 $50,000 $8,000 $50,000

Subtotal Costs: $253,000 $460,000 $84,000 $114,608 $23,800 $100,000 $8,000 $0

Hardware/Software TotalsTotal Number of New Servers: 35

Total Cost of New Servers: $797,000Total Cost of Additional Software Licenses: $346,4082 Additional CPUs for Database HA Server: $20,000

Rack kit for 450s: $16,000

Grand Total: $1,179,408

0

0

0

0

0

0

0

0


15/44


Page: 15

B.Phase-I Intranet Budgeted Costs for Hardware and Software:

C.Phase-II Internet Budgeted Costs for Hardware and Software:


16/44


Page: 16

VI. Approach Strategy

One of the primary principles behind the Approach Strategy for the Sample Charter

project is to establish a project foundation that follows proven industry standards for the

following Project Management Life Cycle Phases:

Project Initiation

Project Planning

Project Execution

Project Control

Project Close-Out

By following an industry standard Project Management Life Cycle the project team is

effectively managing risk in the area of how the project will project managed.

In addition, the project will follow the Technique/X (MAGNUS) Project Life Cycle as a

way to effectively organize, manage, and track project work. As with the Project

Management Life Cycle, by following an industry standard Project Life Cycle the project

team is effectively managing risk in the area of project work.

Also, the project team will fast track (run in parallel) project tasks at the start of the

project as a way to move things along more quickly. Only project tasks that have

minimum risk and provide optimum return will be fast tracked.

Finally, the project team will start early to develop appropriate and adequate test plans to

ensure that the appropriate unit testing, system integration testing, regression testing

(where applicable) and User acceptance testing is conducted. User training through

documentation and classroom training will be provided as determined by the project

team. A detailed synchronized implementation plan will be developed that covers all

dependencies and linkages in an effort to help coordinate the final production rollout.


17/44


Page: 17

D.Technique/X Project Management

The Project Management practices for the Sample Charter project will adhere to the ABC

Technique/X (MAGNUS) Project Management Methodology. The primary reason for

this is to ensure that the ABC Technique/X minimum project deliverables are achieved.

By following an industry standard Project Management methodology the Sample Charter

Project will be managed in such a way that consistent practices for both business and

technology are followed. This will provide a common approach, verifiable project

deliverables, and clearly defined project roles and responsibilities.

These practices will achieve a balance between competing stakeholder needs and

managing expectations related to scope, time, cost, and quality.

Plan ProjectExecution

Project Plan-Project Schedule-Project Risk Mgmt Rpt

OrganizeProject

Resources

Define and Mana e Business CaseBusiness Case

-Busines Case Economics

ReportProjectStatus

Project Status Rpt Pkg

ControlProject Work

Issue or Open Pt.Project Change Request

Manage the Testing Effort

Iterate as required

PrepareProject

CompleteProject

Final Project Report

Manage the Infrastructure

Technique X

Project Management


18/44


Page: 18

X. Work Breakdown Structure

ProjectWork Breakdown Structure

As of: 9/21/2001

1.2 Analysis 1.3 Design1.1 Project Management

1.1.1 Project Charter

1.1.1.1 Benefits

1.1.1.2 Cost Estimate

1.1.1.3 Scope

1.1.1.4 Project Approach/Strategy

1.1.1.5 Define ProjectTeam

1.1.1.7 Governance Plan

1.1.1.8 Project Plan

1.1.1.9 Control Strategy

1.1.1.10 Risk Assessment

1.2.1 ProjectPhase Definition

1.2.1.1 Phase-I ABCCo.Net

1.2.1.2 Phase-II Internet

1.2.2 BusinessRequirements

1.2.2.2 ABC

1.2.3 Technical

Requirements

1.2.5 ProcedureChanges

1.3.1 HardwareDesign

1.3.3 SoftwareDesign

1.4.1 CreateBranch

1.4.2 PrepareFacilities

1.4.2.1 Data CenterSpace

1.4.2.2 SANConnections

1.4.2.3 NetworkConnections

1.4.3 Prepare forServer Installs

1.4.3.1 Rack/StackServers

1.4 Build

1.4.3.2 JumpstartServers

1.5.1 Create TestPlans

1.5 Integration/Test

1.6.1 Phase-I ABCCo.Net

1.6 Production COver

1.6.3 Phase II -Internet

1.2.3.1 Phase-I ABCCo.Net / Phase-II

Internet

1.4.5 Phase-I BuildABC Co.Net

1.4.5.1 Build Servers

1.4.5.2 Build Software

1.5.1.1 BusinessTest Plans

1.5.1.2 TechnicalTest Plan

1.5.2 Phase-I ExecuteTest Scripts

1.5.2.1 BusinessTest Scripts

1.5.2.2 TechnicalTest Scripts

1.1.1.6 OrganizationalBreakdown Structure

1.1.2 Kick-OffMeetings

1.1.4 Project RAF

1.2.2.3 FBXC

1.2.2.4 ABC Co. Family

1.2.2.5 ABC Co. Health

1.2.2.6 Hartland

1.2.2.7 ABC Co. Inc.

1.2.4 SoftwareRequirements

1.2.4.1 Phase-I ABCCo.Net / Phase-II

Internet

1.2.6 OrderHardware/Software

1.4.5.3 MigrateApplications

1.4.6 Phase-IIInternet

1.4.6.1 Build Servers

1.4.6.2 Build Software

1.5.3 Phase-IIExecute Test Scripts

1.5.3.1 BusinessTest Scripts

1.5.3.2 TechnicalTest Scripts


19/44


Page: 19

IX. Project Plan

The following project plan provides a timeline that assumes no new resources added to the project.

D Task Name % Finish1 1 Project 0% Tue 04/16/022 1.1 Project Management 0% Tue 04/16/023 1.1.1 Project Charter 0% Tue 10/16/01

48 1.1.2 Project Kick-Off Meetings 0% Thu 09/27/0154 1.1.3 Project Meetings 0% Fri 04/05/0258 1.1.4 Document the RAF 0% Mon 10/08/0159 1.1.5 Management Reserve Based on Initial Risk Assessment 0% Tue 04/16/02

60 1.2 Analysis 0% Thu 11/08/0161 1.2.1 Define Project Phases 0% Tue 09/04/0169 1.2.2 Business Requirements 0% Fri 10/19/0101 1.2.3 Technical Requirements 0% Tue 10/09/0107 1.2.4 Software Requirements 0% Tue 10/23/0122 1.2.5 Document Procedure Changes 0% Thu 11/08/0145 1.2.6 Order Hardware/Software 0% Fri 09/28/0150 1.3 Design 0% Fri 10/19/0151 1.3.1 Hardware Design 0% Tue 09/11/0155 1.3.2 Software Design 0% Tue 10/02/0159 1.3.3 Prepare for Architectual Design Review 0% Fri 10/19/0160 1.3.4 Conduct Architectual Design Review 0% Fri 10/19/0162 1.4 Build 0% Tue 02/05/02

63 1.4.1 Create Second Branch to Resolve PROD Load Issue 0% Fri 10/19/0178 1.4.2 Prepare Facilities for New Hardware/Software 0% Fri 09/28/0199 1.4.3 Prepare for Server Installations 0% Fri 10/12/0111 1.4.4 Validate software/system requirements 0% Mon 09/10/0112 1.4.5 Phase-I Build isNet 0% Tue 01/15/0278 1.4.6 Phase-II Build Internet 0% Tue 02/05/0272 1.5 Integration/Test 0% Thu 02/14/0273 1.5.1 Create Test Plans for ALL Phases 0% Thu 11/15/0105 1.5.2 Execute Test Scripts for Phase-I Net 0% Thu 01/24/0230 1.5.3 Execute Test Scripts for Phase-II Internet 0% Thu 02/14/0255 1.6 Production Cut-Over 0% Thu 03/07/0256 1.6.1 Cut-Over Phase-I sNet to Production 0% Thu 02/14/0260 1.6.2 Cut-Over Phase-II Internet to Production 0% Thu 03/07/02

0%0%

0%

0%0%

0%0%

0%0%

0%0%

0%0%

0%10/19

0

0%0%

0%0%

0%

0

0%0%

Aug Sep Oct Nov Dec Jan Febuarter 4th Quarter 1st Quarter


20/44


Page: 20

X. Project Team

A.Organizational Breakdown Structure

AProject Lead

DProject Lead

Team Member

AProject Lead

b

BProject Lead

Project Steering CommitteeJon Doe

s

I-Net Relationship Managers

Project Manager

Project Auditor

Team MemberProject Sponsor

I-NetManager

Technical ArchitectTeam Lead

I-Net Manager I-Net Manager

I-Net OperationExpert

Security Expert

Production ControlExpert

Open SYstemsSupport

Team Lead

Lead EngineerTBD

Oracle DBA Expert

Middleware Expert Network ExpertOpen SystemsSupport

CProject Lead

EProject Lead

Team Member

AProject Lead

AProject Lead

Team Member Team Member

AProject Lead

Project Organizational Breakdown Structure as of 10/05/2001

Team MemberF

Project LeadF

Project Lead

I-Net Tools Support


21/44


Page: 21

B.Project Roles and Responsibilities

Sample Charter ProjectRoles and Responsibilities Matrix

Individual(s) Role Responsibilities

Project Sponsor Project Champion

Offer strategic business leadership and direction

Provide Communication bridge to outside the

project Senior Management

Scope change approval

Budget variance approval

Removes project barriers

I-Net

Relationship

Managers

Executive SteeringCommittee

Scope change approval Offer strategic business leadership and direction

Remove project barriers

Project Manager Manage daily project tasks

Manage project deliverables, resources, andschedule

Track project progress to plan and manage the

project plan

Facilitate project communication, project

decision making, project issue resolution, and

project risk management

Facilitate Monthly Executive Steering

Committee meetings

Review project deliverables, facilitate

adjustments as needed, and facilitate change

approval

Issue and Change management log owner

Project Status Report author

Testing site auditor/QA

I-Net AccountManagers

Ensure that the business needs are met Communicate project scope/objectives to

business I-Net customers

Obtain testing resources from the businesses

FBIC

Business Project

Leads

Act as project contact for the business

Provide leadership in the coordination of

assigned project tasks for business team

members


22/44


Page: 22


ABC Family

ABC HealthHartford

ABC Inc.

ABC IT

Provide business requirements input, test

planning, test execution, and User Acceptancetesting sign-off

Provide business sign-off for project milestones

as needed

Ensure that the appropriate business resources

are available to meet project schedule and

project deliverables

Business Team

Members

Provide business content expertise

Provide input to business requirements

Provide input to business test planning

Conduct test script execution

Provide documentation as required for theproject

Project Auditor Provide independent assessment of projectactivities and issues

Provide audit standards guidelines and

enforcement where needed and appropriate

Provide documentation as required for the

project

Technical

Architect,

Technical Lead


assigned project tasks for the technical team

Provide technical architect and design expertise Ensure that the architected designs fit within

ABC strategic infrastructure vision

Provide technical sign-off for project milestones

as needed


project

Open Systems

Support, Technical

Lead

Act as the project contact for the Open Systems

Support area


assigned project tasks for the Open Systems

Support area

Provide Unix operating system expertiseImplement Unix hardware configuration and

setup

Implement system software configuration and

setup

Insure that all ABC standards are met (i.e. base

configuration, security audits, etc.)


23/44


Page: 23


Provide technical sign-off for project milestones

as neededEnsure that the appropriate Open Systems

Support resources are available to meet project

schedule and project deliverables

1st line of support for all project issues related

above responsibilities


project

I-Net Operations

Expert

Provide technical expertise in the area of

Websphere configuration and setup

Provide technical expertise in the area of Apache

server, Application server, NFS server, and Webserver configuration and setup

Provide technical expertise for the configuration

and setup of appropriate software for the various

server types

Provide technical expertise for SiteMinder agent

Provide technical expertise for load balancing

Provide input to technical test plan

Conduct technical testing as required

1st

line of support for all project issues related



Security Expert


and setup for SiteMinder

Provide technical expertise for SiteMinder agent


and setup of iPlanet



1st

line of support for all project issues related



Production Control

Expert


and setup of Harvest



1st line of support for all project issues related



24/44


Page: 24



projectTBD Lead Engineer

Provide technical expertise in the area of Load

testing

Provide input to the technical test plan for Load

Testing

Complete technical tasks as related to the setup,

configuration, and testing of Load testing as

related to the new ABC Intranet and ABC

Internet


project

Oracle DBAExpert

Provide technical expertise in the area of Oracledatabases as related to the new ABC Intranet and

ABC Internet infrastructures


configuration, and testing of the Oracle

databases as related to the new ABC Intranet and

ABC Internet


project

Network Expert

Act as the primary project contact for all

network related issues/questions

Provide technical expertise in the area ofnetwork administration, components, and

implementation


configuration, and testing of the network as


Internet


project

Middleware

Expert

Act as the primary project contact for all

Middleware issues/questions

Provide technical expertise in the area ofMiddleware coding, components, and

implementation


configuration, and testing of the Middleware as


Internet



25/44


Page: 25


project

I-Net ToolsSupport

Act as the primary technical contact for thebusiness units during the life of the project

Provide business application support during

application migration and testing

Complete support tasks as related to the setup,

configuration, and testing of the business

applications as related to the new ABC Intranet

and ABC Internet


project

C.Project Roster

All project resource phone numbers and email addresses are outlined in the table

below. This information will be used as the best means of communication for the

team and other key resources for the project.

Name Department Project Role Work Phone Pager/CellPhone

Home Phone

Internet Address

Assurant Business Project

Lead

N/A N/A

I-Net Production

Control Expert

N/A

I-Net Technical

Architect

N/A

Open Systems

Support

Open Systems

Support Expert

N/A

Corporate

Security

Executive

Steering

Committee

N/A N/A

Open Systems

Support

Executive

SteeringCommittee

N/A N/A

Audit Services Project Auditor N/A N/A

I-Net Project Sponsor N/A

I-Net Tools I-Net Tools

Support

N/A

Data Center

Operations

Executive

Steering

Committee

N/A

I-Net I-Net N/A


26/44


Page: 26

Name Department Project Role Work Phone Pager/Cell

Phone

Home Phone

Internet Address

RelationshipManager

I-Net Tools I-Net Tools

Support

N/A

I-Net I-Net

Relationship

Manager

N/A

FBX Business Project

Lead

N/A

ABC Health Business Team

Member

N/A

I-Net I-Net

Operations

Expert

N/A

I-Net Services Stakeholder N/A


27/44


Page: 27

XI. Risk Management

The project risks will be identified at the start of the project and the impact of realizing the risks

will be factored in as part of the project plan planning process (management reserve). Each risk

will be assessed, prioritized, and rated. Such an approach provides a means to track risks, and

more importantly a means to proactively work to prevent them from negatively impacting the

project.

In addition, risk trigger points will be identified and mitigation strategies documented. As risks

are realized, the risk will be logged as an issue and then tracked through the change control

process (if required) until the risk is mitigated.

Also, new project risks will be identified and logged throughout the life of the project. As new

risks are discovered, the risk is logged as an issue and follows the issue management processes.

If deemed necessary, a risk assessment will be conducted for the issue and factored into the

project plan. All risks will be managed at the project team level unless escalated to the

Executive Steering Committee.

Detailed information outlining the initial Risk Assessment for the Sample Charter Project is

provided in Appendix A of the Sample Charter Project Charter document.


28/44


Page: 28

XII. Governance Plan

Issue Escalation

Issues will surface weekly, if not daily throughout the course of the project.

Effective issue tracking and resolution are critical to the success of the project.

The following issue escalation process is recommended:

Tier 1 Project Team to Project Manager

Project Team members escalate issues to the Project Manager who in turn will

document the issue(s) on the Issue Tracking Log. The log is reviewed weekly by

the Project Manager to ensure issues are being appropriately addressed andclosed.

Tier 2 Project Manager to Project Team

The Project Manager escalates issues to the Project Team for further discussion in

an effort to clarify and/or resolve issues. The Project Team will assist the Project

Manager in resolving the issue, if possible. If resolved, the Project Manager will

update the Issue Tracking Log and close the issue.

Tier 3 Project Manager to Project Sponsor

The Project Manager escalates issues to the Project Sponsor to ensure that ABC

management members are fully aware of unresolved critical issues. The ProjectSponsor will assist the Project Manager in resolving the issue, if possible. If

resolved, the Project Manager will update the Issue Tracking Log and close the

issue.

Tier 4 Project Manager to Executive Steering Committee

The Project Manager escalates the most sensitive and urgent issues to the

Executive Steering Committee to ensure that the appropriate ABC senior

management members are fully aware of unresolved critical issues. The

Executive Steering Committee will assist the Project Manager in resolving the

issue, if possible. When resolved, the Project Manager will update the Issue

Tracking Log and close the issue.


29/44


Page: 29

XIII.Project Control Strategies

A. Quality Assurance

Milestone reviews by the business and technical teams will be presented during the weekly

team meetings. Tight controls and metrics will be utilized to manage scope, budget and

timeline through dedicated task management from the Project Manager, a detailed project

measurement tool, and the change request approval process.

B. Change Control

All changes to the Sample Charter project will be reviewed and approved by the Executive

Steering Committee. All approved changes will be added to the Project Charter document

and be identified as an approved Change request.

Detail Change control information will be documented in the Sample Charter Change

Request MAGNUS and maintained within the Sample Charter Change Control Log. The

Change Control process and definition is outlined and explained within the Sample Charter

Change Control Plan.

In addition, the following Change Control rules apply:

At any time, any team member may submit a Project Change Request (PCR)

to the Project Manager.

The Project Manager is responsible to assess and present the PCR to the

technical and core project teams for review.

The Project Manager is responsible for maintaining the Sample Charter

Change Control Log.

C. Communications

Status Reports

Status reports will be submitted by the Project Manager to the Sample Charterproject team members on a weekly basis (bend of business every Tuesday).

In addition, a copy of the weekly status report will be submitted to the appropriate

ABC management team as indicated in the Sample Charter Communications

Matrix (see appendix B).


30/44


Page: 30

These reports provide a snapshot of weekly accomplishments, tasks to complete

for the next reporting period, milestones reached, project issues, and PCRs in

progress.Input by project team members will be provided as part of the weekly core team

and technical team meetings. Project team members will provide the necessary

information to complete the weekly snapshot for their area of responsibility.

Meetings

Meetings for the Sample Charter project will be conducted under the following

format:

Core Team Meetings

Core team meetings will include technical team leads, business project teammembers, and will meet on a weekly basis. The core team meeting will be a

primary vehicle for project communications and decision-making.

Technical Team Meetings

Technical team meetings will include technical team leads, technical team

members, and will meet on a weekly basis. The technical team meeting will

be a primary vehicle for project communications and decision-making.

Executive Steering Committee Meetings

Executive Steering Committee meetings will meet on a monthly basis as a

way to communicate project progress to ABC senior management. Additional

meetings may be scheduled as required based upon project issues resolutionand change control needs.

Additional Meetings

Additional meetings will be scheduled as required.

E-Mail

E-mail will be the primary mode of communication for project team members.

D. Information Management


31/44


Page: 31

Project Website

In an effort to manage and maintain project documentation, the Project Manager will

maintain a binder, file set and/or electronic repository of all required documentation to meetthe Technique/X minimum deliverables. This information will be published on the project

website located at the following address: http://inc.us.ABC.com/xxx/

The Project website may include the following documentation:

Project Charter

Project Plan

Project Issue Log (includes resolution)

Project Risk Watch (Risk Assessment)

Project Change Requests and Change Log Meeting Notes

Status Reports

Communication plan

Updated budget

Test plan strategy

Technical and Functional Specifications

All signature signoffs will be captured and maintained by the Project Manager in thepaper based project handbook.


32/44


Page: 32

XIV.APPENDIX A - Initial Project Risk AssessmentThe risks identified in the following table represent items that have been identified by the Sample Charter project t

project.

Risk

Item/

Priority

Potential Risk

Consequence

Risk Resolution Progress Probability

(%)

Impact

(Hours)

P1.1-01 The impact of

daily work for

the technical

team maycause delays in

completing

project work

Resolution to this risk can be incrementally

realized by implementing the following

measures to mitigate the risk:

Add additional technical resources. Shift production support from the project

technical resources to non-project

technical resources.

Cut back on project scope. Extend the project time line to

accommodate resource constraints.

100% 440

OPS=8hrs/wk*20

wks=160hrs

UNIX=

8hrs/wk*20

wks=160hrs

PROD

CNTRL=

4hrs/wk*20

wks=80hrs

SEC=

4hrs/wk*10

wks=40hrs


33/44


Page: 33

Risk

Item/

Priority

Potential Risk

Consequence


(%)

Impact

(Hours)


added other

project work

do to the I-Net

Operations

resource

vacancy is

causing delays

in completing

project work




Fill I-Net Operation Manager position Add additional technical resources. Shift I-Net Manager tasks from the

project technical resources to non-project




Prioritize I-Net projects so that SampleCharter is #1 priority

100 80

4hrs/wk *20

weeks =

80hrs


34/44


Page: 34

Risk

Item/

Priority

Potential Risk

Consequence


(%)

Impact

(Hours)


daily work for

the business

team may cause

delays in

completing

project work




Add additional business resources. Shift daily business tasks from the

project technical resources to non-project


Designate a Business Project Lead foreach business unit to assist in the

coordination and completion of projectwork.

Assign a project Business Liaison toassist in working with the Business

Project Leads to complete project work.



Provide a minimum of 30 day lead timeon project work requests to the business

units for planning purposes Allow an appropriate amount of time for

testing

100% 48

8hrs/month* 6 months

= 48 hrs


35/44


Page: 35

Risk

Item/

Priority

Potential Risk

Consequence


(%)

Impact

(Hours)

P1.4-04 The installation

of Netegrity

software on the

Apache servers

with Solaris 2.8

is being done

for the first time




Conduct Netegrity research/analysistesting early in the project (complete by

end of Sept. 2001) to allow for time to

switch to alternative option (stay

w/Solaris 2.7 on old Netras) if necessary

without impacting project time line.

Contract a Service Level Agreement withthe Netegrity vendor that provides

immediate response with Senior Level

Netegrity programming resources as a

way to expedite issue resolution.

Project Sponsor contacts Netegritymanagement to raise awareness of ABC

I-Net support expectations and impact

during the implementation of a ABC

mission critical project.

25% 260

Hour

estimates

based on

history of

previous

implementat

ion of

Netegrity


36/44


Page: 36

Risk

Item/

Priority

Potential Risk

Consequence


(%)

Impact

(Hours)

P1.5-05 The upgrade to

Websphere 4.0

may uncover

compatibility

issues




Contract with the IBM for a senior levelWebsphere expert (interviewed/ accepted

by ABC) as a way to minimize the

learning curve and expedite issue

resolution.

Install TECH environment during Phase-I (moved up from Phase-II) to conductWebsphere 4.0 testing.

Project Sponsor contact IBMmanagement to raise awareness of ABC


during the implementation of an ABC


50% 100

Hour

estimatesbased on

history of

previous

implementat

ion of

Websphere


37/44


Page: 37

Risk

Item/

Priority

Potential Risk

Consequence


(%)

Impact

(Hours)

P1.6-06 The

implementation

of Model

Cloning may

uncover

compatibility

issues




Implement Websphere 4.0 to takeadvantage of added Websphere

functionality.

Contract with the IBM for a senior levelWebsphere Model Cloning expert

(interviewed/ accepted by ABC) as a way

to minimize the learning curve andexpedite issue resolution

Project Sponsor contact IBMmanagement to raise awareness of ABC




50% 80

Hour

estimatebased on

experience

with Web

sphere and

Model

Cloning


38/44


Page: 38

Risk

Item/

Priority

Potential Risk

Consequence


(%)

Impact

(Hours)

P1.7-07 Veritas

Clustering is

new and

complex and

may uncover

compatibility

issues




Implement Websphere 4.0 to takeadvantage of added Websphere

functionality.

Contract with the Veritas vendor for asenior level Veritas expert (interviewed/

accepted by ABC) as a way to minimize

the learning curve and expedite issueresolution

Project Sponsor contacts Veritasmanagement to raise awareness of ABC




Conduct Veritas research/analysis testingearly in the project to allow for time to

switch to alternative option if necessary


Connect directly to the SAN.


39/44


Page: 39

Risk

Item/

Priority

Potential Risk

Consequence


(%)

Impact

(Hours)

P1.8-08 The use of NFS

servers in the

ABC

infrastructure is

new and

potentially

unstable




Conduct NFS research/analysis testingearly in the project to allow for time to

switch to alternative option if necessary


Connect directly to the SAN (note: needto pre-order cards for this option)

Add disk space to servers and do not useNFS

80

8hrs/server*

10 servers =80hrs

P1.9-09 The use of NIS

PLUS is new to

the ABC

infrastructure

and complex




Conduct NIS PLUS research/analysistesting early in the project to allow for

time to switch to alternative option if

necessary without impacting project time

line. Add additional technical resources. Dont install NIS PLUS as part of

Sample Charter project


40/44


Page: 40

Risk

Item/

Priority

Potential Risk

Consequence


(%)

Impact

(Hours)

P1.10-10 The SAN Space

and SAN

connections are

near full

capacity




Communicate to the SAN group theSample Charter project time line and

expectations

25% 120

Based on

past history,

SAN delays

have been

as great as 3

weeks or

120hrs

Totals:


41/44


42/44

DRAFT

Page: 42

XV. APPENDIX B Communications MatrixDAY OF

MEETING

TYPE OF MEETING/

COMMUNICATION TIME of

MEETING PURPOSE of MEETING

MATERIALS

SENT OUT BY: A

WEEKLY Project Status Report N/A The Weekly Project Status Report will

be e-mailed to project team members

and published on the Sample Charter

web site.

Published every

Tuesday

WEEKLY Technical Team Meeting Wednesday at

11:00am CST

The technical team meeting is a forum

for the technical team to discuss

project work, project schedule, and

project issues at a detailed level.

Within 2 days

after meeting

WEEKLY Core Team Meeting Thursday at10:00am CST

The business team meeting is a forumfor the business team to discuss

project work, project schedule, and

project issues at a detailed level.

Within 2 daysafter meeting

MONTHLY Executive Steering

Committee Meeting

9/18/01, 10/16/01,

11/13/01,

12/18/01, 1/15/02,

2/19/02, 3/19/02

The Project Steering Committee

meeting is designed to inform

executive management of project

progress to date. This meeting will

also be used to make decisions

regarding project budget, issues,

scope, and timeline.

Within 2 days

after meeting

Sample Project Management Plan


43/44


44/44


XVI.Approval Signatures

Jon Muggins / Project Manager Date

/ Executive Sponsor Date

/ Executive Steering Committee Date






abc inet pm plan

Documents