Anda di halaman 1dari 37

IT Integrated Project/ Solution Delivery And Business Engagement Model

Alan McSweeney

Core Dimensions Of Projects

Every Project Has Two Core Dimensions: IT And Business Functions/ Roles/ Activities 1. Project Stages from Initial Concept to Delivery Various Stakeholders Involved at Various Project Stages and in Various Roles Performing Various Activities

2.

Project Stages/Timeline

March 2, 2014

Integrated Project Business Engagement Model

Projects are a continuum from initial concept to planning, design, implementation and management and operation of the implemented solution (and ultimate decommissioning) and across IT and business functions Therefore important to have an integrated project delivery approach that crosses both these core dimensions

March 2, 2014

Components Of Integrated Project Delivery And Business Engagement Model


Stages

S
Artefacts

A G
Gates

Activities

March 2, 2014

Extended Dimensions Of Project Delivery


Project Review and Decision Gates

IT And Business Functions/ Roles/ Activities

Artefacts

Project Stages/Timeline
March 2, 2014 5

Extended Dimensions Of Project Delivery

Offers a common and consistent frame of reference for all projects

Integrated Project Delivery Process And Business Engagement Model


Time
Project Stages/ Timeline
Concept Project Management Business Function Business Analysis Solution Architecture Implementation and Delivery Test and Quality Organisation Readiness Service Management Infrastructure and Communications
March 2, 2014 7

Initiate

Plan

Design

Build

Test

Deploy

Manage and Operate

Project Activity/ Function

Business Functions/ Roles

Integrated Project Delivery Process And Business Engagement Model


Take an artefacts- and results/deliverables-based integrated approach with review gates where go/no-go decisions are made Across all project phases and project delivery roles Focus on getting the project right at the start will yield benefits Provides a complete view of what has to be achieved Allows project status to be assessed Allows effort to be quantified across all stages and resources Designed to reduce risk of project failures

March 2, 2014 8

Integrated Project Delivery Process

Integrates project management into all other aspects and activities of project and solution delivery
Business Business Analysis Solution Architecture Implementation and Delivery Test and Quality Organisation Readiness Service Management Infrastructure

All relevant stakeholders are identified at an early stage and involved throughout subsequently
March 2, 2014 9

Spectrum Of Project Failures


Performance and/or Operational Problems More Expensive to Operate Than Planned Project Late and/or Over Budget Specified Business Benefits and Savings Not Delivered Functionality Delivered Does not Meet Business Requirements Significant Rework Required Solution Largely Unused And/Or Unusable

Complete Project Success: On-time, On-budget and Delivering Specified Benefits

Increasing Frequency/ Probability of Occurrence

Complete Project Failure: Cancelled, Unused, Rejected

March 2, 2014

10

Project Failures

Project Failures late projects, over budget, project functionality not delivered, anticipated business benefits not achieved Project Rework involving additional cost Deferred/Removed Scope needed to meet project schedule and either never implemented or implemented later at additional cost

March 2, 2014

11

Reasons For Project Failures


Project foundations not correct before implementation starts


Project failure is embedded in the process from the start

Requirements - not captured, documented, validated and agreed poor requirement management process and capability Design - proposed solution designs not analysed and defined in sufficient detail to understand Implementation - started before scope and complexity understood, documented and defined - there is no check ensure detail is captured and documented before development starts Scope - Project scope not defined and challenged and solution complexity not understood and documented Stakeholders all stakeholders not accurately identified Budget project costs are not validated or challenged
March 2, 2014 12

Artefacts/Deliverables Define Across Project Delivery Process


Time
Project Stages/ Timeline
Concept Project Management Business Function Business Analysis Solution Architecture Implementation and Delivery Test and Quality Organisation Readiness Service Management Infrastructure and Communications
March 2, 2014

Initiate

Plan

Design

Build

Test

Deploy

Manage and Operate

Artefact Artefact Artefact Artefact Artefact Artefact Artefact Artefact

Project Activity/ Function

Business Functions/ Roles

13

Artefacts/Deliverables

Exist to demonstrate work done to a defined standard and quality Forces projects to gather information to validate their activities Provides an audit trail and proof of work done Provides a library of project material that can be reused for other projects Artefacts structures are designed to be generic to apply across all project types

March 2, 2014

14

Artefact View Of Integrated Project Delivery Process


Concept
Project Management Business Function Business Analysis Solution Architecture
Rough Order of Magnitude Estimate Solution Concept/ Requirements Document

Initiate
Project Charter Project Initiation Document Business Case

Plan
Project Plan Project Resource Plan

Design

Build

Test

Deploy

Operate

Project Management Planning, Resource, Scheduling Risk, Actions, Issues and Dependencies Management Reporting and Communications Management Change Management Benefits Schedule and Benefits Realisation Plan User Acceptance Test Results User Acceptance Test Design and Plan Standard Operating Procedures Benefits Realisation Review Lessons Learned Documentation Library

Functional Requirements As Is Process Definition Solution Architecture High Level Design

To Be Process Definition

Non Functional Requirements Detailed Solution Design/ Functional Specification Data Migration Test System Test Plan Results UAT Changes and Rework Data Migration to Live Results Deploy to Production Results Support and Operations Documentation Go Live Support

Delivery

Confirmed Estimates Data Migration Results Data Audit Data Design and Data Build Documentation Configuration Migration Plan Management Approach Unit Test Results and Plan Technical/Build Integration Test Results Specification Detailed Estimates Test Strategy

Test and Quality

Functional Test Design Functional Test Results Operational Readiness and Plan Review Non-Functional Test Non-Functional Test Results Design and Plan Integration Test Integration Test Design Results and Plan System Test Results System Test Design and Plan Change Impact Assessment Detailed Communications Plan Training Needs Analysis Service Level Requirements Access and Security Definition Change Action Plan Organisation Design Develop Training Material Role Definition Training Schedule Organisation and Staffing Implementation Training Delivery Service and Operational Level Agreement(s) Transfer to Production Plan Build Production Environment Decommission Unused Environments

Organisation Readiness Service Management

Management Team Briefing Communications Strategy and Plan Service Impact Assessment

Operations Acceptance Operations Acceptance Testing Design and Plan Testing Results Service Definition

Infrastructure Plan

Infrastructure

Infrastructure Design Build Test Environment Infrastructure Technical Build UAT Environment Specification Build OAT Environment Build Development Environment

Build Training Environment

March 2, 2014

15

Artefact View Of Integrated Project Delivery Process

Takes a complete view of project delivery and implementation from initial design to management and operation

March 2, 2014

16

Artefact View Integrates Different Activity Lifecycles


Strategy, Business Planning and Business Analysis
Business Concept Initial Discovery Requirements Elicitation Decision to Proceed Requirements Management and Change Management Operations and Use

Solution Architecture and Design


Solution Architecture Solution Design Solution Specification and Change Management

Project Management Cycle


Initiate Execute and Control Plan Close

Solution Delivery - Implementation and Deployment Lifecycle


Setup and Prepare Implement Manage Develop Test Deploy Evolve

March 2, 2014

17

Initial Focus Area Business Engagement And Solution Definition


Time Getting This Right
Concept Project Management Business Function Business Analysis Solution Architecture Implementation and Delivery Test and Quality Organisation Readiness Service Management Infrastructure and Communications
March 2, 2014

Project Stages/ Timeline


Initiate Plan Design Build Test Deploy Manage and Operate

Business Functions/ Roles

Focus on these project stages and project activities will ensure that the project foundations are sound

Project Activity/ Function

Means Problems Will Be Avoided At Later Stages


18

Artefact View Of Initial Focus Area Business Engagement And Solution Definition
Concept Project Management Initiate
Project Charter Project Initiation Document Solution Concept/ Requirements Document Business Case

Plan
Project Plan Project Resource Plan

Design

Business Function

Benefits Schedule and Benefits Realisation Plan Functional Requirements To Be Process Definition Non Functional Requirements

Business Analysis

As Is Process Definition Rough Order of Magnitude Estimate Solution Architecture High Level Design

Solution Architecture

Detailed Solution Design/ Functional Specification

Establishes solid foundations on which to build solution delivery and implementation


March 2, 2014 19

Initial Focus Area Business Engagement And Solution Definition

March 2, 2014

20

Initial Focus Area Business Engagement And Solution Definition And Validation

Have a defined solution to meet a defined and articulated business need that will deliver a realisable and achievable set of business benefits Understand the complexity of what has to be delivered

March 2, 2014

21

Initial Focus Area Business Engagement And Solution Definition And Validation

Ensures there is a strong and solid foundation for solution implementation, delivery and management and operation

March 2, 2014

22

Initial Focus Area Business Engagement And Solution Definition And Validation
Getting These Wrong
Concept Project Management Business Function Business Analysis Solution Architecture Implementation and Delivery Test and Quality Organisation Readiness Service Management Infrastructure and Communications
March 2, 2014

Time
Project Stages/ Timeline
Initiate Plan Design Build Test Deploy Manage and Operate

Solution Concept/ Requirements Business Case Functional Requirements High Level Design Benefits Schedule and Benefits Realisation Plan

Project Activity/ Function

Business Functions/ Roles

Means Problems

Will Occur During


The Project
23

Initial Focus Area Business Engagement And Solution Definition And Validation

Where there are gaps in the foundation on which solution implementation is being based, the project is at significant risk of failure

March 2, 2014

24

Weaknesses In Business Analysis And Solution Design Capabilities At The Root of Many Project Failures
Poor Requirements
Poor Analysis Practices

Size/Capacity/ Complexity

Poor Strategic Alignment

Large Project, Complex, Difficult Changes and Processes Large Project Team and Multiple Stakeholders

Inadequate Business Case, Undefined Problem/Need Business Benefits Not Measured

Business Requirements Not Captured

Business Needs Not Met Opportunities Lost

Inadequate Resource Allocation and Prioritisation Inadequate Business Involvement

Unproven Technology

Inadequately Explored Solution Options

Investment Wasted

Dynamic, Changing Environment

Solution Design Not Aligned to Business Needs

Poor Focus on Business Needs


March 2, 2014

Uncertainly/ Ambiguity

Poor Solution Design


25

Analysis And Solution Design-Related Causes Of Failures


Poor Requirements
Poor Analysis Practices

Size/Capacity/ Complexity

Poor Strategic Alignment

Large Project, Complex, Difficult Changes and Processes Large Project Team and Multiple Stakeholders

Inadequate Business Case, Undefined Problem/Need Business Benefits Not Measured

Business Requirements Not Captured

Business Needs Not Met Opportunities Lost

Inadequate Resource Allocation and Prioritisation Inadequate Business Involvement

Unproven Technology

Inadequately Explored Solution Options

Investment Wasted

Dynamic, Changing Environment

Solution Design Not Aligned to Business Needs

Poor Focus on Business Needs


March 2, 2014

Uncertainly/ Ambiguity

Poor Solution Design


26

Project Gates
Time
Project Stages/ Timeline
Concept Project Management Business Function Business Analysis Solution Architecture Implementation and Delivery Test and Quality Organisation Readiness Service Management Infrastructure and Communications
March 2, 2014 27

Initiate

Plan

Design

Build

Test

Deploy

Manage and Operate

Project Activity/ Function

Business Functions/ Roles

Gate 3

Gate 6

Gate 0

Gate 2

Gate 4

Gate 5

Gate 7

Gate 1

Project Gates

Gates exist after each to ensure project is ready to move to the next stage or to be stopped or whether rework is required Review and decision points Artefacts must be ready for review on gate entry Gate exit requires artefacts completed to the required standard Reduces cost, risk and rework Puts controls around the delivery process Ensures work remains on track
March 2, 2014 28

Gate Process

Gate Entry Criteria Phase

Gate

Gate Successful Exit Phase

Project Stopped Sent Back for Rework

STOP

March 2, 2014

29

Project Process Gates


Gate 0 Concept Initiate Gate 1 Plan Gate 2 Gate 4 Test Gate 5 Gate 6 Deploy Operate Gate 7 Build Gate 3 Design

March 2, 2014

30

Project Process Gates


Gate 0 Concept
Validate Solution Concept and Estimates and Make Go/No Go Decision

Gate 1 Initiate
Validate Business Case and Make Go/No Go Decision

Plan Gate 2

Gate 4 Test Gate 5


Build Review, Organisation Design Review, Readiness to Proceed to System Test and UAT

Gate 3 Build
Validate Detailed Design, Readiness to Proceed to Build and Make Go/No Go Decision

Design
Validate Plan, High-Level Design, Benefits, Readiness to Proceed to Detailed Design and Make Go/No Go Decision

Gate 6
Test Review, Organisation Change Review, Training Review, Service Planning Review
March 2, 2014

Gate 7 Operate

Deploy
Go Live Readiness Review, Staffing and Training Review

Benefits Realisation Validation, Lessons Learned


31

Sample Gate Review for Gate 3 Before Move To Implementation/Development

Gate 3 Pre-requisites
Benefits Schedule To Be Processes Non-Functional Requirements Detailed Solution Design/ Functional Specification Security Design Data Design, Migration and Testing Strategy Design and Plan Functional Tests Design and Plan Integration Tests Design and Plan Non-Functional Tests System Test Plan Systems Inventory Data Migration Plan Change Impact Assessment Detailed Communications Plan Training Needs Analysis Training Strategy Service Design Capacity Requirements Plan Infrastructure Specification
32

Gate review ensures that the relevant items have been created and are of sufficient quality Designed to ensure that solution complexity has been captured so there is confidence that what is being developed is what is needed to be developed

March 2, 2014

32

Artefact-Based Status View Of Project


Concept
Project Management Business Function Business Analysis Solution Architecture
Rough Order of Magnitude Estimate Solution Concept/ Requirements Document

Initiate
Project Charter Project Initiation Document Business Case

Plan
Project Plan Project Resource Plan

Design

Build

Test

Deploy

Operate

Benefits Schedule and Benefits Realisation Plan Functional Requirements As Is Process Definition Solution Architecture High Level Design To Be Process Definition User Acceptance Test Design and Plan Standard Operating Procedures

User Acceptance Test Results

Benefits Realisation Review Lessons Learned Documentation Library

Non Functional Requirements Detailed Solution Design/ Functional Specification Confirmed Estimates Data Design and Data Migration Plan Technical/Build Specification Data Migration Results Build Documentation Unit Test Results Integration Test Results Data Migration Test System Test Plan Results UAT Changes and Rework Data Migration to Live Results Deploy to Production Results Support and Operations Documentation Go Live Support

Data Audit

Delivery

Configuration Management Approach and Plan` Detailed Estimates Test Strategy

Test and Quality

Functional Test Design Functional Test Results Operational Readiness and Plan Review Non-Functional Test Non-Functional Test Results Design and Plan Integration Test Integration Test Design Results and Plan System Test Results System Test Design and Plan Change Action Plan Change Impact Assessment Organisation Design Detailed Develop Training Communications Plan Material Training Needs Analysis Service Level Requirements Access and Security Definition Role Definition Training Schedule Organisation and Staffing Implementation Training Delivery Service and Operational Level Agreement(s) Transfer to Production Plan Build Production Environment Decommission Unused Environments

Organisation Readiness Service Management

Management Team Briefing Communications Strategy and Plan Service Impact Assessment

Operations Acceptance Operations Acceptance Testing Design and Plan Testing Results Service Definition

Infrastructure Plan

Infrastructure

Infrastructure Design Build Test Environment Infrastructure Technical Build UAT Environment Specification Build OAT Environment Build Development Environment

Build Training Environment

March 2, 2014

33

Consistent View Of Projects

March 2, 2014

34

Artefact-Based Status View Of Project

Use the status of the artefacts at project stages to assess and measure the status of the project One element of project reporting

March 2, 2014

35

Summary

Provides a consistent and repeatable approach to projects Independent of the specifics of a project Artefact-based view Enables gate review process where deliverables can be evaluated for quality and substance Enables status of the project to assessed Ensures success by emphasising business engagement and solution analysis and design at an early stage Engages early with project complexity
March 2, 2014 36

More Information
Alan McSweeney http://ie.linkedin.com/in/alanmcsweeney

March 2, 2014

37