IT Integrated Project/

Solution Delivery And

Business Engagement Model

Alan McSweeney
Core Dimensions Of Projects

Every Project Has Two Core Dimensions:

IT And 1. Project Stages from Initial Concept to

Business Delivery
Functions/
Roles/ 2. Various Stakeholders Involved at
Activities Various Project Stages and in Various
Roles Performing Various Activities

Project Stages/Timeline

March 2, 2014 2
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 3
Components Of Integrated Project Delivery And
Business Engagement Model

Stages

S
Artefacts A A Activities

G
Gates

March 2, 2014 4
 Extended Dimensions Of Project Delivery
Project Review and Decision Gates

IT And
Business Artefacts
Functions/
Roles/
Activities

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

Manage
Concept Initiate Plan Design Build Test Deploy and
Operate
Project
Management
Business
Project Activity/ Function

Function

Business Business Analysis

Functions/ Solution
Architecture
Roles
Implementation
and Delivery

Test and Quality

Organisation
Readiness
Service
Management
Infrastructure
and
Communications

March 2, 2014 7
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
Specified
Performance and/or Business Benefits
Operational and Savings Not
Problems Delivered

Functionality
More Expensive Delivered Does not
to Operate Than Meet Business
Planned Requirements

Project Late Significant

and/or Over Rework
Budget Required

Complete Project
Success:
On-time, On-budget
and Delivering
Specified Benefits
Solution Largely
Unused And/Or
Unusable
Increasing Frequency/
Complete Project
Probability of Failure: Cancelled,
Occurrence 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

Manage
Concept Initiate Plan Design Build Test Deploy and
Operate
Project
Management Artefact
Business
Artefact
Project Activity/ Function

Function

Business Business Analysis Artefact

Functions/ Solution
Architecture Artefact
Roles
Implementation
and Delivery Artefact
Test and Quality Artefact
Organisation
Readiness Artefact
Service
Management Artefact
Infrastructure
and
Communications

March 2, 2014 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 Initiate Plan Design Build Test Deploy Operate
Project Charter Project Plan Project Management – Planning, Resource, Scheduling
Project Risk, Actions, Issues and Dependencies Management
Project Initiation Project Resource Plan Reporting and Communications Management
Management Document Change Management
Solution Concept/ Business Case Benefits Schedule and User Acceptance Test Benefits Realisation
Business Requirements Benefits Realisation Results Review
Function Document Plan Lessons Learned
Functional To Be Process User Acceptance Test Documentation Library
Business Requirements Definition Design and Plan
Analysis As Is Process Definition Standard Operating
Procedures
Rough Order of Solution Architecture Non Functional
Solution Magnitude Estimate High Level Design Requirements
Detailed Solution
Architecture Design/ Functional
Specification
Data Audit Confirmed Estimates Data Migration Results Data Migration Test Data Migration to Live Go Live Support
Data Design and Data Build Documentation Results
Configuration System Test Plan
Management Approach Migration Plan Unit Test Results Results Deploy to Production
Delivery and Plan Technical/Build UAT Changes and
Results
Integration Test Results Support and Operations
Detailed Estimates Specification Rework
Documentation

Test Strategy Functional Test Design Functional Test Results Operational Readiness
and Plan Non-Functional Test Review
Non-Functional Test Results
Design and Plan
Test and Quality Integration Test
Integration Test Design Results
and Plan System Test Results
System Test Design
and Plan
Management Team Change Impact Change Action Plan Role Definition Organisation and
Briefing Assessment Staffing
Organisation Detailed
Organisation Design Training Schedule Implementation
Communications Develop Training
Readiness Strategy and Plan Communications Plan
Material
Training Delivery
Training Needs Analysis
Service Impact Service Level Operations Acceptance Operations Acceptance Service and
Assessment Requirements Testing Design and Plan Testing Results Operational Level
Service Agreement(s)
Access and Security Service Definition
Management Definition Transfer to Production
Plan
Infrastructure Plan Infrastructure Design Build Test Environment Build Training Build Production Decommission Unused
Infrastructure Technical Build UAT Environment Environment Environment Environments
Infrastructure Specification Build OAT Environment
Build Development
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

Requirements Decision to Operations and

Business Concept Initial Discovery Requirements Management and Change Management
Elicitation Proceed Use

Solution Architecture and Design

Solution Solution Specification and Change

Solution Design
Architecture Management

Project Management Cycle

Initiate Execute and Control

Plan Close

Solution Delivery - Implementation and Deployment Lifecycle

Implement
Setup and
Manage Evolve
Prepare
Develop Test Deploy

March 2, 2014 17
 Initial Focus Area – Business Engagement And
Solution Definition
Time
Getting This
Right … Project Stages/ Timeline
Manage
Concept Initiate Plan Design Build Test Deploy and
Operate
Project
Management
Business
Focus on these project stages
Project Activity/ Function

Function and project activities will

Business Business Analysis ensure that the project
Functions/ Solution
foundations are sound
Architecture
Roles
Implementation
and Delivery

Test and Quality

Organisation
Readiness
Service
Management … Means Problems
Infrastructure Will Be Avoided At
and
Communications Later Stages

March 2, 2014 18
Artefact View Of Initial Focus Area – Business
Engagement And Solution Definition
Concept Initiate Plan Design

Project Charter Project Plan

Project Management Project Initiation Project Resource Plan
Document

Solution Concept/ Business Case Benefits Schedule and

Business Function Requirements Benefits Realisation
Document Plan

Functional To Be Process
Requirements Definition
Business Analysis Non Functional
As Is Process
Definition Requirements

Rough Order of Solution Architecture Detailed Solution

Solution Magnitude Estimate High Level Design Design/ Functional
Architecture 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 Time
These Wrong
… Project Stages/ Timeline
Manage
Concept Initiate Plan Design Build Test Deploy and
Operate
Project Solution Concept/ Requirements
Management
Business
Business Case
Project Activity/ Function

Function Functional Requirements

Business Business Analysis High Level Design
Functions/ Solution Benefits Schedule and Benefits Realisation
Architecture Plan
Roles
Implementation
and Delivery

Test and Quality

Organisation
Readiness
Service
Management
… Means Problems
Infrastructure
and
Communications
Will Occur During
The Project
March 2, 2014 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 Size/Capacity/ Poor Strategic
Requirements Complexity Alignment
Poor Analysis Large Project, Inadequate Business
Practices Complex, Difficult Case, Undefined
Changes and Processes Problem/Need

Business Requirements Large Project Team and Business Benefits Business Needs
Not Captured Multiple Stakeholders Not Measured Not Met

Opportunities
Lost

Investment
Inadequate Resource Unproven Technology Inadequately Explored Wasted
Allocation and Solution Options
Prioritisation

Inadequate Business Dynamic, Changing Solution Design Not

Involvement Environment Aligned to Business Needs

Poor Focus on Uncertainly/ Poor Solution

Business Needs Ambiguity Design
March 2, 2014 25
 Analysis And Solution Design-Related Causes Of
Failures
Poor Size/Capacity/ Poor Strategic
Requirements Complexity Alignment
Poor Analysis Large Project, Inadequate Business
Practices Complex, Difficult Case, Undefined
Changes and Processes Problem/Need

Business Requirements Large Project Team and Business Benefits Business Needs
Not Captured Multiple Stakeholders Not Measured Not Met

Opportunities
Lost

Investment
Inadequate Resource Unproven Technology Inadequately Explored Wasted
Allocation and Solution Options
Prioritisation

Inadequate Business Dynamic, Changing Solution Design Not

Involvement Environment Aligned to Business Needs

Poor Focus on Uncertainly/ Poor Solution

Business Needs Ambiguity Design
March 2, 2014 26
 Project Gates
Time

Project Stages/ Timeline

Manage
Concept Initiate Plan Design Build Test Deploy and
Operate
Project
Management
Business
Project Activity/ Function

Function

Business Business Analysis

Functions/ Solution
Architecture
Roles
Gate 0

Gate 3

Gate 6
Gate 1

Gate 2

Gate 4

Gate 5

Gate 7
Implementation
and Delivery

Test and Quality

Organisation
Readiness
Service
Management
Infrastructure
and
Communications

March 2, 2014 27
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 Gate

Criteria Successful Exit
Gate

Phase Phase

Project
Stopped
Sent Back for
Rework
STOP

March 2, 2014 29
Project Process Gates
Gate 0 Gate 1

Concept Initiate Plan

Gate 2

Gate 4 Gate 3

Test Build Design

Gate 5

Gate 6 Gate 7

Deploy Operate

March 2, 2014 30
 Project Process Gates
Gate 0 Gate 1

Concept Initiate Plan

Validate Solution Validate Business Case Gate 2
Concept and Estimates and Make Go/No Go
and Make Go/No Go Decision
Decision

Gate 4 Gate 3

Test Build Design

Validate Plan,
Gate 5 Build Review, Organisation Validate Detailed Design,
High-Level Design,
Benefits, Readiness
Design Review, Readiness to Readiness to Proceed to
Proceed to System Test and to Proceed to
Build and Make Go/No Go Detailed Design
UAT Decision and Make Go/No
Gate 6 Gate 7 Go Decision
Test Review,
Organisation
Change Review, Deploy Operate
Training
Review, Service
Planning Go Live Readiness Benefits Realisation
Review Review, Staffing and Validation, Lessons
Training Review Learned
March 2, 2014 31
Sample Gate Review for Gate 3 – Before Move To
Implementation/Development
• Gate 3 Pre-requisites • Gate review ensures that the relevant
− Benefits Schedule items have been created and are of
− To Be Processes sufficient quality
− Non-Functional Requirements • Designed to ensure that solution
− Detailed Solution Design/ Functional complexity has been captured so
Specification there is confidence that what is being
− Security Design developed is what is needed to be
− Data Design, Migration and Testing developed
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
March 2, 2014 32 32
 Artefact-Based Status View Of Project
Concept Initiate Plan Design Build Test Deploy Operate
Project Charter Project Plan
Project
Project Initiation Project Resource Plan
Management Document

Business Solution Concept/ Business Case Benefits Schedule and User Acceptance Test Benefits Realisation
Requirements Benefits Realisation Results Review
Function Document Plan Lessons Learned
Functional To Be Process User Acceptance Test Documentation Library
Business Requirements Definition Design and Plan
Analysis As Is Process Definition Standard Operating
Procedures
Rough Order of Solution Architecture Non Functional
Solution Magnitude Estimate High Level Design Requirements
Architecture Detailed Solution
Design/ Functional
Specification
Data Audit Confirmed Estimates Data Migration Results Data Migration Test Data Migration to Live Go Live Support
Data Design and Data Build Documentation Results
Configuration System Test Plan
Management Approach Migration Plan Unit Test Results Results Deploy to Production
Delivery and Plan` UAT Changes and
Results
Technical/Build Integration Test Results
Specification Rework Support and Operations
Detailed Estimates Documentation

Test Strategy Functional Test Design Functional Test Results Operational Readiness
and Plan Non-Functional Test Review
Non-Functional Test Results
Design and Plan
Test and Quality Integration Test Design
Integration Test
Results
and Plan System Test Results
System Test Design
and Plan
Management Team Change Impact Change Action Plan Role Definition Organisation and
Briefing Assessment Staffing
Organisation Detailed
Organisation Design Training Schedule Implementation
Communications
Readiness Strategy and Plan Communications Plan Develop Training Training Delivery
Material
Training Needs Analysis
Service Impact Service Level Operations Acceptance Operations Acceptance Service and
Service Assessment Requirements Testing Design and Plan Testing Results Operational Level
Access and Security Agreement(s)
Management Service Definition
Definition Transfer to Production
Plan
Infrastructure Plan Infrastructure Design Build Test Environment Build Training Build Production Decommission Unused
Infrastructure Technical Build UAT Environment Environment Environment Environments
Infrastructure Specification Build OAT Environment
Build Development
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