I'll split it into three groups Ones who drink vendor or tech show kool-aid (where E includes Framework X) E, B, C (no A or D)
Ones who are driving from IT with minimal business engagement B, E, C Ones who are driving from a business perspective with IT aligned A, B, C, E, D(?) I'm not seeing much of the D in any case and being blunt calling the product led piece "governance" is pushing it, its more product fanaticism than IT governance. Steve 2008/7/25 jeffrschneider <[EMAIL PROTECTED]>: > In what order do you think enterprises are currently prioritizing > these areas, example: (B, E, A, C, D)? > > A. Plan Time Governance - Ensuring that business initiatives aligned > with key I.T. services, avoiding silos while gaining cross > organizational funding, etc. > > B. Design Time Governance - Utilizing registries, repositories, > validation frameworks, etc. to promote best practices in schema and > contract design enabling reuse, search, verify, etc. > > C. Pre-Release Governance - Validating solutions meet pre-production > needs (highly available, secure, fast response times, new version > doesn't break existing consumers, etc.) > > D. Run Time Governance - Ensuring that the services in production are > monitored, adhere to SLA's, leverage run time policies, etc. > > E. Infrastructure Governance - Verify that the infrastructure used > (ESB's, Registries, Mediation Devices, etc.) adhere to the corporate > standards. > >
