Proposed Project Office Strategy

Proposed Methodology

Josh Folgado Business Enterprise Architect

Project Management Office

Standards used: Prince2/PM2 for Project Management TOGAF for Process and

Documentation Zachman for Enterprise

Done by Josh Folgado. Copyright © 2014 joshfolgado.com . All rights reserved.

Agenda Purpose of Discussion

Proposed Project Management Process Some Project Examples Zachman Framework What/how information is gathered during Project Process using Framework The Project Template (TGL): Transformation Governance Log Open discussion on project methodology


Purpose of Discussion

• Learn about proposed Project Management Methodology, get feedback for refinement and how to use it

• Need support for delivering uniform Project Management Services - for both the Business and IT, i.e. business projects, new products, application development, database development, etc.

• Active engagement to implement best-practice: Business Process Reengineering (BPR)

• Discover and help fine-tune single document (TGL) that keeps all information regarding project


Agenda Purpose of Discussion Proposed Project Management Process

Some Project Examples

Zachman Framework

What/how information is gathered during

Project Process using Framework The Project Template (TGL):

Transformation Governance Log

Open discussion on project methodology


Project Management Process Closure phase

Execution phase

Initiation phase

Start-up phase


Closure phase

Execution phase

Initiation phase

Start-up phase

Quality street

NO

Project Management Process

YES


Closure phase

Execution phase

Initiation phase

Start-up phase

Quality street Architecture Services

• Business Intake • Architecture Guidance

• Project Start Architecture • Architecture Guidance • Business Approval

• Project Health Check • Architecture Guidance

• Final Conformity Audit



• Business Intake:

Closure phase

Execution phase

Initiation phase

Start-up phase







– Assess impact and strategic needs of organisation

– Why are you doing this work; what is the benefit to the organisation

– What business services will be delivered to the project and draft subsequent dependencies

– Discuss with all involved parties; inform and involve everyone concerned for best understanding and focus of deliverables

Architecture is responsible for Business Intake

Programme manager agrees schedule based on resources, criteria, priorities and impact to the organisation


• Project Impact:

Closure phase

Execution phase

Initiation phase

Start-up phase







Risk Factor Rating

Solution complexity Low/Medium/High

Standards compliance Low/Medium/High

Project size and complexity Low/Medium/High

Business strategy Low/Medium/High

Business impact Low/Medium/High

Business compliance Low/Medium/High

Impact to methods and structure Low/Medium/High

Resource usage/dependencies Low/Medium/High

Training of resources Low/Medium/High

Data/application models Low/Medium/High


Closure phase

Execution phase

Initiation phase

Start-up phase






Service

Intake

PSA

Approval

Health Check

Final Audit


Medium Impact

Mandatory

Recommended

Mandatory

Recommended

Mandatory

High Impact

Mandatory

Mandatory

Mandatory

Mandatory

Mandatory

Low Impact

Mandatory

Optional

Recommended

Optional

Recommended


• Project Start Architecture

Closure phase

Execution phase

Initiation phase

Start-up phase







– Which borders will the project have to respect

– Identify steps and milestones for project, i.e. building blocks

– What business services are involved and subsequent dependencies

Architecture is responsible for project start architecture

– Creation/updating of enterprise blueprints for solution

Final agreement on project’s deliverables and schedule


• Project Start Architecture – Which borders will the project have to respect – Identify steps and milestones for project, i.e. building blocks – What business services are involved and subsequent dependencies – Creation/updating of enterprise blueprints for solution – Final agreement on project’s deliverables and schedule

Closure phase

Execution phase

Initiation phase

Start-up phase







• Business Approval

Architecture is responsible for Business Approval

Sign-off by project owner and architecture on how the project is to be done by the applicable business services

Inform project office on execution status


• Project Health Check

Closure phase

Execution phase

Initiation phase

Start-up phase







– In depth examination of the project's deliverables and their alignment with approval/recommendations and/or architecture standards, guidelines and principles or additional change requests

Programme manager may set multiple health checks for projects, depending on risk and project complexity

– Manage unexpected/unapproved features with programme manager i.e. change requests

Health checks can be called at anytime by programme manager

Architecture is responsible for health checks and reports results to programme manager


Closure phase

Execution phase

Initiation phase

Start-up phase







• Final Conformity Audit – Check and confirm final project deliverables are in line with agreements

with business service that owns project

Project owner signs-off project

Architecture is responsible for final audit, working along with programme manager and business owner

Project office finalises and closes TGL document

– Verify that enterprise models are updated, according to final solution




Zachman Framework






Project Services - Low Impact Examples

• Study to replace the company logo

• Cleaning of content in databases

• Rearrange the parking area


Project Services - Medium Impact Examples

• Multiple BPR Projects for process improvement

• New regulations to be adopted in financial systems

• Upgrade PABX


Project Services - High Impact Examples

• Moving of IT to external entity

• Data Warehouse

• Restructuring of Business Services




Zachman Framework






Business Domains

Business Data Model

Logical Data Model

Physical Data Model

Data Specification

Data

Organisation Structure

Business Roles

User Centric Design

User Interface Presentation

Security Specification

Organisation

Business Locations

Environments and Locations

Technology Platforms

Physical (network) Design

Hardware and Network

Specifications

Network

Business Functions and

Services

Business Processes

Model

Application Landscape

Application Design

Application Service

Specification

Service

Business Drivers

Roadmaps

Transformation Governance

Control Design

Timing Specification

Change

Business Strategy

Business Goals and Objectives

Guiding Principles

Policies

Standards

Strategy

Planner

Enterprise Architect

Solution Architect

Designer

Engineer

Functioning Enterprise

Scope

Business Model

System Model

Technology Model

Detailed specifications

Enterprise Architecture What How Where Who When Why

Zachman Framework

A1

A2

A3

A4

A5

B1

B2

B3

B4

B5

C1

C2

C3

C4

C5

D1

D2

D3

D4

D5

E1

E2

E3

E4

E5

F1

F2

F3

F4

F5

A6 B6 C6 D6 E6 F6


Closure phase

Execution phase

Initiation phase

Start-up phase






Focus during start-up phase

Project Services and Framework

Business Domains

Business Data Model

Logical Data Model

Physical Data Model

Data Specificatio

n Data


Business Roles

User Centric Design User

Interface Presentatio

n Security Specificatio

n Organisatio

n

Business Locations

Environments and

Locations



Hardware and

Network Specificatio

ns Network

Business Functions

and Services Business

Processes Model


Application Design

Application Service

Specification Service

Business Drivers

Roadmaps

Transformation

Governance Control

Design

Timing Specificatio

n Change

Business Strategy


Guiding Principles

Policies

Standards

Strategy

Planner


Solution Architect

Designer

Engineer


Scope

Business Model

System Model

Technology Model


EA What How Where Who When Why


Closure phase

Execution phase

Initiation phase

Start-up phase






Focus during initiation phase


Business Domains

Business Data Model

Logical Data Model

Physical Data Model

Data Specificatio

n Data


Business Roles

User Centric Design

User Interface

Presentation Security

Specification

Organisation

Business Locations

Environments and

Locations



Hardware and


ns Network

Business Functions


Processes Model


Application Design

Application Service


Business Drivers

Roadmaps

Transformation

Governance

Control Design

Timing Specificatio

n Change

Business Strategy


Guiding Principles

Policies

Standards

Strategy

Planner


Solution Architect

Designer

Engineer


Scope

Business Model

System Model

Technology Model





Closure phase

Execution phase

Initiation phase

Start-up phase







Focus during execution phase



Business Domains

Business Data Model

Logical Data Model

Physical Data Model

Data Specificatio

n Data


Business Roles

User Centric Design

User Interface

Presentation

Security Specificatio

n Organisatio

n

Business Locations

Environments and

Locations



Hardware and


ns Network

Business Functions


Processes Model


Application Design

Application Service


Business Drivers

Roadmaps

Transformation

Governance

Control Design

Timing Specificatio

n Change

Business Strategy


Guiding Principles

Policies

Standards

Strategy

Planner


Solution Architect

Designer

Engineer


Scope

Business Model

System Model

Technology Model




Closure phase

Execution phase

Initiation phase

Start-up phase










Business Domains

Business Data Model

Logical Data Model

Physical Data Model

Data Specification

Data


Business Roles

User Centric Design

User Interface

Presentation


Organisation

Business Locations

Environments and

Locations



Hardware and Network Specification

s Network

Business Functions


Processes Model


Application Design

Application Service

Specification

Service

Business Drivers

Roadmaps

Transformation

Governance

Control Design


Change

Business Strategy


Guiding Principles

Policies

Standards

Strategy

Planner


Solution Architect

Designer

Engineer


Scope

Business Model

System Model

Technology Model




Closure phase

Execution phase

Initiation phase

Start-up phase










Business Domains

Business Data Model

Logical Data Model

Physical Data Model

Data Specification

Data


Business Roles

User Centric Design

User Interface

Presentation


Organisation

Business Locations

Environments and

Locations



Hardware and Network Specification

s Network

Business Functions


Processes Model


Application Design

Application Service

Specification

Service

Business Drivers

Roadmaps

Transformation

Governance

Control Design


Change

Business Strategy


Guiding Principles

Policies

Standards

Strategy

Planner


Solution Architect

Designer

Engineer


Scope

Business Model

System Model

Technology Model



Focus during closure phase




Zachman Framework






Business Domains

Business Data Model

Logical Data Model

Physical Data Model

Data Specification

Data


Business Roles

User Centric Design



Organisation

Business Locations





Specifications

Network


Services

Business Processes

Model


Application Design

Application Service

Specification

Service

Business Drivers

Roadmaps


Control Design


Change

Business Strategy


Guiding Principles

Policies

Standards

Strategy

Planner


Solution Architect

Designer

Engineer


Scope

Business Model

System Model

Technology Model



A1

A2

A3

A4

A5

B1

B2

B3

B4

B5

C1

C2

C3

C4

C5

D1

D2

D3

D4

D5

E1

E2

E3

E4

E5

F1

F2

F3

F4

F5

A6 B6 C6 D6 E6 F6

Framework


Business Domains

Business Data Model

Logical Data Model

Physical Data Model

Data Specification

Data


Business Roles

User Centric Design



Organisation

Business Locations





Specifications

Network


Services

Business Processes

Model


Application Design

Application Service

Specification

Service

Business Drivers

Roadmaps


Control Design


Change

Business Strategy


Guiding Principles

Policies

Standards

Strategy

Planner


Solution Architect

Designer

Engineer


Scope

Business Model

System Model

Technology Model



A1

A2

A3

A4

A5

B1

B2

B3

B4

B5

C1

C2

C3

C4

C5

D1

D2

D3

D4

D5

E1

E2

E3

E4

E5

F1

F2

F3

F4

F5

A6 B6 C6 D6 E6 F6

ProjectIntakeFramework


Business Domains

Business Data Model

Logical Data Model

Physical Data Model

Data Specification

Data


Business Roles

User Centric Design



Organisation

Business Locations





Specifications

Network


Services

Business Processes

Model


Application Design

Application Service

Specification

Service

Business Drivers

Roadmaps


Control Design


Change

Business Strategy


Guiding Principles

Policies

Standards

Strategy

Planner


Solution Architect

Designer

Engineer


Scope

Business Model

System Model

Technology Model



A1

A2

A3

A4

A5

B1

B2

B3

B4

B5

C1

C2

C3

C4

C5

D1

D2

D3

D4

D5

E1

E2

E3

E4

E5

F1

F2

F3

F4

F5

A6 B6 C6 D6 E6 F6

ProjectIntake

Conformity ApprovalFramework


Business Domains

Business Data Model

Logical Data Model

Physical Data Model

Data Specification

Data


Business Roles

User Centric Design



Organisation

Business Locations





Specifications

Network


Services

Business Processes

Model


Application Design

Application Service

Specification

Service

Business Drivers

Roadmaps


Control Design


Change

Business Strategy


Guiding Principles

Policies

Standards

Strategy

Planner


Solution Architect

Designer

Engineer


Scope

Business Model

System Model

Technology Model



A1

A2

A3

A4

A5

B1

B2

B3

B4

B5

C1

C2

C3

C4

C5

D1

D2

D3

D4

D5

E1

E2

E3

E4

E5

F1

F2

F3

F4

F5

A6 B6 C6 D6 E6 F6

ProjectIntake

Conformity Approval

HealthCheckFramework


Business Domains

Business Data Model

Logical Data Model

Physical Data Model

Data Specification

Data


Business Roles

User Centric Design



Organisation

Business Locations





Specifications

Network


Services

Business Processes

Model


Application Design

Application Service

Specification

Service

Business Drivers

Roadmaps


Control Design


Change

Business Strategy


Guiding Principles

Policies

Standards

Strategy

Planner


Solution Architect

Designer

Engineer


Scope

Business Model

System Model

Technology Model



ProjectIntake

Conformity Approval

HealthCheck

HealthCheck

A1

A2

A3

A4

A5

B1

B2

B3

B4

B5

C1

C2

C3

C4

C5

D1

D2

D3

D4

D5

E1

E2

E3

E4

E5

F1

F2

F3

F4

F5

Framework

A6 B6 C6 D6 E6 F6


Business Domains

Business Data Model

Logical Data Model

Physical Data Model

Data Specification

Data


Business Roles

User Centric Design



Organisation

Business Locations





Specifications

Network


Services

Business Processes

Model


Application Design

Application Service

Specification

Service

Business Drivers

Roadmaps


Control Design


Change

Business Strategy


Guiding Principles

Policies

Standards

Strategy

Planner


Solution Architect

Designer

Engineer


Scope

Business Model

System Model

Technology Model



ProjectIntake

Conformity Approval

HealthCheck

HealthCheck

A1

A2

A3

A4

A5

B1

B2

B3

B4

B5

C1

C2

C3

C4

C5

D1

D2

D3

D4

D5

E1

E2

E3

E4

E5

F1

F2

F3

F4

F5

Framework

A6 B6 C6 D6 E6 F6

FinalAudit




Zachman Framework






Transformation Governance Log (TGL) Project Start-up

What services/solutions will be delivered to the project

Sign off regarding the approach by the applicable business services

In depth examination of the project's deliverables and their alignment with approval and/or architecture standards, guidelines and principles

Project Initiation Which borders will the

project have to respect

- Business Intake

- Project Start Architecture

Project Execution

- Final Conformity Audit Before Project Closure

Final project deliverables in line with agreements

- Project Health Check

- Business Approval




Zachman Framework






Presentations & Public Speaking

Proposed Project Office Strategy