Implementation Governance Model

Project XXXX
Client YYYY
<<Note: This document provides a generic template. It may require tailoring to suit a specific client and
project situation.>>
Table of Contents
1 Purpose of this ocument...........................................................................................................................................!
" #overnance Processes.................................................................................................................................................$
! #overnance %rgani&ation 'tructure............................................................................................................................(
$ #overnance )oles and )esponsi*ilities......................................................................................................................+
( #overnance ,hec-points and 'uccess./ailure ,riteria..............................................................................................0
Document Information
Project Name: Project 111
Prepared By: Document Version No: 2.1
Title: Implementation #overnance 3odel Document Version Date:
Reviewed By: Review Date:
Distribution List
From Date Phone/Fax/mail
To !ction" Due Date Phone/Fax/mail
4 5ction Types: 5pprove6 )evie76 Inform6 /ile6 5ction )equired6 5ttend 3eeting6 %ther 8please specify9
Document Version Histor
Version
Num#er
Version
Date Revised By Description Filename
T%#5/: ; Template: Implementation #overnance 3odel "
,opyright < "212 The %pen #roup. 5ll rights reserved. T%#5/: is a trademar- of The %pen #roup.
! Purpose of t"is Document
<<%nce an architecture has *een defined6 it is necessary to plan ho7 the Transition 5rchitecture that
implements the architecture 7ill *e governed through implementation. =ithin organi&ations that have
esta*lished architecture functions6 there is li-ely to *e a governance frame7or- already in place6 *ut
specific processes6 organi&ations6 roles6 responsi*ilities6 and measures may need to *e defined on a
project>*y>project *asis.
The Implementation #overnance 3odel ensures that a project transitioning into implementation also
smoothly transitions into appropriate architecture governance.>>
T%#5/: ; Template: Implementation #overnance 3odel !
,opyright < "212 The %pen #roup. 5ll rights reserved. T%#5/: is a trademar- of The %pen #roup.
# Governance Processes
<<The purpose of this section is to outline fundamental functionality and attri*utes: semantic6
unam*iguous6 including security capa*ility and managea*ility.>>
#$! %vervie&
#$# Governance Processes
<<%utline -ey governance processes.>>
T%#5/: ; Template: Implementation #overnance 3odel $
,opyright < "212 The %pen #roup. 5ll rights reserved. T%#5/: is a trademar- of The %pen #roup.
' Governance %r(ani)ation *tructure
<<Interfaces: chosen set6 supplied.>>
'$! Governance *tructure
<<%utline the governance structure? e.g.6 simple organi&ation chart sho7ing roles and reporting lines.>>
T%#5/: ; Template: Implementation #overnance 3odel (
,opyright < "212 The %pen #roup. 5ll rights reserved. T%#5/: is a trademar- of The %pen #roup.
+ Governance ,oles and ,esponsibilities
<<3ap to *usiness.organi&ational entities and policies.>>
+$! *ta-e"olders. Concerns. and Vie&s
The follo7ing ta*le sho7s the sta-eholders6 their concerns6 and vie7s.
$ta%eholder &oncern View
<<'ta-eholder1>> <<escri*e 7hat aspects of the
architecture 7ill *e of interest to this
sta-eholder.>>
<<@ist any vie7s to *e created to address
this sta-eholderAs concerns.>>
+$# ,oles and ,esponsibilities /,0CI1
<<=here relevant6 add a )5,I chart B sho7ing -ey sta-eholders and activities6 and 7ho is
8)9esponsi*le6 859ccounta*le6 8,9onsulted6 8I9nformed in each case.>>
T%#5/: ; Template: Implementation #overnance 3odel +
,opyright < "212 The %pen #roup. 5ll rights reserved. T%#5/: is a trademar- of The %pen #roup.
2 Governance C"ec-points and *uccess34ailure Criteria
2$! Governance C"ec-points
2$# Metrics and 5PIs
In addition6 the follo7ing metrics 7ill *e used to determine the success of this architecture 7or-:
'etric 'easurement Techni(ue Tar)et Value Rationale/Further Notes
<<)efer *ac- to the )equest for 5rchitecture =or- and restate.refine.>>
2$' *uccess34ailure Criteria
2$+ 0cceptance Procedure
<<escri*e the process to *e used for acceptance.sign>off.>>
T%#5/: ; Template: Implementation #overnance 3odel 0
,opyright < "212 The %pen #roup. 5ll rights reserved. T%#5/: is a trademar- of The %pen #roup.