Integrated Project and Solution Delivery And Business Engagement Model

50 %
50 %
Information about Integrated Project and Solution Delivery And Business Engagement Model
Entertainment

Published on March 2, 2014

Author: alanmcsweeney

Source: authorstream.com

IT Integrated Project/ Solution Delivery And Business Engagement Model: IT Integrated Project/ Solution Delivery And Business Engagement Model Alan McSweeney Core Dimensions Of Projects: Core Dimensions Of Projects Project Stages/Timeline I T And Business Functions/ Role s/ Activities Every Project Has Two Core D imensions: Project Stages from I nitial Concept to Delivery Various Stakeholders Involved at Various Project Stages and in Various Roles Performing Various Activities March 2, 2014 2 Integrated Project Business Engagement Model: 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: Components Of Integrated Project Delivery And Business Engagement Model March 2, 2014 4 A A G Extended Dimensions Of Project Delivery: Extended Dimensions Of Project Delivery Project Stages/Timeline I T And Business Functions/ Role s/ Activities March 2, 2014 5 Project Review and Decision Gates Artefacts Extended Dimensions Of Project Delivery: Extended Dimensions Of Project Delivery Offers a common and consistent frame of reference for all projects Integrated Project Delivery Process And Business Engagement Model: Integrated Project Delivery Process A nd Business Engagement Model Project Stages/ Timeline Project Activity/ Function Concept Initiate Plan Design Build Test Deploy Manage and Operate Project Management Business Function Business Analysis Solution Architecture Implementation and Delivery Test and Quality Organisation Readiness Service Management Infrastructure and Communications Time Business Functions/ Roles March 2, 2014 7 Integrated Project Delivery Process And Business Engagement Model: Integrated Project Delivery Process A nd 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: 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: Spectrum Of Project Failures Complete Project Success: On-time, On-budget and Delivering Specified Benefits Project Late and/or Over Budget More Expensive to Operate Than Planned Performance and/or Operational Problems 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 Failure: Cancelled, Unused, Rejected Increasing Frequency/ Probability of Occurrence March 2, 2014 10 Project Failures: 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: 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: Artefacts/Deliverables Define Across Project Delivery Process Project Stages/ Timeline Project Activity/ Function Concept Initiate Plan Design Build Test Deploy Manage and Operate Project Management Business Function Business Analysis Solution Architecture Implementation and Delivery Test and Quality Organisation Readiness Service Management Infrastructure and Communications Time Business Functions/ Roles Artefact Artefact Artefact Artefact Artefact Artefact Artefact Artefact March 2, 2014 13 Artefacts/Deliverables: 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: Artefact View Of Integrated Project Delivery Process Concept Initiate Plan Design Build Test Deploy Operate Project Management Business Function Business Analysis Solution Architecture Delivery Test and Quality Organisation Readiness Service Management Infrastructure Solution Concept/ Requirements Document Rough Order of Magnitude Estimate Project Charter Project Initiation Document Business Case Project Plan Project Resource Plan Functional Requirements As Is Process Definition Benefits Schedule and Benefits Realisation Plan User Acceptance Test Results Benefits Realisation Review Lessons Learned To Be Process Definition User Acceptance Test Design and Plan Standard Operating Procedures Documentation Library Solution Architecture High Level Design Non Functional Requirements Detailed Solution Design/ Functional Specification Data Audit Data Design and Data Migration Plan Data Migration Results Data Migration Test Data Migration to Live Results Go Live Support Configuration Management Approach and Plan Technical/Build Specification Build Documentation Unit Test Results Integration Test Results System Test Plan Results UAT Changes and Rework Deploy to Production Results Support and Operations Documentation Test Strategy Functional Test Design and Plan Non-Functional Test Design and Plan Integration Test Results System Test Results Operational Readiness Review Management Team Briefing Communications Strategy and Plan Change Impact Assessment Organisation Design Develop Training Material Detailed Communications Plan Training Needs Analysis Change Action Plan Role Definition Training Schedule Organisation and Staffing Implementation Training Delivery Service Impact Assessment Service Level Requirements Access and Security Definition Operations Acceptance Testing Design and Plan Operations Acceptance Testing Results Service Definition Functional Test Results Non-Functional Test Results Integration Test Design and Plan System Test Design and Plan Service and Operational Level Agreement(s) Transfer to Production Plan Infrastructure Plan Infrastructure Design Infrastructure Technical Specification Build Development Environment Build Test Environment Build UAT Environment Build OAT Environment Build Training Environment Build Production Environment Decommission Unused Environments Detailed Estimates Confirmed Estimates Project Management – Planning, Resource, Scheduling Risk, Actions, Issues and Dependencies Management Reporting and Communications Management Change Management March 2, 2014 15 Artefact View Of Integrated Project Delivery Process: 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: Artefact View Integrates Different Activity Lifecycles Strategy, Business Planning and Business Analysis Project Management Cycle Solution Delivery - Implementation and Deployment Lifecycle Business Concept Initial Discovery Requirements Elicitation Decision to Proceed Requirements Management and Change Management Operations and Use Initiate Plan Execute and Control Close Setup and Prepare Implement Develop Test Deploy Manage Evolve Solution Architecture and Design Solution Architecture Solution Design Solution Specification and Change Management March 2, 2014 17 Initial Focus Area – Business Engagement And Solution Definition: Initial Focus Area – Business Engagement And Solution Definition Project Stages/ Timeline Project Activity/ Function Concept Initiate Plan Design Build Test Deploy Manage and Operate Project Management Focus on these project stages and project activities will ensure that the project foundations are sound Business Function Business Analysis Solution Architecture Implementation and Delivery Test and Quality Organisation Readiness Service Management Infrastructure and Communications Time Business Functions/ Roles Getting This Right … … Means Problems Will Be Avoided At Later Stages March 2, 2014 18 Artefact View Of Initial Focus Area – Business Engagement And Solution Definition: Artefact View Of Initial Focus Area – Business Engagement And Solution Definition Establishes solid foundations on which to build solution delivery and implementation Concept Initiate Plan Design Project Management Business Function Business Analysis Solution Architecture Solution Concept/ Requirements Document Rough Order of Magnitude Estimate Project Charter Project Initiation Document Business Case Project Plan Project Resource Plan Functional Requirements As Is Process Definition Benefits Schedule and Benefits Realisation Plan To Be Process Definition Solution Architecture High Level Design Non Functional Requirements Detailed Solution Design/ Functional Specification March 2, 2014 19 Initial Focus Area – Business Engagement And Solution Definition: Initial Focus Area – Business Engagement And Solution Definition March 2, 2014 20 Initial Focus Area – Business Engagement And Solution Definition And Validation: 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: 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: Initial Focus Area – Business Engagement And Solution Definition And Validation Project Stages/ Timeline Project Activity/ Function Concept Initiate Plan Design Build Test Deploy Manage and Operate Project Management Solution Concept/ Requirements Business Case Functional Requirements High Level Design Benefits Schedule and Benefits Realisation Plan Business Function Business Analysis Solution Architecture Implementation and Delivery Test and Quality Organisation Readiness Service Management Infrastructure and Communications Time Business Functions/ Roles Getting These Wrong … … Means Problems Will Occur During The Project March 2, 2014 23 Initial Focus Area – Business Engagement And Solution Definition And Validation: 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: Weaknesses In Business Analysis And Solution Design Capabilities At The Root of Many Project Failures Business Needs Not Met Opportunities Lost Investment Wasted Inadequate Business Case, Undefined Problem/Need Business Benefits Not Measured Poor Analysis Practices Business Requirements Not Captured Poor Requirements Poor Strategic Alignment Poor Focus on Business Needs Inadequate Resource Allocation and Prioritisation Inadequate Business Involvement Poor Solution Design Inadequately Explored Solution Options Solution Design Not Aligned to Business Needs Large Project, Complex, Difficult Changes and Processes Large Project Team and Multiple Stakeholders Size/Capacity/Complexity Uncertainly/ Ambiguity Unproven Technology Dynamic, Changing Environment March 2, 2014 25 Analysis And Solution Design-Related Causes Of Failures: Analysis And Solution Design-Related Causes Of Failures Business Needs Not Met Opportunities Lost Investment Wasted Inadequate Business Case, Undefined Problem/Need Business Benefits Not Measured Poor Analysis Practices Business Requirements Not Captured Poor Requirements Poor Strategic Alignment Poor Focus on Business Needs Inadequate Resource Allocation and Prioritisation Inadequate Business Involvement Poor Solution Design Inadequately Explored Solution Options Solution Design Not Aligned to Business Needs Large Project, Complex, Difficult Changes and Processes Large Project Team and Multiple Stakeholders Size/Capacity/Complexity Uncertainly/ Ambiguity Unproven Technology Dynamic, Changing Environment March 2, 2014 26 Project Gates: Project Gates Project Stages/ Timeline Project Activity/ Function Concept Initiate Plan Design Build Test Deploy Manage and Operate Project Management Gate 0 Gate 1 Gate 2 Gate 3 Gate 4 Gate 5 Gate 6 Gate 7 Business Function Business Analysis Solution Architecture Implementation and Delivery Test and Quality Organisation Readiness Service Management Infrastructure and Communications Time Business Functions/ Roles March 2, 2014 27 Project Gates: Pro ject 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 Process March 2, 2014 29 Phase Phase Gate Sent Back for Rework Gate Entry Criteria Gate Successful Exit STOP Project Stopped Project Process Gates: Project Process Gates March 2, 2014 30 Concept Initiate Plan Design Test Build Deploy Operate Gate 0 Gate 1 Gate 2 Gate 3 Gate 4 Gate 5 Gate 6 Gate 7 Project Process Gates: Project Process Gates March 2, 2014 31 Concept Initiate Plan Design Test Build Deploy Operate Gate 0 Validate Solution Concept and Estimates and Make Go/No Go Decision Gate 1 Gate 2 Gate 3 Gate 4 Gate 5 Gate 6 Gate 7 Validate Business Case and Make Go/No Go Decision Validate Plan, High-Level Design, Benefits, Readiness to Proceed to Detailed Design and Make Go/No Go Decision Build Review, Organisation Design Review, Readiness to Proceed to System Test and UAT Validate Detailed Design, Readiness to Proceed to Build and Make Go/No Go Decision Test Review, Organisation Change Review, Training Review, Service Planning Review Go Live Readiness Review, Staffing and Training Review Benefits Realisation Validation, Lessons Learned Sample Gate Review for Gate 3 – Before Move To Implementation/Development: 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: Artefact -Based Status View Of Project Concept Initiate Plan Design Build Test Deploy Operate Project Management Business Function Business Analysis Solution Architecture Delivery Test and Quality Organisation Readiness Service Management Infrastructure Solution Concept/ Requirements Document Rough Order of Magnitude Estimate Project Charter Project Initiation Document Business Case Project Plan Project Resource Plan Functional Requirements As Is Process Definition Benefits Schedule and Benefits Realisation Plan User Acceptance Test Results Benefits Realisation Review Lessons Learned To Be Process Definition User Acceptance Test Design and Plan Standard Operating Procedures Documentation Library Solution Architecture High Level Design Non Functional Requirements Detailed Solution Design/ Functional Specification Data Audit Data Design and Data Migration Plan Data Migration Results Data Migration Test Data Migration to Live Results Go Live Support Configuration Management Approach and Plan` Technical/Build Specification Build Documentation Unit Test Results Integration Test Results System Test Plan Results UAT Changes and Rework Deploy to Production Results Support and Operations Documentation Test Strategy Functional Test Design and Plan Non-Functional Test Design and Plan Integration Test Results System Test Results Operational Readiness Review Management Team Briefing Communications Strategy and Plan Change Impact Assessment Organisation Design Develop Training Material Detailed Communications Plan Training Needs Analysis Change Action Plan Role Definition Training Schedule Organisation and Staffing Implementation Training Delivery Service Impact Assessment Service Level Requirements Access and Security Definition Operations Acceptance Testing Design and Plan Operations Acceptance Testing Results Service Definition Functional Test Results Non-Functional Test Results Integration Test Design and Plan System Test Design and Plan Service and Operational Level Agreement(s) Transfer to Production Plan Infrastructure Plan Infrastructure Design Infrastructure Technical Specification Build Development Environment Build Test Environment Build UAT Environment Build OAT Environment Build Training Environment Build Production Environment Decommission Unused Environments Detailed Estimates Confirmed Estimates March 2, 2014 33 Consistent View Of Projects: Consistent View Of Projects March 2, 2014 34 Artefact-Based Status View Of Project: 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: Summary Provides a c onsistent 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: March 2, 2014 37 More Information Alan McSweeney http://ie.linkedin.com/in/alanmcsweeney

Add a comment

Related presentations

Related pages

Integrated project delivery - Wikipedia, the free encyclopedia

Integrated project delivery (IPD), ... even in a single business, ... Is integrated project design the solution?
Read more

Service Engagement Models - Cynosure Solutions ...

Service Engagement Models Flexibility That Works for You. Based on the volatile scenario of today’s market, enterprise software projects are gaining more ...
Read more

Global delivery model - Wikipedia, the free encyclopedia

... Global Delivery Model is typically associated with companies engaged in IT consulting and services delivery business and using a model ... model of ...
Read more

TCS: Global Network Delivery Model™ (GNDM™)

... can provide you with 24/7 solutions ... Our unique global engagement model allows you to ... By leveraging its Global Network Delivery Model ...
Read more

Integrated Business Plan 2013–2014 | Shared Services Canada

Integrated Business Plan ... This integrated solution will replace the 63 individual email ... Implement the partnership engagement models developed ...
Read more

Integrated Business Plan 2012 – 2013 | Shared Services ...

Integrated Business Plan 2012 ... showing it is responsible for “Enterprise & Business Project Delivery, ... Projects and business solutions implemented ...
Read more

Project development and delivery - Network Rail - we run ...

Project Development & Delivery Project Development & Delivery Supporting Document Our ambition is to be the best rail infrastructure project delivery
Read more

Solutions | Oracle

Oracle’s modern business solutions ... Address complex challenges with integrated solutions ... Intel Boosts Engagement by Activating Look-Alike Models;
Read more