- Gregor Hohpe (Moderator and now at Google)
- Chris Harding (who did the keynote)
- David Bressler (Progress)
- Tony Carrato (IBM)
- There must be an impact to violating governance, too often people ignore governance knowing that they will get away with it
- Governance is not one-size fits all, find appropriate governance models in different areas
- Governance is about people and process much more than it is about technology
- The Business needs to be accountable for SOA governance and the business Services
- IT needs to be responsible for the delivery of SOA and the technical parts of the services
- Too many companies are buying registries as if that is all they need to do for SOA governance (a top point by Dave)
- Governance needs to not create big document jockey processes, it needs to be effective
- Bad governance kills innovation (a good point from the floor)
- Governance isn't a new IT problem with SOA, projects have failed for years due to bad governance. The point is that SOA provides a better structure for governance than previous project based approaches.
- SOA governance isn't an IT thing, it impacts the business accountability, the funding model and the full lifecycle.
Myself and Tony disagreed about the most effective way to enforce governance, I preferred using a stick with nails in it while Tony felt shooting someone and leaving the body around was more effective. Personally I prefer the stick with nails as its personal, but I see where Tony is coming from :)
The basic piece though was that if you don't switch you governance model to actually be based around the services and the business then you are being wildly optimistic if you think that applying a new technology (like a registry) will solve your problem.
One of the more enjoyable panels I've been on. They were video'ing it but I don't know what happens with the videos, if I find out I'll link it.
Tomorrow its SOA Runtime headed up by Dave Chappell.