This document discusses the role and importance of enterprise business analysis as a strategic capability for achieving business and IT alignment and driving innovation. Some key points:
- Enterprise business analysis can help translate business strategy into objectives, ensure IT solution delivery is aligned to strategy/objectives, and contribute to solution delivery governance.
- It involves analyzing business requirements and processes associated with changes, defining business solutions to deliver requirements/processes, and rebuilding the conversation between business and IT.
- Multiple levels of business analysis (enterprise, functional, IT) are needed to effectively prevent fragmentation across the organization and deliver solutions in response to business needs from strategy through delivery.
- Without this capability, IT risks delivering solutions that are not
Review of Information Technology Function Critical Capability ModelsAlan McSweeney
IT Function critical capabilities are key areas where the IT function needs to maintain significant levels of competence, skill and experience and practise in order to operate and deliver a service. There are several different IT capability frameworks. The objective of these notes is to assess the suitability and applicability of these frameworks. These models can be used to identify what is important for your IT function based on your current and desired/necessary activity profile.
Capabilities vary across organisation – not all capabilities have the same importance for all organisations. These frameworks do not readily accommodate variability in the relative importance of capabilities.
The assessment approach taken is to identify a generalised set of capabilities needed across the span of IT function operations, from strategy to operations and delivery. This generic model is then be used to assess individual frameworks to determine their scope and coverage and to identify gaps.
The generic IT function capability model proposed here consists of five groups or domains of major capabilities that can be organised across the span of the IT function:
1. Information Technology Strategy, Management and Governance
2. Technology and Platforms Standards Development and Management
3. Technology and Solution Consulting and Delivery
4. Operational Run The Business/Business as Usual/Service Provision
5. Change The Business/Development and Introduction of New Services
In the context of trends and initiatives such as outsourcing, transition to cloud services and greater platform-based offerings, should the IT function develop and enhance its meta-capabilities – the management of the delivery of capabilities? Is capability identification and delivery management the most important capability? Outsourced service delivery in all its forms is not a fire-and-forget activity. You can outsource the provision of any service except the management of the supply of that service.
The following IT capability models have been evaluated:
• IT4IT Reference Architecture https://www.opengroup.org/it4it contains 32 functional components
• European e-Competence Framework (ECF) http://www.ecompetences.eu/ contains 40 competencies
• ITIL V4 https://www.axelos.com/best-practice-solutions/itil has 34 management practices
• COBIT 2019 https://www.isaca.org/resources/cobit has 40 management and control processes
• APQC Process Classification Framework - https://www.apqc.org/process-performance-management/process-frameworks version 7.2.1 has 44 major IT management processes
• IT Capability Maturity Framework (IT-CMF) https://ivi.ie/critical-capabilities/ contains 37 critical capabilities
The following model has not been evaluated
• Skills Framework for the Information Age (SFIA) - http://www.sfia-online.org/ lists over 100 skills
Creating A Business Focussed Information Technology StrategyAlan McSweeney
This presentation describes a structured approach to creating a business-focussed information technology strategy.
An effective business-oriented IT strategy is an opportunity to resolve the disconnection and to ensure the IT function is able to and does respond to business needs and is trusted by the business to provide IT solutions.
The IT strategy will consist of static structural elements relating to the organisation of the IT function:
• Capabilities – skills and abilities the IT function should possess and be able to use effectively and efficiently
• IT Function Structure – the organisation and arrangement of the sub-functions and their responsibilities and relationships
• Operating Model – how the IT function work and delivers value and the processes it implements and operates
• Staffing And Roles – the numbers of people, their roles, responsibilities, expected skills, experience and abilities, workload, reporting structures and expected ways of operating
It will also include dynamic elements relating to initiatives, both enabling initiatives within the IT function and specific business initiatives required to achieve the business strategy.
Digital strategy is a statement about the organisation’s digital positioning, competitors and customer and collaborator needs and behaviour to achieve a direction for innovation, communication, transaction and promotion.
This describes facets of exploring the options for digital to ensure that the resulting strategy is realistic, achievable and will deliver a return.
Enterprise Architecture needs to be involved in the development of digital architecture. Digital architecture needs to be at the core of the organisation’s wider Enterprise Architecture.
Technology generally accelerates existing business momentum rather than being the originator of momentum. Digital is not a panacea. Digital interactions with third parties gives rise to expectations
Digital will make weaknesses in business processes and underlying technology very evident very quickly. Iterate through digital initiatives, starting small and focussed, learning from experience.
How to develop and govern a Technology Strategy in 10 weeksLeo Barella
This presentation covers the organizational layout, EA Services and EA Governance processes necessary to develop and govern a technology strategy effectively.
Review of Information Technology Function Critical Capability ModelsAlan McSweeney
IT Function critical capabilities are key areas where the IT function needs to maintain significant levels of competence, skill and experience and practise in order to operate and deliver a service. There are several different IT capability frameworks. The objective of these notes is to assess the suitability and applicability of these frameworks. These models can be used to identify what is important for your IT function based on your current and desired/necessary activity profile.
Capabilities vary across organisation – not all capabilities have the same importance for all organisations. These frameworks do not readily accommodate variability in the relative importance of capabilities.
The assessment approach taken is to identify a generalised set of capabilities needed across the span of IT function operations, from strategy to operations and delivery. This generic model is then be used to assess individual frameworks to determine their scope and coverage and to identify gaps.
The generic IT function capability model proposed here consists of five groups or domains of major capabilities that can be organised across the span of the IT function:
1. Information Technology Strategy, Management and Governance
2. Technology and Platforms Standards Development and Management
3. Technology and Solution Consulting and Delivery
4. Operational Run The Business/Business as Usual/Service Provision
5. Change The Business/Development and Introduction of New Services
In the context of trends and initiatives such as outsourcing, transition to cloud services and greater platform-based offerings, should the IT function develop and enhance its meta-capabilities – the management of the delivery of capabilities? Is capability identification and delivery management the most important capability? Outsourced service delivery in all its forms is not a fire-and-forget activity. You can outsource the provision of any service except the management of the supply of that service.
The following IT capability models have been evaluated:
• IT4IT Reference Architecture https://www.opengroup.org/it4it contains 32 functional components
• European e-Competence Framework (ECF) http://www.ecompetences.eu/ contains 40 competencies
• ITIL V4 https://www.axelos.com/best-practice-solutions/itil has 34 management practices
• COBIT 2019 https://www.isaca.org/resources/cobit has 40 management and control processes
• APQC Process Classification Framework - https://www.apqc.org/process-performance-management/process-frameworks version 7.2.1 has 44 major IT management processes
• IT Capability Maturity Framework (IT-CMF) https://ivi.ie/critical-capabilities/ contains 37 critical capabilities
The following model has not been evaluated
• Skills Framework for the Information Age (SFIA) - http://www.sfia-online.org/ lists over 100 skills
Creating A Business Focussed Information Technology StrategyAlan McSweeney
This presentation describes a structured approach to creating a business-focussed information technology strategy.
An effective business-oriented IT strategy is an opportunity to resolve the disconnection and to ensure the IT function is able to and does respond to business needs and is trusted by the business to provide IT solutions.
The IT strategy will consist of static structural elements relating to the organisation of the IT function:
• Capabilities – skills and abilities the IT function should possess and be able to use effectively and efficiently
• IT Function Structure – the organisation and arrangement of the sub-functions and their responsibilities and relationships
• Operating Model – how the IT function work and delivers value and the processes it implements and operates
• Staffing And Roles – the numbers of people, their roles, responsibilities, expected skills, experience and abilities, workload, reporting structures and expected ways of operating
It will also include dynamic elements relating to initiatives, both enabling initiatives within the IT function and specific business initiatives required to achieve the business strategy.
Digital strategy is a statement about the organisation’s digital positioning, competitors and customer and collaborator needs and behaviour to achieve a direction for innovation, communication, transaction and promotion.
This describes facets of exploring the options for digital to ensure that the resulting strategy is realistic, achievable and will deliver a return.
Enterprise Architecture needs to be involved in the development of digital architecture. Digital architecture needs to be at the core of the organisation’s wider Enterprise Architecture.
Technology generally accelerates existing business momentum rather than being the originator of momentum. Digital is not a panacea. Digital interactions with third parties gives rise to expectations
Digital will make weaknesses in business processes and underlying technology very evident very quickly. Iterate through digital initiatives, starting small and focussed, learning from experience.
How to develop and govern a Technology Strategy in 10 weeksLeo Barella
This presentation covers the organizational layout, EA Services and EA Governance processes necessary to develop and govern a technology strategy effectively.
It is well known that an effective PMO is key to successful and efficient program and project execution. In other words, doing things “right”. Enterprise Architecture is the discipline that plans and monitors enterprise transformation and aligns the business strategy with information technology capabilities. In other words, doing the “right things” to support the business.
Why is it organizations despite having both of these disciplines still struggle with effective enterprise transformation? What can we done to use these disciplines more effectively to effect better business outcomes? What are the roles of each discipline and how do they work together to create business value?
In this presentation, Riaz will address these questions and will provide real life examples that can help build a strong relationship between the PMO and Enterprise Architecture.
Learning Objectives:
• How to build a strong relationship between the PMO and Enterprise Architecture (EA) to deliver positive outcomes for your organization
• Identify the different roles and functions of the PMO and EA as well as their similarities
Business Architecture is a multi dimensional discipline primarily focused on organizational structure and performance in terms of business strategy, business functions, capabilities, roles and their relationships. Implementing and executing Business Strategy goals is among Business Architecture’s focus areas.
This presentation and discussion will focus on Strategic planning relationship with Business Architecture. Employing Business Architecture techniques, Corporate Planners can translate business strategy goals into actions, identify critical areas of enterprise change and transformation while identifying and mitigating related risks.
Introduction to Enterprise architecture and the steps to perform an Enterpris...Prashanth Panduranga
This presentation was used to introduce Enterprise Architecture, Introduction to how to perform an Enterprise Architecture Assessment followed by TechSharp introduction.
Deliverables in the presentation is not clear, the slides represent what was shown as part of the demo.
List of deliverables:
Application Rationalization framework
Portfolio Analysis framework
Road Map
Current state analysis
Target State establishing process
System Context
System Landscape
How to Articulate the Value of Enterprise Architecturecccamericas
Ever struggled with the question, What is the Value of Enterprise Architecture? In this facilitated conversation, Michael Fulton will share his perspective on Enterprise Architecture and the value it provides to the CIO, to IT, and to the business.
Come ready to engage, because in the conversation we will discuss:
•The EA 7-year itch
•Several External Perspectives on EA Value
•The CC&C perspective on a simplified approach to EA Value
•Ensuring your perspective on EA Value is relevant for your stakeholders
At the end of this conversation, you should walk away with:
•A new perspective on the value of EA
•Tips and tricks on how to articulate and quantify EA Value for your key stakeholders.
Critical Review of Open Group IT4IT Reference ArchitectureAlan McSweeney
This reviews the Open Group’s IT4IT Reference Architecture (https://www.opengroup.org/it4it) with respect to other operational frameworks to determine its suitability and applicability to the IT operating function.
IT4IT is intended to be a reference architecture for the management of the IT function. It aims to take a value chain approach to create a model of the functions that IT performs and the services it provides to assist organisations in the identification of the activities that contribute to business competitiveness. It is intended to be an integrated framework for the management of IT that emphasises IT service lifecycles.
This paper reviews what is meant by a value-chain, with special reference to the Supply Chain Operations Reference (SCOR) model (https://www.apics.org/apics-for-business/frameworks/scor). the most widely used and most comprehensive such model.
The SCOR model is part of wider set of operations reference models that describe a view of the critical elements in a value chain:
• Product Life Cycle Operations Reference model (PLCOR) - Manages the activities for product innovation and product and portfolio management
• Customer Chain Operations Reference model (CCOR) - Manages the customer interaction processes
• Design Chain Operations Reference model (DCOR) - Manages the product and service development processes
• Managing for Supply Chain Performance (M4SC) - Translates business strategies into supply chain execution plans and policies
It also compares the IT4IT Reference Architecture and its 32 functional components to other frameworks that purport to identify the critical capabilities of the IT function:
• IT Capability Maturity Framework (IT-CMF) https://ivi.ie/critical-capabilities/ contains 37 critical capabilities
• Skills Framework for the Information Age (SFIA) - http://www.sfia-online.org/ lists over 100 skills
• European e-Competence Framework (ECF) http://www.ecompetences.eu/ contains 40 competencies
• ITIL IT Service Management https://www.axelos.com/best-practice-solutions/itil
• COBIT 2019 https://www.isaca.org/resources/cobit has 40 management and control processes
Introduction to Business Architecture - Part 2Alan McSweeney
The first part is available at: https://www.slideshare.net/alanmcsweeney/introduction-to-business-architecture-part-1.
This material describes conducting a specific business architecture engagement. The engagement process is generic and needs to be adapted to each specific application and use. The engagement is a formal process for gathering information and creating a new business function model based on an analysis of that information.
The objective is to create a realistic and achievable target business architecture to achieve the desired business change.
Business architecture is a structured approach to analysing the operation of an existing business function or entire organisation with a view to improving its operations or developing a new business function, with a strong focus on processes and technology. Business architecture is not about business requirements – it is about business solutions and organisation changes to deliver business objectives.
Defining the business value proposition of EA and PPM
Eliminating project risks
Accelerating project execution
Managing project and architecture inter-dependencies
Delivering realized value
Improving collaboration of Architecture and PMO
Stepping-stones of enterprise-architecture: Process and practice in the real...Tetradian Consulting
What do we do when we’re doing enterprise architecture? What issues do we tackle, in what sequence, for what business reasons, for what business value? And how do we get results fast? This presentation describes how to adapt the Architectural Development Method (ADM) from The Open Group Architecture Framework (TOGAF) for use in all types of enterprise architecture - for IT and beyond - and at all architecture maturity-levels.
[Presentation at TOGAF Conference, London, April 2009. Applies to TOGAF versions 8.1 and 9. Copyright (c) Tetradian Consulting 2009]
IT Strategy I Best Practices I NuggetHubRichardNowack
IT strategy is a plan of action to create an information technology capability for maximum, and sustainable value for an organization. In this business best practice slide deck you learn how to assess and setup an IT strategy and a transformation plan.
We provide you with the following best practices:
- IT Strategy Definition and Introduction
- IT Strategy Frameworks
- IT Strategy Approaches and Transformation
During last few years, role of Enterprise Architecture has expanded from technical to strategic in an Organization. This slide deck presents: Using Enterprise Architecture in your Organization.
Unpacking TOGAF's 'Phase B': Business Transformation, Business Architecture a...Tetradian Consulting
The Open Group Architecture Framework (TOGAF) is a structured method for developing enterprise architectures. As standard, its 'Phase B', 'Business Architecture', is an IT-centric way of viewing the business: we need to 'unpack' it to move to a more holistic view of the enterprise in which IT takes a more realistic role.
[Presentation at TOGAF Conference, Paris, April 2007. Describes TOGAF 8.1, but most details apply as much to TOGAF 9. Copyright (c) Tetradian Consulting 2007]
It is well known that an effective PMO is key to successful and efficient program and project execution. In other words, doing things “right”. Enterprise Architecture is the discipline that plans and monitors enterprise transformation and aligns the business strategy with information technology capabilities. In other words, doing the “right things” to support the business.
Why is it organizations despite having both of these disciplines still struggle with effective enterprise transformation? What can we done to use these disciplines more effectively to effect better business outcomes? What are the roles of each discipline and how do they work together to create business value?
In this presentation, Riaz will address these questions and will provide real life examples that can help build a strong relationship between the PMO and Enterprise Architecture.
Learning Objectives:
• How to build a strong relationship between the PMO and Enterprise Architecture (EA) to deliver positive outcomes for your organization
• Identify the different roles and functions of the PMO and EA as well as their similarities
Business Architecture is a multi dimensional discipline primarily focused on organizational structure and performance in terms of business strategy, business functions, capabilities, roles and their relationships. Implementing and executing Business Strategy goals is among Business Architecture’s focus areas.
This presentation and discussion will focus on Strategic planning relationship with Business Architecture. Employing Business Architecture techniques, Corporate Planners can translate business strategy goals into actions, identify critical areas of enterprise change and transformation while identifying and mitigating related risks.
Introduction to Enterprise architecture and the steps to perform an Enterpris...Prashanth Panduranga
This presentation was used to introduce Enterprise Architecture, Introduction to how to perform an Enterprise Architecture Assessment followed by TechSharp introduction.
Deliverables in the presentation is not clear, the slides represent what was shown as part of the demo.
List of deliverables:
Application Rationalization framework
Portfolio Analysis framework
Road Map
Current state analysis
Target State establishing process
System Context
System Landscape
How to Articulate the Value of Enterprise Architecturecccamericas
Ever struggled with the question, What is the Value of Enterprise Architecture? In this facilitated conversation, Michael Fulton will share his perspective on Enterprise Architecture and the value it provides to the CIO, to IT, and to the business.
Come ready to engage, because in the conversation we will discuss:
•The EA 7-year itch
•Several External Perspectives on EA Value
•The CC&C perspective on a simplified approach to EA Value
•Ensuring your perspective on EA Value is relevant for your stakeholders
At the end of this conversation, you should walk away with:
•A new perspective on the value of EA
•Tips and tricks on how to articulate and quantify EA Value for your key stakeholders.
Critical Review of Open Group IT4IT Reference ArchitectureAlan McSweeney
This reviews the Open Group’s IT4IT Reference Architecture (https://www.opengroup.org/it4it) with respect to other operational frameworks to determine its suitability and applicability to the IT operating function.
IT4IT is intended to be a reference architecture for the management of the IT function. It aims to take a value chain approach to create a model of the functions that IT performs and the services it provides to assist organisations in the identification of the activities that contribute to business competitiveness. It is intended to be an integrated framework for the management of IT that emphasises IT service lifecycles.
This paper reviews what is meant by a value-chain, with special reference to the Supply Chain Operations Reference (SCOR) model (https://www.apics.org/apics-for-business/frameworks/scor). the most widely used and most comprehensive such model.
The SCOR model is part of wider set of operations reference models that describe a view of the critical elements in a value chain:
• Product Life Cycle Operations Reference model (PLCOR) - Manages the activities for product innovation and product and portfolio management
• Customer Chain Operations Reference model (CCOR) - Manages the customer interaction processes
• Design Chain Operations Reference model (DCOR) - Manages the product and service development processes
• Managing for Supply Chain Performance (M4SC) - Translates business strategies into supply chain execution plans and policies
It also compares the IT4IT Reference Architecture and its 32 functional components to other frameworks that purport to identify the critical capabilities of the IT function:
• IT Capability Maturity Framework (IT-CMF) https://ivi.ie/critical-capabilities/ contains 37 critical capabilities
• Skills Framework for the Information Age (SFIA) - http://www.sfia-online.org/ lists over 100 skills
• European e-Competence Framework (ECF) http://www.ecompetences.eu/ contains 40 competencies
• ITIL IT Service Management https://www.axelos.com/best-practice-solutions/itil
• COBIT 2019 https://www.isaca.org/resources/cobit has 40 management and control processes
Introduction to Business Architecture - Part 2Alan McSweeney
The first part is available at: https://www.slideshare.net/alanmcsweeney/introduction-to-business-architecture-part-1.
This material describes conducting a specific business architecture engagement. The engagement process is generic and needs to be adapted to each specific application and use. The engagement is a formal process for gathering information and creating a new business function model based on an analysis of that information.
The objective is to create a realistic and achievable target business architecture to achieve the desired business change.
Business architecture is a structured approach to analysing the operation of an existing business function or entire organisation with a view to improving its operations or developing a new business function, with a strong focus on processes and technology. Business architecture is not about business requirements – it is about business solutions and organisation changes to deliver business objectives.
Defining the business value proposition of EA and PPM
Eliminating project risks
Accelerating project execution
Managing project and architecture inter-dependencies
Delivering realized value
Improving collaboration of Architecture and PMO
Stepping-stones of enterprise-architecture: Process and practice in the real...Tetradian Consulting
What do we do when we’re doing enterprise architecture? What issues do we tackle, in what sequence, for what business reasons, for what business value? And how do we get results fast? This presentation describes how to adapt the Architectural Development Method (ADM) from The Open Group Architecture Framework (TOGAF) for use in all types of enterprise architecture - for IT and beyond - and at all architecture maturity-levels.
[Presentation at TOGAF Conference, London, April 2009. Applies to TOGAF versions 8.1 and 9. Copyright (c) Tetradian Consulting 2009]
IT Strategy I Best Practices I NuggetHubRichardNowack
IT strategy is a plan of action to create an information technology capability for maximum, and sustainable value for an organization. In this business best practice slide deck you learn how to assess and setup an IT strategy and a transformation plan.
We provide you with the following best practices:
- IT Strategy Definition and Introduction
- IT Strategy Frameworks
- IT Strategy Approaches and Transformation
During last few years, role of Enterprise Architecture has expanded from technical to strategic in an Organization. This slide deck presents: Using Enterprise Architecture in your Organization.
Unpacking TOGAF's 'Phase B': Business Transformation, Business Architecture a...Tetradian Consulting
The Open Group Architecture Framework (TOGAF) is a structured method for developing enterprise architectures. As standard, its 'Phase B', 'Business Architecture', is an IT-centric way of viewing the business: we need to 'unpack' it to move to a more holistic view of the enterprise in which IT takes a more realistic role.
[Presentation at TOGAF Conference, Paris, April 2007. Describes TOGAF 8.1, but most details apply as much to TOGAF 9. Copyright (c) Tetradian Consulting 2007]
The Centre Cannot Hold: Making IT Architecture Relevant In A Post IT WorldAlan McSweeney
Business has a consistently poor experience of the internal IT function. It is now all too easy for the business to bypass the central IT function. There is a business shift to cloud service providers offering infrastructure-less solutions with no perceived IT involvement. Outsourcing and the divestment of IT functions in response to business wishes to remove the overhead. The business need to respond to the interrelated developments of digital, mobile and social computing and perceived inability of the central IT function to respond.
If the IT function cannot react to the requirements of the business due to business pressures, the business will go elsewhere. Shadow IT - the acquisition of IT solutions outside the control of the IT function - is an unpleasant and common reality. 50% of IT expenditure is routinely spent outside the control of the IT function. Shadow IT is a symptom of a post-IT world.
The central IT function loses relevance and control. Businesses reduce their reliance on the core IT function.
IT architecture should act as a glue joining the business strategy to the IT strategy. IT architecture needs to operate as an internal business consulting And advisory function. An effective business oriented IT architecture function can get the correct balance between too little and too much, too slowly and too quickly. The IT Architecture team needs to operate as a team rather than a set of siloed internally focussed IT roles, involving business as well as technologists.
Conway's Law, Cognitive Diversity, Organisation Transformation And Solution D...Alan McSweeney
These topics may appear to be separate but are closely related to the need for an effective solution design process, approach and function.
Nearly 50 years ago, Dr Melvin Conway wrote a short and insightful article titled How Do Committees Invent? where he made a number of observations on the system and solution design process including “… organizations which design systems … are constrained to produce designs which are copies of the communication structures of these organizations.” which has become known as Conway’s Law. He identified organisation problems that lead to poor solution design.
Conway’s Law is a warning rather than a prediction. It provides an insight into the solution design problems that can occur if the solution design structures, processes and function are not optimised. What he describes does not have to happen but all too frequently does.
Cognitive Diversity has become a fashionable concept that is talked about more than implemented. It has been written about extensively by Dr Scott Page. The core concept is that “… a random group of intelligent problem solvers will outperform a group of the best problem solvers”.
The value of cognitive diversity to organisations is greatest in the thinking areas such as the solution design function. Managing diverse teams can be difficult and achieving cognitive diversity can be painful and challenging. Cognitive diversity of less value in pure operational and transactions areas where there is a reduced need for problem-solving.
Cognitive diversity protects the organisation against factors such as Cognitive Bias, Strategic Misrepresentation, Planning Fallacy, Optimism Bias, Focalism and Groupthink and their consequences.
Cognitive diversity protects against the effects of Conway’s Law.
Many organisations are attempting to transform themselves in response to external changes and drivers. Organisation transformation is frequently concerned with a migration from product-orientation to services-orientation characterised by responsiveness, customer centricity, self-service and flexibility. Information technology underpins successful and effective organisation transformation.
This is especially true of initiatives such as digital transformation. Digital transformation involves designing and implementing solutions across a wide range of application and system areas.
Being good at solution design means that solutions are defined, designed and delivered in a reliable, stable and innovative way to ensure that cost, time, required functionality and quality are constantly optimised to meet the needs of the business.
Good solution design mean:
• Being aware of all the options and selecting the most appropriate one subject to all constraints
• Avoiding all the conscious and unconscious biases that lead to bad solutions
Put simply, a cognitively diverse team designs better solutions.
Don’t Mention The “A” Word – Trends In Continuing Business And IT MisalignmentAlan McSweeney
Despite years of emphasising the need for IT and business alignment, the disconnect between business and IT continues. IT focuses too much of pure technology. However, business expectations cam be unrealistic, based on part on IT not explaining itself to the business. IT technology trends are not relevant the business. The business is concerned with the results of investment in IT and sees technology as means to an end and not as ends in themselves. IT needs to structure itself so alignment pervades the entire IT function. IT must embed business alignment in the way it operates to ensure it remains relevant to the business. IT needs to mediate between the business and suppliers and technologies, acting as a lens focussing business needs on appropriate solutions. The gulf is between business and IT seems to be getting wider. Failure to ensure this alignment may lead to the business bypassing IT and going straight to suppliers and service providers. Disintermediation of IT is central to the business plans of many internet-based service providers. Failure to systematise alignment will expose IT to the danger of becoming irrelevant.
Or how I learned to stop worrying and love Continuous Deployment...
Presentation by Tom Wilkie on 29/09/16 at SF Microservices Meetup.
In this talk I discuss the journey Weaveworks has been through building Weave Cloud, using all the laster buzzword-compliant techniques: Microservices, DevOps, Continuous Delivery, Kubernetes, Docker etc.
After unnecessary complexity has been reduced from the problem being solved, the scope of the solution to the problem is governed by the complexity of the problem. Complexity is needed to handle and process complexity. Systems acquire or accrete unnecessary complexity over time as originally unforeseen exceptions or changes are incorporated. It may be possible to reduce complexity by collapsing/compressing/combining/consolidating elements and by removing non-value-adding, duplicate, redundant activities. When unnecessary or accreted complexity in the problem being solved has been removed, you are left with necessary complexity that must be incorporated into the solution. Simple problems do not have complex solutions. Complex problems do not have simple solutions. The complexity factor of the proposed solution must match the complexity factor of the problem being resolved. Many system implementation and operational failures arise because of failure to understand and address the core complexity of the problem.
Investing Intelligently In The IT FunctionAlan McSweeney
Describes an approach to defining the competencies and capabilities required of the IT function and to use current levels of competence and importance of competency across all activity areas of the IT function to identify those areas at which getting better will yield the greatest return, allowing for targeted investment of resources to get good at what matters
This describes the concept of a Process Oriented Architecture. A Process Oriented Architecture is a way of linking process areas to actual (desired) interactions – customer (external interacting party) service journeys through the organisation. It allows two views of any process to be maintained and operated:
1. External view – that experienced by user
2. Internal view – that worked on by the organisational competency
An organisation will interact will multiple external parties. Each external party will have a number of interaction paths or journeys. These journeys are the routes of experience of external parties. These routes of experience need to be mapped (as) seamlessly (as possible) to internal organisational operational process competency groupings.
The interaction paths or journeys represent the Straight Through Processing that the customer (external party) wants to experience. The complexity of internal organisational operational process competency groupings needs to be masked from the customer (external party). Process Oriented Architecture is a key enabler of successful digital transformation.
Competence in sourcing is a core skill of the IT function. The IT function is becoming largely a manager of suppliers and service providers across a wide range of products, solutions and services. IT mediates between the business and the supplier ecosystem, acting as a lens focussing business needs on appropriate suppliers. When products and services are outsourced, the risks of the suppliers and service providers are inherited by the acquiring organisation. Sourcing should not be a “fire and forget” activity. Effective supplier selection and ongoing assessment, validation and management is an important skill for the IT function. The Service Organisation Controls audit approach can be adapted for use by the IT function to develop an approach to vendor governance.
Integrated Project and Solution Delivery And Business Engagement ModelAlan McSweeney
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 it is important to have an integrated project delivery approach that crosses these core dimensions.
This describes an integrated approach to solution delivery encompassing Stages - project stages/timeline, Activities - IT and business functions/ roles/ activities, Gates - project review and decision gates and Artefacts - project results and deliverables. This combines 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
It emphasises early business engagement and solution definition and validation to detail a solution that meet a clear and articulated business need that will deliver a realisable and achievable set of business benefits. It ensures that the complexity of what has to be delivered is understood so there is a strong and solid foundation for solution implementation, delivery and management and operation.
Introduction To Business Architecture – Part 1Alan McSweeney
This is the first of a proposed four part introduction to Business Architecture. It is intended to focus on activities associated with Business Architecture work and engagements.
Business change without a target business architecture and a plan is likely to result in a lack of success and even failure. An effective approach to business architecture and business architecture competency is required to address effectively the pressures on businesses to change. Business architecture connects business strategy to effective implementation and operation:
• Translates business strategic aims to implementations
• Defines the consequences and impacts of strategy
• Isolates focussed business outcomes
• Identifies the changes and deliverables that achieve business success
Enterprise Architecture without Solution Architecture and Business Architecture will not deliver on its potential. Business Architecture is an essential part of the continuum from theory to practice.
This Slideshare presentation is a partial preview of the full business document. To view and download the full document, please go here:
http://flevy.com/browse/business-document/it-strategy-209
This is a comprehensive document on Information Technology (IT) / Management Information Systems (MIS) Strategy.
This document includes IT strategy frameworks, critical success factors, detailed project approach and organizational structure, sample deliverables, and more.
Slides from a presentation given by Paul Turner to meetings of IIBA UK on 16 July and 12 August 2014.
Much has been written about technical and solution architectures, without due attention being given to how these work together with the Business Architecture.
It is easy to believe that those who are involved in business analysis, requirements definition and systems modelling do not need to consider the Business Architecture at all. This could not be further from the truth. This talk explains the rationale behind Business Architecture, what its main components are and why Business Analysts should ensure that they understand it and the influence it is likely to have on their work.
How to use ITIL Practitioner skills to impress the CEOPink Elephant EMEA
A hands-on workshop focusing on key IT related issues and trends including ITIL Practitioner & Business & IT Alignment. IT service management simulation that can be useful in any size organisation.
Business & IT Alignment : How ITIL Practitioner can bridge the gap. Communication is an imperative for success & this simulation shows you not only why, but how!
These slides - based on the webinar featuring Dennis Drogseth, VP of research at leading IT analyst firm Enterprise Management Associates (EMA), and Sasha Gilenson, founder and CEO at Evolven Software - examine how “tiered” or “blended” sources can bring fast time to value across performance management, change management and other use cases.
These slides cover:
- Why, and in what contexts, do IT organizations need to change to become more effective and valued?
- What is tiered or blended analytics, and how can it come to the rescue?
- How is blended analytics different from more traditional big data approaches?
Acquity Group is a business process and technology consulting firm. We are and end to end provider of strategy, process and technology solutions. This deck highlights our key competencies around IT Strategy, IT Governance & IT Operations
Critical success factors to develop and deliver a forward-looking BI strategy...SAP Analytics
sap.com/analytics - This SAPinsider #BI2015 session attendees will learn key elements of an effective BI strategy that benefits both IT and the core business alike.
A well-designed IT Service Delivery Model is critical to achieving success in IT management and operations. Many IT organizations focus on optimizing their technology assets -- the infrastructure and applications. However, in our experience, business value is achieved most effectively when technology assets and the IT service delivery model are integrated and work together seamlessly.
Comprehensive And Integrated Approach To Project Management And Solution Deli...Alan McSweeney
Describes a complete and integrated approach to solution delivery that encompasses project management, project portfolio management, business analysis and solution architecture and design
Effective solution delivery requires an integrated approach to projects across all key disciplines
Project portfolio management
Project management
Business analysis
Solution design
Having silos of expertise that do not communicate or co-operate leads to significant risk
KPIs are almost universally used in organizations of all types. But are they being used effectively? Are they making an impact on the system? Or are they expensive, consultant-driven projects that simply report performance? A well-designed KPI system provides the right agility to fit your business, and it keeps business in control.
In this webinar ( presentation), "Building a KPI Solution" you will
• Learn to discover and unleash the real value in your data
• Understand how you should plan for and design an effect KPI system
• Learn how to specify a solution, and how to avoid vendors that cannot deliver
This webinar (presentation) will also cover best practices in solution design, where to define your business logic, how to include analytics, and how to best work with the solution. Discover how organizations of all types are using actionable KPI systems to achieve business outcomes.
Benchmark Your Costs and Transform Your Source-to-Pay ProcessSAP Ariba
Reducing supply chain costs and meeting customer requirements continue to be the key supply chain priorities for many organizations. Indirect spend is a key cost driver, and managing strategic sourcing and tactical sourcing through a well-managed process lowers costs and improves execution capability. In this session, IGATE will instruct you how to benchmark yourself against your industry peers and set a goal to improve your success rate in transforming your source-to-pay process. You will also hear how other companies are experiencing success on their source-to-pay transformation journey.
Similar to Enterprise Business Analysis Capability - Strategic Asset for Business Alignment and Driving Innovation (20)
The data architecture of solutions is frequently not given the attention it deserves or needs. Frequently, too little attention is paid to designing and specifying the data architecture within individual solutions and their constituent components. This is due to the behaviours of both solution architects ad data architects.
Solution architecture tends to concern itself with functional, technology and software components of the solution
Data architecture tends not to get involved with the data aspects of technology solutions, leaving a data architecture gap. Combined with the gap where data architecture tends not to get involved with the data aspects of technology solutions, there is also frequently a solution architecture data gap. Solution architecture also frequently omits the detail of data aspects of solutions leading to a solution data architecture gap. These gaps result in a data blind spot for the organisation.
Data architecture tends to concern itself with post-individual solutions. Data architecture needs to shift left into the domain of solutions and their data and more actively engage with the data dimensions of individual solutions. Data architecture can provide the lead in sealing these data gaps through a shift-left of its scope and activities as well providing standards and common data tooling for solution data architecture
The objective of data design for solutions is the same as that for overall solution design:
• To capture sufficient information to enable the solution design to be implemented
• To unambiguously define the data requirements of the solution and to confirm and agree those requirements with the target solution consumers
• To ensure that the implemented solution meets the requirements of the solution consumers and that no deviations have taken place during the solution implementation journey
Solution data architecture avoids problems with solution operation and use:
• Poor and inconsistent data quality
• Poor performance, throughput, response times and scalability
• Poorly designed data structures can lead to long data update times leading to long response times, affecting solution usability, loss of productivity and transaction abandonment
• Poor reporting and analysis
• Poor data integration
• Poor solution serviceability and maintainability
• Manual workarounds for data integration, data extract for reporting and analysis
Data-design-related solution problems frequently become evident and manifest themselves only after the solution goes live. The benefits of solution data architecture are not always evident initially.
Solution Architecture and Solution Estimation.pdfAlan McSweeney
Solution architects and the solution architecture function are ideally placed to create solution delivery estimates
Solution architects have the knowledge and understanding of the solution constituent component and structure that is needed to create solution estimate:
• Knowledge of solution options
• Knowledge of solution component structure to define a solution breakdown structure
• Knowledge of available components and the options for reuse
• Knowledge of specific solution delivery constraints and standards that both control and restrain solution options
Accurate solution delivery estimates are need to understand the likely cost/resources/time/options needed to implement a new solution within the context of a range of solutions and solution options. These estimates are a key input to investment management and making effective decisions on the portfolio of solutions to implement. They enable informed decision-making as part of IT investment management.
An estimate is not a single value. It is a range of values depending on a number of conditional factors such level of knowledge, certainty, complexity and risk. The range will narrow as the level of knowledge and uncertainty decreases
There is no easy or magic way to create solution estimates. You have to engage with the complexity of the solution and its components. The more effort that is expended the more accurate the results of the estimation process will be. But there is always a need to create estimates (reasonably) quickly so a balance is needed between effort and quality of results.
The notes describe a structured solution estimation process and an associated template. They also describe the wider context of solution estimates in terms of IT investment and value management and control.
Validating COVID-19 Mortality Data and Deaths for Ireland March 2020 – March ...Alan McSweeney
This analysis seeks to validate published COVID-19 mortality statistics using mortality data derived from general mortality statistics, mortality estimated from population size and mortality rates and death notice data
Analysis of the Numbers of Catholic Clergy and Members of Religious in Irelan...Alan McSweeney
This analysis looks at the changes in the numbers of priests and nuns in Ireland for the years 1926 to 2016. It combines data from a range of sources to show the decline in the numbers of priests and nuns and their increasing age profile.
This analysis consists of the following sections:
• Summary - this highlights some of the salient points in the analysis.
• Overview of Analysis - this describes the approach taken in this analysis.
• Context – this provides background information on the number of Catholics in Ireland as a context to this analysis.
• Analysis of Census Data 1926 – 2016 - this analyses occupation age profile data for priests and nuns. It also includes sample projections on the numbers of priests and nuns.
• Analysis of Catholic Religious Mortality 2014-2021 - this analyses death notice data from RIP.ie to shows the numbers of priests and nuns that have died in the years 2014 to 2021. It also looks at deaths of Irish priests and nuns outside Ireland and at the numbers of countries where Irish priests and nuns have worked.
• Analysis of Data on Catholic Clergy From Other Sources - this analyses data on priests and nuns from other sources.
• Notes on Data Sources and Data Processing - this lists the data sources used in this analysis.
IT Architecture’s Role In Solving Technical Debt.pdfAlan McSweeney
Technical debt is an overworked term without an effective and common agreed understanding of what exactly it is, what causes it, what are its consequences, how to assess it and what to do about it.
Technical debt is the sum of additional direct and indirect implementation and operational costs incurred and risks and vulnerabilities created because of sub-optimal solution design and delivery decisions.
Technical debt is the sum of all the consequences of all the circumventions, budget reduction, time pressure, lack of knowledge, manual workarounds, short-cuts, avoidance, poor design and delivery quality and decisions to remove elements from solution scope and failure to provide foundational and backbone solution infrastructure.
Technical debt leads to a negative feedback cycle with short solution lifespan, earlier solution replacement and short-term tactical remedial actions.
All the disciplines within IT architecture have a role to play in promoting an understanding of and in the identification of how to resolve technical debt. IT architecture can provide the leadership in both remediating existing technical debt and preventing future debt.
Failing to take a complete view of the technical debt within the organisation means problems and risks remained unrecognised and unaddressed. The real scope of the problem is substantially underestimated. Technical debt is always much more than poorly written software.
Technical debt can introduce security risks and vulnerabilities into the organisation’s solution landscape. Failure to address technical debt leaves exploitable security risks and vulnerabilities in place.
Shadow IT or ghost IT is a largely unrecognised source of technical debt including security risks and vulnerabilities. Shadow IT is the consequence of a set of reactions by business functions to an actual or perceived inability or unwillingness of the IT function to respond to business needs for IT solutions. Shadow IT is frequently needed to make up for gaps in core business solutions, supplementing incomplete solutions and providing omitted functionality.
Solution Architecture And Solution SecurityAlan McSweeney
This describes an approach to embedding security within the technology solution landscape. It describes a security model that encompasses the range of individual solution components up to the entire solution landscape. The solution security model allows the security status of a solution and its constituent delivery and operational components to be tracked wherever those components are located. This provides an integrated approach to solution security across all solution components and across the entire organisation topology of solutions. It allows the solution architect to validate the security of an individual solution. It enables the security status of the entire solution landscape to be assessed and recorded. Solution security is a wicked problem because there is no certainly about when the problem has been resolved and a state of security has been achieved. The security state of a solution can just be expressed along a subjective spectrum of better or worse rather than a binary true or false. Solution security can have negative consequences: prevents types of access, limits availability in different ways, restricts functionality provided, makes solution harder to use, lengthens solution delivery times, increases costs along the entire solution lifecycle, leads to loss of usability, utility and rate of use.
Data Privatisation, Data Anonymisation, Data Pseudonymisation and Differentia...Alan McSweeney
This paper describes how technologies such as data pseudonymisation and differential privacy technology enables access to sensitive data and unlocks data opportunities and value while ensuring compliance with data privacy legislation and regulations.
Data Privatisation, Data Anonymisation, Data Pseudonymisation and Differentia...Alan McSweeney
Your data has value to your organisation and to relevant data sharing partners. It has been expensively obtained. It represents a valuable asset on which a return must be generated. To achieve the value inherent in the data you need to be able to make it appropriately available to others, both within and outside the organisation.
Organisations are frequently data rich and information poor, lacking the skills, experience and resources to convert raw data into value.
These notes outline technology approaches to achieving compliance with data privacy regulations and legislation while providing access to data.
There are different routes to making data accessible and shareable within and outside the organisation without compromising compliance with data protection legislation and regulations and removing the risk associated with allowing access to personal data:
• Differential Privacy – source data is summarised and individual personal references are removed. The one-to-one correspondence between original and transformed data has been removed
• Anonymisation – identifying data is destroyed and cannot be recovered so individual cannot be identified. There is still a one-to-one correspondence between original and transformed data
• Pseudonymisation – identifying data is encrypted and recovery data/token is stored securely elsewhere. There is still a one-to-one correspondence between original and transformed data
These technologies and approaches are not mutually exclusive – each is appropriate to differing data sharing and data access use cases
The data privacy regulatory and legislative landscape is complex and getting even more complex so an approach to data access and sharing that embeds compliance as a matter of course is required.
Appropriate technology appropriately implemented and operated is a means of managing and reducing risks of re-identification by making the time, skills, resources and money necessary to achieve this unrealistic.
Technology is part of a risk management approach to data privacy. There is wider operational data sharing and data privacy framework that includes technology aspects, among other key areas. Using these technologies will embed such compliance by design into your data sharing and access facilities. This will allow you to realise value from your data successfully.
Solution architects must be aware of the need for solution security and of the need to have enterprise-level controls that solutions can adopt.
The sets of components that comprise the extended solution landscape, including those components that provide common or shared functionality, are located in different zones, each with different security characteristics.
The functional and operational design of any solution and therefore its security will include many of these components, including those inherited by the solution or common components used by the solution.
The complete solution security view should refer explicitly to the components and their controls.
While each individual solution should be able to inherit the security controls provided by these components, the solution design should include explicit reference to them for completeness and to avoid unvalidated assumptions.
There is a common and generalised set of components, many of which are shared, within the wider solution topology that should be considered when assessing overall solution architecture and solution security.
Individual solutions must be able to inherit security controls, facilities and standards from common enterprise-level controls, standards, toolsets and frameworks.
Individual solutions must not be forced to implement individual infrastructural security facilities and controls. This is wasteful of solution implementation resources, results in multiple non-standard approaches to security and represents a security risk to the organisation.
The extended solution landscape potentially consists of a large number of interacting components and entities located in different zones, each with different security profiles, requirements and concerns. Different security concerns and therefore controls apply to each of these components.
Solution security is not covered by a single control. It involves multiple overlapping sets of controls providing layers of security.
Solution Architecture And (Robotic) Process Automation SolutionsAlan McSweeney
Automation is a technology trend IT architects should be aware of and know how to respond to business requests as well as recommend automation technologies and solutions where appropriate. Automation is a bigger topic than just RPA (Robotic Process Automation).
Automation solutions, like all other technology solutions, should be subject to an architecture and design process. There are many approaches to and options for the automation of business activities. Too often automation solutions are tactical applications layered over existing business systems
The objective of all IT solutions is to automate manual business processes and their activities to a certain extent. The requirement for RPA-type applications arises in part because of automation failures within existing applications or the need to automate the interactions with or integrations between separate, possibly legacy, applications.
One of the roles of IT architecture is to always seek to take the wider architectural view and to ensure that solutions are designed and delivered within a strategic framework to avoid, as much as is practical and realistic, short-term tactical solutions and approaches that lead to an accumulation of design, operations and support debt. Tactical solutions will always play a part in the organisation’s solution landscape.
The objective of these notes is to put automation into its wider and larger IT architecture context while accepting the need for tactical approaches in some instances.
These notes cover the following topics:
• Solution And Process Automation – The Wider Technology And Approach Landscape
• Business Processes, Business Solutions And Automation
• Organisation Process Model
• Strategic And Tactical Automation
• Deciding On The Scope Of Automation
• Digital Strategy, Digital Transformation And Automation
• Specifying The Automation Solution
• Business Process Model and Notation (BPMN)
• Sample Business Process – Order To Cash
• RPA (Robotic Process Automation)
Data Profiling, Data Catalogs and Metadata HarmonisationAlan McSweeney
These notes discuss the related topics of Data Profiling, Data Catalogs and Metadata Harmonisation. It describes a detailed structure for data profiling activities. It identifies various open source and commercial tools and data profiling algorithms. Data profiling is a necessary pre-requisite activity in order to construct a data catalog. A data catalog makes an organisation’s data more discoverable. The data collected during data profiling forms the metadata contained in the data catalog. This assists with ensuring data quality. It is also a necessary activity for Master Data Management initiatives. These notes describe a metadata structure and provide details on metadata standards and sources.
Comparison of COVID-19 Mortality Data and Deaths for Ireland March 2020 – Mar...Alan McSweeney
This document compares published COVID-19 mortality statistics for Ireland with publicly available mortality data extracted from informal public data sources. This mortality data is taken from published death notices on the web site www.rip.ie. This is used a substitute for poor quality and long-delayed officially published mortality statistics.
Death notice information on the web site www.rip.ie is available immediately and contains information at a greater level of detail than published statistics. There is a substantial lag in officially published mortality data and the level of detail is very low. However, the extraction of death notice data and its conversion into a usable and accurate format requires a great deal of processing.
The objective of this analysis is to assess the accuracy of published COVID-19 mortality statistics by comparing trends in mortality over the years 2014 to 2020 with both numbers of deaths recorded from 2020 to 2021 and the COVID-19 statistics. It compares number of deaths for the seven 13-month intervals:
1. Mar 2014 - Mar 2015
2. Mar 2015 - Mar 2016
3. Mar 2016 - Mar 2017
4. Mar 2017 - Mar 2018
5. Mar 2018 - Mar 2019
6. Mar 2019 - Mar 2020
7. Mar 2020 - Mar 2021
It focuses on the seventh interval which is when COVID-19 deaths have occurred. It combines an analysis of mortality trends with details on COVID-19 deaths. This is a fairly simplistic analysis that looks to cross-check COVID-19 death statistics using data from other sources.
The subject of what constitutes a death from COVID-19 is controversial. This analysis is not concerned with addressing this controversy. It is concerned with comparing mortality data from a number of sources to identify potential discrepancies. It may be the case that while the total apparent excess number of deaths over an interval is less than the published number of COVID-19 deaths, the consequence of COVID-19 is to accelerate deaths that might have occurred later in the measurement interval.
Accurate data is needed to make informed decisions. Clearly there are issues with Irish COVID-19 mortality data. Accurate data is also needed to ensure public confidence in decision-making. Where this published data is inaccurate, this can lead of a loss of this confidence that can exploited.
Analysis of Decentralised, Distributed Decision-Making For Optimising Domesti...Alan McSweeney
This analysis looks at the potential impact that large numbers of electric vehicles could have on electricity demand, electricity generation capacity and on the electricity transmission and distribution grid in Ireland. It combines data from a number of sources – electricity usage patterns, vehicle usage patterns, electric vehicle current and possible future market share – to assess the potential impact of electric vehicles.
It then analyses a possible approach to electric vehicle charging where the domestic charging unit has some degree of decentralised intelligence and decision-making capability in deciding when to start vehicle charging to minimise electricity usage impact and optimise electricity generation usage.
The potential problem to be addressed is that if large numbers of electric cars are plugged-in and charging starts immediately when the drivers of those cars arrive home, the impact on demand for electricity will be substantial.
Operational Risk Management Data Validation ArchitectureAlan McSweeney
This describes a structured approach to validating data used to construct and use an operational risk model. It details an integrated approach to operational risk data involving three components:
1. Using the Open Group FAIR (Factor Analysis of Information Risk) risk taxonomy to create a risk data model that reflects the required data needed to assess operational risk
2. Using the DMBOK model to define a risk data capability framework to assess the quality and accuracy of risk data
3. Applying standard fault analysis approaches - Fault Tree Analysis (FTA) and Failure Mode and Effect Analysis (FMEA) - to the risk data capability framework to understand the possible causes of risk data failures within the risk model definition, operation and use
Data Integration, Access, Flow, Exchange, Transfer, Load And Extract Architec...Alan McSweeney
These notes describe a generalised data integration architecture framework and set of capabilities.
With many organisations, data integration tends to have evolved over time with many solution-specific tactical approaches implemented. The consequence of this is that there is frequently a mixed, inconsistent data integration topography. Data integrations are often poorly understood, undocumented and difficult to support, maintain and enhance.
Data interoperability and solution interoperability are closely related – you cannot have effective solution interoperability without data interoperability.
Data integration has multiple meanings and multiple ways of being used such as:
- Integration in terms of handling data transfers, exchanges, requests for information using a variety of information movement technologies
- Integration in terms of migrating data from a source to a target system and/or loading data into a target system
- Integration in terms of aggregating data from multiple sources and creating one source, with possibly date and time dimensions added to the integrated data, for reporting and analytics
- Integration in terms of synchronising two data sources or regularly extracting data from one data sources to update a target
- Integration in terms of service orientation and API management to provide access to raw data or the results of processing
There are two aspects to data integration:
1. Operational Integration – allow data to move from one operational system and its data store to another
2. Analytic Integration – move data from operational systems and their data stores into a common structure for analysis
Ireland 2019 and 2020 Compared - Individual ChartsAlan McSweeney
This analysis compares some data areas - Economy, Crime, Aviation, Energy, Transport, Health, Mortality. Housing and Construction - for Ireland for the years 2019 and 2020, illustrating the changes that have occurred between the two years. It shows some of the impacts of COVID-19 and of actions taken in response to it, such as the various lockdowns and other restrictions.
The first lockdown clearly had major changes on many aspects of Irish society. The third lockdown which began at the end of the period analysed will have as great an impact as the first lockdown.
The consequences of the events and actions that have causes these impacts could be felt for some time into the future.
Analysis of Irish Mortality Using Public Data Sources 2014-2020Alan McSweeney
This describes the use of published death notices on the web site www.rip.ie as a substitute to officially published mortality statistics. This analysis uses data from RIP.ie for the years 2014 to 2020.
Death notice information is available immediately and contains information at a greater level of detail than published statistics. There is a substantial lag in officially published mortality data.
This analysis compares some data areas - Economy, Crime, Aviation, Energy, Transport, Health, Mortality. Housing and Construction - for Ireland for the years 2019 and 2020, illustrating the changes that have occurred between the two years. It shows some of the impacts of COVID-19 and of actions taken in response to it, such as the various lockdowns and other restrictions.
The first lockdown clearly had major changes on many aspects of Irish society. The third lockdown which began at the end of the period analysed will have as great an impact as the first lockdown.
The consequences of the events and actions that have causes these impacts could be felt for some time into the future.
Analysis of Possible Excess COVID-19 Deaths in Ireland From Jan 2020 to Jun 2020Alan McSweeney
This analysis seeks to determine if there are excess deaths that occurred in Ireland in the interval Jan – Jun 2020 that can be attributed to COVID-19. Excess deaths means deaths in excess of the number of expected deaths plus the number of deaths directly attributed to COVID-19. On the other hand a deficiency of deaths would occur when the number of expected deaths plus the number of deaths directly attributed to COVID-19 is less than the actual deaths.
This analysis uses number of deaths taken from the web site RIP.ie to generate an estimate of the number of deaths in Jan – Jun 2020 in the absence of any other official source. The last data extract from the RIP.ie web site was taken on 3 Jul 2020.
The analysis uses historical data from RIP.ie from 2018 and 2019 to assess its accuracy as a data source.
The analysis then uses the following three estimation approaches to assess the excess or deficiency of deaths:
1. The pattern of deaths in 2020 can be compared to previous comparable year or years. The additional COVID-19 deaths can be added to the comparable year and the difference between the expected, actual from RIP.ie and actual COVID-19 deaths can be analysed to generate an estimate of any excess or deficiency.
2. The age-specific mortality rates described on page 16 can be applied to estimates of population numbers to generates an estimate of expected deaths. This can be compared to the actual RIP.ie and actual COVID-19 deaths to generate an estimate of any excess or deficiency.
3. The range of death rates per 1,000 of population as described in Figure 10 on page 16 can be applied to estimates of population numbers to generates an estimate of expected deaths. This can be compared to the actual RIP.ie and actual COVID-19 deaths to generate an estimate of any excess or deficiency.
This presentation describes systematic, repeatable and co-ordinated approach to agile solution architecture and design. It is intended to describe a set of practical steps and activities embedded within a framework to allow an agile method to be adopted and used for solution design and delivery. This approach ensures consistency in the assessment of solution design options and in subsequent solution design and solution delivery activities. This process leads to the rapid design and delivery of realistic and achievable solutions that meet real solution consumer needs. The approach provides for effective solution decision-making. It generates options and results quickly and consistently. Implementing a framework such as this provides for the creation of a knowledgebase of previous solution design and delivery exercises that leads to an accumulated body of knowledge within the organisation.
Elevating Tactical DDD Patterns Through Object CalisthenicsDorra BARTAGUIZ
After immersing yourself in the blue book and its red counterpart, attending DDD-focused conferences, and applying tactical patterns, you're left with a crucial question: How do I ensure my design is effective? Tactical patterns within Domain-Driven Design (DDD) serve as guiding principles for creating clear and manageable domain models. However, achieving success with these patterns requires additional guidance. Interestingly, we've observed that a set of constraints initially designed for training purposes remarkably aligns with effective pattern implementation, offering a more ‘mechanical’ approach. Let's explore together how Object Calisthenics can elevate the design of your tactical DDD patterns, offering concrete help for those venturing into DDD for the first time!
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...UiPathCommunity
💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™:
See how to accelerate model training and optimize model performance with active learning
Learn about the latest enhancements to out-of-the-box document processing – with little to no training required
Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages
This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath.
Speakers:
👨🏫 Andras Palfi, Senior Product Manager, UiPath
👩🏫 Lenka Dulovicova, Product Program Manager, UiPath
State of ICS and IoT Cyber Threat Landscape Report 2024 previewPrayukth K V
The IoT and OT threat landscape report has been prepared by the Threat Research Team at Sectrio using data from Sectrio, cyber threat intelligence farming facilities spread across over 85 cities around the world. In addition, Sectrio also runs AI-based advanced threat and payload engagement facilities that serve as sinks to attract and engage sophisticated threat actors, and newer malware including new variants and latent threats that are at an earlier stage of development.
The latest edition of the OT/ICS and IoT security Threat Landscape Report 2024 also covers:
State of global ICS asset and network exposure
Sectoral targets and attacks as well as the cost of ransom
Global APT activity, AI usage, actor and tactic profiles, and implications
Rise in volumes of AI-powered cyberattacks
Major cyber events in 2024
Malware and malicious payload trends
Cyberattack types and targets
Vulnerability exploit attempts on CVEs
Attacks on counties – USA
Expansion of bot farms – how, where, and why
In-depth analysis of the cyber threat landscape across North America, South America, Europe, APAC, and the Middle East
Why are attacks on smart factories rising?
Cyber risk predictions
Axis of attacks – Europe
Systemic attacks in the Middle East
Download the full report from here:
https://sectrio.com/resources/ot-threat-landscape-reports/sectrio-releases-ot-ics-and-iot-security-threat-landscape-report-2024/
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
Keynote at DIGIT West Expo, Glasgow on 29 May 2024.
Cheryl Hung, ochery.com
Sr Director, Infrastructure Ecosystem, Arm.
The key trends across hardware, cloud and open-source; exploring how these areas are likely to mature and develop over the short and long-term, and then considering how organisations can position themselves to adapt and thrive.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
JMeter webinar - integration with InfluxDB and GrafanaRTTS
Watch this recorded webinar about real-time monitoring of application performance. See how to integrate Apache JMeter, the open-source leader in performance testing, with InfluxDB, the open-source time-series database, and Grafana, the open-source analytics and visualization application.
In this webinar, we will review the benefits of leveraging InfluxDB and Grafana when executing load tests and demonstrate how these tools are used to visualize performance metrics.
Length: 30 minutes
Session Overview
-------------------------------------------
During this webinar, we will cover the following topics while demonstrating the integrations of JMeter, InfluxDB and Grafana:
- What out-of-the-box solutions are available for real-time monitoring JMeter tests?
- What are the benefits of integrating InfluxDB and Grafana into the load testing stack?
- Which features are provided by Grafana?
- Demonstration of InfluxDB and Grafana using a practice web application
To view the webinar recording, go to:
https://www.rttsweb.com/jmeter-integration-webinar
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
Generating a custom Ruby SDK for your web service or Rails API using Smithyg2nightmarescribd
Have you ever wanted a Ruby client API to communicate with your web service? Smithy is a protocol-agnostic language for defining services and SDKs. Smithy Ruby is an implementation of Smithy that generates a Ruby SDK using a Smithy model. In this talk, we will explore Smithy and Smithy Ruby to learn how to generate custom feature-rich SDKs that can communicate with any web service, such as a Rails JSON API.
Empowering NextGen Mobility via Large Action Model Infrastructure (LAMI): pav...
Enterprise Business Analysis Capability - Strategic Asset for Business Alignment and Driving Innovation
1. Enterprise Business Analysis
Capability - Strategic Asset
for Business Alignment and
Driving Innovation
Alan McSweeney
http://ie.linkedin.com/in/alanmcsweeney
2. Enterprise Business Analysis
• Introducing the concept of Enterprise Business Analysis as
a strategic resource to achieve business and IT alignment
May 11, 2015 2
4. Business Solution Delivery In Context
• Solution delivery needs to be a continuum from business
strategy to operational and managed solution
• Solution delivery needs to work in the context of business
changes and the need for the business to respond to
changes
May 11, 2015 4
6. Business IT Requirements And IT Alignment
May 11, 2015 6
Business Needs
Market Changes
Regulatory Changes
Customer Requirements
Organisational Changes
IT Function Underlying
Solution Delivery And
Operation Enablement
Structure
Business Solution Design
And Delivery
Alignment
New Products/ Services
Competitive Pressures
8. Dimensions Of Changes
May 11, 2015 8
Business
Needs
Market
Changes
Competitive
Pressures
Organisational
Changes
New
Products/
Services
Regulatory
Changes
Customer
Requirements
Business
Needs
Market
Changes
Competitive
Pressures
Organisational
Changes
New
Products/
Services
Regulatory
Changes
Customer
Requirements
Business
Needs
Market
Changes
Competitive
Pressures
Organisational
Changes
New
Products/
ServicesRegulatory
Changes
Customer
Requirements
Pace And Impact of
Business Changes
Increasing
9. Business IT Requirements And IT Alignment …
• … Means …
• Having an IT function with an underlying delivery-oriented structure,
attitude, approach, intention
• Being able to analyse and define business requirements associated with
business changes
• Being able to analyse and define business processes associated with
business changes
• Being able to define and design business solutions that deliver
requirements and processes
• Rebuild the fragmented and disjointed conversation between business and
IT
− Business and IT Alignment requires more than just relationship
management – it requires actual engagement by IT with the
needs of the business
May 11, 2015 9
10. Business Analysis And Business Operating
Environment
May 11, 2015 10
Business
Strategy
Business
Objectives
Changes In
Products/
Services
Changes in
Organisation
Process Changes
Merger/
Acquisition/
Divestment
Regulatory
Changes
Market
Changes
Competitive
Pressure
Changes In IT
Solutions To
Enable Business
Change
New
Products/
Services
Customer
Requirements
12. Levels Of Business Analysis And Business Analyst
May 11, 2015 12
Functional Business Analyst
Understand business objectives
and solution functional
requirements
Analyse, define and optimise
business processes
Understand products and
services provided and associated
processes and solution
Assist with the optimisation of
the solution portfolio
Participate in optimisation of
organisation structure of
business function
Enterprise Business Analyst
Assist with translation of
business strategy to business
objectives
Ensure IT solution delivery is
aligned with business strategy
and business objectives
Assist with optimising IT solution
delivery activities
Contribute to solution delivery
governance
Support optimisation of
organisation structure
IT Business Analyst
Gather and analyse business
requirements
Map and document the business
processes
Assist with the creation of
solution functional specifications
14. Effective Business Analysis Prevents Discontinuity
And Fragmentation
May 11, 2015 14
Local Fragmentation and
Discontinuity
Organisation Wide Fragmentation and Discontinuity
15. Levels Of Business Analysis And Business Analyst
May 11, 2015 15
Functional Business Analyst
Enterprise Business Analyst
IT Business Analyst
Greater
Business
Analysis
Capability
Delivers
Greater
Effectiveness
16. Preventing The Bumpy And Uncomfortable Journey From
Business Strategy To Execution And IT Solution Delivery
May 11, 2015 16
Business
Strategy
Business
Objectives
Changes In
Products/
Services
Changes in
Organisation
Process Changes
Changes In IT
Solutions To
Enable Business
Change
17. What IT All Too Frequently Delivers
May 11, 2015 17
Lack of response to business
needs
Slow and costly solution delivery
High solution maintenance and
operation costs
Fragile solutions with many
manual workarounds
Excessive and duplicated
development effort and
operation
Duplicated and costly
investments in many solutions
Siloed applications with lack of
integration
Poor return on investment
Too little, too late, not
what was wanted or
needed
Business Needs
Market Changes
New Products/ Services
Regulatory Changes
Customer Requirements
Organisational Changes
Competitive Pressures
The IT Funnel of
Fragmentation
and
Discontinuity
18. Integrated Approach To Business Analysis Optimises
Delivery, Removes Friction And Creates Effective Linkages
May 11, 2015 18
From …
To …
19. IT Does Provide Competitive Advantage
• IT does really provide competitive advantages to
organisations
• Business really does need IT to operate and grow
• Business can and does bypass the IT function if it does not
listen to the business and deliver solutions that enable
delivery of business objectives
• The business will look elsewhere for the necessary IT
solutions
• The consequence will be a fragmented and balkanised IT
solution landscape that is costly to operate and support
May 11, 2015 19
22. Enterprise Business Analysis
• A highly capable business analysis function is a key enabler
of business change
• Identifier of solutions to business problems
• Driver of solution innovation and renovation
• Assist the business to address its challenges
• Business and IT alignment is a continuous process
• Assists in bridging the gap between the business and IT
• Mediates between the business and IT
• Ensures that IT is relevant to the business
May 11, 2015 22
23. Business
Strategy
Business
Objectives
Changes In
Products/
Services
Changes in
Organisation
Process Changes
Changes In IT
Solutions To
Enable Business
Change
Business Analysis Across Business Operating
Environment
May 11, 2015 23
Enterprise Business
Analysis
Functional
Business Analysis IT Business Analysis
Siloed Business
Analysis
Collaboration And
Sharing Across
Organisation
Functions
Organisation-Wide
Analysis Capability
With Consistent,
Repeatable
Processes
24. Business xNovation
May 11, 2015 24
Business
Strategy
Business
Objectives
Changes In
Products/
Services
Changes in
Organisation
Process Changes
Changes In IT
Solutions To
Enable Business
Change
Innovation
Renovation
25. Business xNovation
• Businesses need to:
− Innovate – introduce new into the organisation
− Renovate – update and modernise existing services, products and
offerings and support systems and processes
• Enterprise Business Analysis can play a central role in
successfully driving xnovation through the business
through to IT
May 11, 2015 25
27. Business And IT Alignment Runs Both Ways
• An effective Enterprise Business Analysis capability within
the IT function means that IT call sell itself to the business
May 11, 2015 27
28. Business And IT Alignment Runs Both Ways
• IT needs:
− Enterprise Architecture that supports and enables solution
delivery and operation
− Enterprise Business Analysis function that provides a
comprehensive view of business processes, solution portfolio,
business requirements
− Enterprise Business Analysis function that speaks the language of
both business and IT and can act as a translator between both
parties
May 11, 2015 28
29. Enterprise Business Analysis Capability
• Without Enterprise Business Analysis Capability
− Siloed operation
− Inconsistent and fragmented operation
− Inconsistent and limited results
− No focus on overall business strategy
− Limited collaboration and sharing of knowledge and experiences
• With Enterprise Business Analysis Capability
− Consistent solution analysis process and approach with predictable
results
− Collaboration across organisation
− Business knows it is being listened to and that commitments will be met
− Effective knowledge management
− Analysis governance and standards
− Enable business respond to changes quickly and effectively
May 11, 2015 29
30. It Is Not About The Project – It Is About The Solution
• The IT project exists to deliver a solution that meets the
requirements of the business and that is usable, operable,
supportable, maintainable and cost-effective
• The focus needs to change from project management to
solution delivery
• The individual business solution exists within the context of a
portfolio of business solutions
• The solution requirements – functional – what it must do – and
non-functional – usability, performance, supportability,
maintenance, reliability, availability – must be delivered on
• Effective solution delivery requires effective business and IT
alignment
May 11, 2015 30
31. It Is Not About The Project – It Is About The Solution
• Capable and effective enterprise-wide business analysis
means the focus will remain on the solution rather than
the project
• A solution can only be regarded as successful if, over its
lifetime, it delivers the defined business results to all its
participants subject to schedule and budgetary constraints
May 11, 2015 31
32. Solution Is Not Just Functionality
• Solution success needs to be assessed against functional and
service/operational factors:
− Usability
− Operability
− Supportability
− Maintainability
− Security
− Integration
− Performance
− Reliability
− Integratability
• Enterprise Business Analysis capability ensures that complete
view of solution exists from the start
• High probability of success is embedded into solution design
from the start
May 11, 2015 32
33. Solution May Not Just A Single Application
May 11, 2015 33
External
Manual
Interaction
External
Manual
Interaction
External
Manual
Interaction
External
Manual
Interaction
Extended Application(s)
System
Component
System
Component
System
Component
External
Component
External
Component
External
Component
Core
Application
End To End View Of Solution
34. Solution May Not Just A Single Application
May 11, 2015 34
External
Manual
Interaction
External
Manual
Interaction
External
Manual
Interaction
External
Manual
Interaction
Extended Application(s)
System
Component
System
Component
System
Component
External
Component
External
Component
External
Component
Core
Application
Limited View All
Too Often Taken
35. Solution May Not Just A Single Application
May 11, 2015 35
System
Component
System
Component
System
Component
External
Component
External
Component
External
Component
Automated
Process
Automated
Process
External
Manual
Interaction
External
Manual
Interaction
Manual
Process
Manual
Process
External
Manual
Interaction
External
Manual
Interaction
Manual
Process
Manual
Process
Extended Application(s)
Core
Application
36. May 11, 2015 36
Hierarchy Of Requirements – From Enterprise To
Solution
Business Vision and
Goals
Business Strategy
Business Objectives
and Plan
Programmes for
Strategic Objectives
Solutions
Operation of
Solutions
Solutions delivered by
programmes and projects
cascade from business vision
to ultimate operation and
service delivery
Solutions delivered by
programmes and projects
need to be aligned to the
overarching business vision
and goal
37. Solution Delivery Boundaries
May 11, 2015 37
Enterprise Architecture Defines the
Solution Technical Boundary
Business
Data
Technical
Functional
Implementation
Management
and Operation
Solution
Enterprise
Business
Analysis
Defines the
Solution
38. Solution May Not Just A Single Application
• Overall solution may consist of core application and integration
points with existing applications
• Overall solution may operate with a mix of automated and
manual processes in a structured or ad-hoc manner to deliver
the required results
• Understanding the overall set of integration points and
processes and their operation is crucial to successful results
• Need to see the entire picture to understand how a solution
should operate
− Core system/application are just one part of this solution universe
• Unambiguous definition of processes is required
• Processes that are to be automated define the scope of the
development and implementation work
May 11, 2015 38
39. Extended Dimensions Of Overall Solution
May 11, 2015 39
Solution
Core
Application
Functionality
Solution
Operational
Characteristics
40. Enterprise Business Analysis
• All too often complete end-to-end view of the solution is
not recognised or appreciated
• Enterprise Business Analysis enables the full scope of the
solution and its operational framework to be understood,
defined and scoped at an early stage
• A realistic end-to-end view maximises the likelihood of
solution success
− All the functional and operational requirements are identified and
quantified
May 11, 2015 40
41. Achieving Alignment
• No doubt that business and IT alignment is necessary and
worthwhile
• But
− What exactly does alignment mean?
− What are the goals of alignment?
− How can its success be assessed?
− What is needed to achieve it?
May 11, 2015 41
42. Achieving Alignment
• Alignment requires enterprise-level commitment and
decisions made at an enterprise-level
• Need enterprise business analysis context within which to
operate
• Need enterprise business analysis framework where
business model, objectives and processes are held
May 11, 2015 42
43. Enterprise Business Analysis Capability – Key
Elements
May 11, 2015 43
Approach
Consistent and
repeatable
approach to
business analysis
Quick and
predictable
results
Top-down
approach
Framework
End-to-end
business
definitions
Cross-functional
process view
Business process
inventory
Teamwork
Collaboration
across and
between teams
Management
commitment
Mentoring and
training
Forum
Quality assurance
and control
Information
Management
Tools and
Techniques
Governance and Management
Information
sharing and
collaboration
tools
Information
management
processes
Complete set of
templates,
artefacts, tools
Consistent
implementation
and use
Management commitment, funding and support
Measurement and reporting
Demand and resource management
44. Achieving Enterprise Business Analysis Capability
• Senior Commitment and Sponsorship
− Without this, the initiative will fail
− There must be a strong belief that the approach will work
− View that Enterprise Business Analysis represents a strategic asset
− Needed to overcome obstacles and setbacks
• Defined Vision
− Articulated goal of what is to be achieved
• Achievable Implementation Plan
− Financial and resource plan to achieve goals that is realistic and
achievable
• Business Acceptance
− Target users of the service must accept the approach
• Skills and Experience
− Appropriately skilled and experienced team
May 11, 2015 44
45. Summary
• Business and IT alignment needs real engagement and not
just relationship management
• Enterprise Business Analysis capability provides a strategic
approach to achieving business and IT alignment
• Projects ≠ Solutions
• Solutions ≠ Functionality
• Enterprise Business Analysis ensures a complete end-to-
end view of solution delivery maximising success and
return on investment
May 11, 2015 45
46. May 11, 2015 46
More Information
Alan McSweeney
http://ie.linkedin.com/in/alanmcsweeney