Yes, governance is another overloaded term that many organizations/
people will have pre-conceived notions as soon they hear the term.
Finding the right angle to take on the problem to get your foot in the
door can be the most difficult thing.
My take on it is that there has to be a reason for adopting SOA,
something that's not being done today or being done poorly. To get
there, something normally needs to change. Simply making a statement
of "fix this" probably won't cut it, or at best, will provide a one-
time fix, but then the organization reverts back to past behavior. We
need something to actually guide us through that change and ensure
that it is a transition to the desired state, rather than a band-aid.
I've chosen to focus on governance to guide that change. If someone
doesn't like term, I would fall back to the discussion of the current
failings and get agreement that something needs to change and get
agreement on the action plan for making that change, regardless of
what we choose to call it.
-tb
Todd Biske
http://www.biske.com/blog/
Sent from my iPhone
On Oct 26, 2008, at 11:55 PM, Steve Jones <[EMAIL PROTECTED]>
wrote:
A million management consultants scream out.
I'm 100% with the aim here, but one challenge around calling business
change "governance" is that in my experience this tends to be a
finance/IT type term that doesn't always produce positive behaviours
(i.e. the Sales and Marketing folks tend to hate it and the Production
guys really understand it, but in a completely different way to what
you want).
I've tended to split this governance from the policy governance and
just called the former the "business change stream" its right to say
its a form of governance but I'm not sure telling everyone that helps.
Steve
2008/10/24 Gervas Douglas <[EMAIL PROTECTED]>:
> Here is an extract from an article in InfoQ:
>
> <<Many people have written that the hardest thing about a successful
> adoption of SOA is not the technology, but rather, the culture
change.
> Whether it's trying to encourage a culture of sharing that goes
> against the grain of developers that prefer complete control over
> their solutions, trying to change the way projects are proposed and
> funding to ensure strategic service creation, or trying to properly
> manage the new dependencies that are created at run-time, these
> changes require more than just technology. What is the key to
ensuring
> that the culture change does happen? It is in managing the process
of
> behavioral change, which is governance.>>
>
> You can read the whole article at:
>
> http://www.infoq.com/articles/implementing-soa-governance
>
> Gervas
>
>
