Governance & Enterprise Architecture. Governance & SOA In 2006, lack of working governance...
-
Upload
juan-padilla -
Category
Documents
-
view
218 -
download
4
Transcript of Governance & Enterprise Architecture. Governance & SOA In 2006, lack of working governance...
Governance & SOA
“In 2006, lack of working governance mechanisms in mid size to large post-pilot SOA projects will be the most common reason for project failure ”
(0.8 probability – Gartner)
IT Governance – A Definition
IT governance: Specifying the decision rights and accountability framework to encourage desirable behaviour in the use of IT.
(Weill and Ross, 2004, IT Governance, HBSP)
Key IT Governance DecisionsIT Principles Decisions
High-level statements about how IT is used in the business
IT ArchitectureDecisions
Organising logic for data,applications, and infrastruc-ture captured in a set ofpolicies, relationships, andtechnical choices to achievedesired business and technical standardisationAnd integration
IT InfrastructureDecisions
Centrally co-ordinated, sharedIT services that provide thefoundation for the enterprise’sIT capability.
Business ApplicationsNeedsSpecifying the business needfor purchasing or internallydeveloped IT applications.
IT Investment andPrioritisation decisions
Decisions about how muchand where to invest in IT,including project approvalsand justification techniques.
(Weill and Ross, 2004, IT Governance, HBSP)
IT Governance ArchetypesSTYLE Who Has Decision or Input Rights?
Business A group of business executives or individual executives (CxOs). IncludesMonarchy committees of senior business executives (may include (CIO), excludes
IT executives acting independently.
IT Monarchy Individuals or groups of IT executives.
Feudal Business unit leaders, key process owners or their delegates.
Federal C-level executives and business groups (eg business units or processes);may also include IT executives as additional participants. Equivalent of thecentral and state governments working together.
IT Duopoly IT executives and one other group (e.g. CxO or business unit or process leaders).
Anarchy Each individual user. (Weill and Ross, 2004, IT Governance, HBSP)
LJMU Federal Governance Model
(Continuing)Information
Management Steering Group
Business Membership
Development Programme
Business Membership
IT Steering Group
Business Membership
ArchitecturePrinciples
InfrastructureBusiness Applications Needs
ITMembership
Investment & prioritisation
Methodologies: MSP ITIL
MonitoringComplianceReview
LJMU Governance Membership
• 7 members of the LJMU Senior Management team, out of a total of 16
• School Directors• Service Directors – Library, Estates, HR• Admin/project/resource managers• All ICT Senior Managers
What Can Governance Do For You?
• Get buy-in across the board • Do it with them, even if they don’t do it to
themselves• Change behaviour, not just technology
EA & Governance
• Executive buy-in to EA approach– Within LJMU Governance structure, Architecture
already identified as responsibility of Information Management Steering Group
• Demonstrate value of EA approach– ‘burning platform’ required, provided by existing
Student Experience Review initiative
• Visibility– Exposes Senior Management to EA approaches
Selling EA & Governance
• Speak the language of the business– Or something as close as you can get
• It’s all about value– The business has to see that this will promote better
IS decision-making to support the business better
• Show them pictures– Not like I’ve been doing in this presentation…– EA development will provide the pictures– See JISC SOA animation
http://www.jisc.ac.uk/whatwedo/programmes/programme_eframework/soa.aspx
Selling EA & Governance
• Business value:– Business wants to know how to analyse staffing
requirements in light of increasing self-service– ‘As Is’ Architecture – self-service capability mapped
to business processes as of now– ‘To Be’ Architecture – self-service capability mapped
to business processes in light of move to Campus Solutions
• Giving a visual representation that addresses the business problem