1. Logosworld.com Roadmap to SOA Governance of agile service oriented projects Governance of agile service oriented projects ©2005 Angeli/Grice logosworld.com

2. Logosworld.com If all politicians mulled over god and the earth before they acted and not after they did, we would have a better state! Platon, On the State Platon, On the State ©2005 Angeli/Grice logosworld.com

3. Logosworld.com Orchestration Replaces Orders  SOA is designed to be built on convergence instead of linearity  Linear models will imperatively fail  SOA requires an implementation independent from sequence  Wikis are best prove of concept!  SOA is designed to be built on convergence instead of linearity  Linear models will imperatively fail  SOA requires an implementation independent from sequence  Wikis are best prove of concept!

4. Logosworld.com Societies work and depend on self- organizing strategies, only! ©2005 Angeli/Grice logosworld.com

5. Logosworld.com Project Management Concepts  Waterfall  Convergence  Chaos (= holistic or self-organizing)  Chaos models are variations of convergence models  Waterfall  Convergence  Chaos (= holistic or self-organizing)  Chaos models are variations of convergence models

6. Logosworld.com Understanding IT as a Service Governance is oriented on organisation of societies Governance is oriented on organisation of societies ©2005 Angeli/Grice logosworld.com

7. Logosworld.com SOA Management  Team Organisations  Teams are tailored to subject matters (“segregation of concerns”) Business needs not organization shall drive team setup  Every team is led by an IT and a business expert Assures a balance between business and technical  The leaders of a team can be from several teams It is actually encouraged that the responsibles roam teams  Every team has at least one member who is a subject expert in another team This assures that knowledge is transportable and communicated  Team Organisations  Teams are tailored to subject matters (“segregation of concerns”) Business needs not organization shall drive team setup  Every team is led by an IT and a business expert Assures a balance between business and technical  The leaders of a team can be from several teams It is actually encouraged that the responsibles roam teams  Every team has at least one member who is a subject expert in another team This assures that knowledge is transportable and communicated

8. Logosworld.com SOA Management  Project Timing and Conduct  SOA projects are non-linear  Self-Containment Ideally no single object‘s implementation or change should block other activities  Interface Stability Every system build interfaces first Dummy responses can replace fully functionality  Self-Test and Sample-Use Every service needs to prove its full functionality in a self-test Every set-up needs to be demonstrated by a sample service  Project Timing and Conduct  SOA projects are non-linear  Self-Containment Ideally no single object‘s implementation or change should block other activities  Interface Stability Every system build interfaces first Dummy responses can replace fully functionality  Self-Test and Sample-Use Every service needs to prove its full functionality in a self-test Every set-up needs to be demonstrated by a sample service

9. Logosworld.com SOA Management  Team Management  Team leaders recruit their members Imagine it like „street-football“, captains are elected and then pick „their“ players  Every team has fully responsibility for subject  Every team knows the core tasks of other teams  Teams can ask other teams for „services“  Management is the „Captain“ of the project  Captain decides about course  Captain is umpire between teams  Team Management  Team leaders recruit their members Imagine it like „street-football“, captains are elected and then pick „their“ players  Every team has fully responsibility for subject  Every team knows the core tasks of other teams  Teams can ask other teams for „services“  Management is the „Captain“ of the project  Captain decides about course  Captain is umpire between teams

10. Logosworld.com Global Project Service Providers  Project head understood as the „Captain“ of all teams  Project coach as main mediator and arbitre  Secretary for logistics  Central service for hotel, travel, expenses, shopping...  Professional language translator  Developer or consultants MUST not do translations  Project head understood as the „Captain“ of all teams  Project coach as main mediator and arbitre  Secretary for logistics  Central service for hotel, travel, expenses, shopping...  Professional language translator  Developer or consultants MUST not do translations

11. Logosworld.com Management inspects for disorders The Captain controls the course and mediates contention and intervenes only when the team does not work in harmony The Captain controls the course and mediates contention and intervenes only when the team does not work in harmony ©2005 Angeli/Grice logosworld.com

12. Logosworld.com Reporting Teams reports disorders Teams reports disorders ©2005 Angeli/Grice logosworld.com

13. Logosworld.com Example of project disorders  Delays in delivery of service interfaces  Quality deficiencies  Illicit side-effects of implementations  Violation of self-containment commandment  Overuse of ressources  Overloading from work  Delays in delivery of service interfaces  Quality deficiencies  Illicit side-effects of implementations  Violation of self-containment commandment  Overuse of ressources  Overloading from work

14. Logosworld.com Project Timing  Plan is built around sync-points (mile- stones) only  Only deviations from target are reported to captain  Teams agree sync-points themselves  An arbitration commitee resolves contention  Plan is built around sync-points (mile- stones) only  Only deviations from target are reported to captain  Teams agree sync-points themselves  An arbitration commitee resolves contention

15. Logosworld.com SOA Governance is based on convergence Many activities run in parallel Many activities run in parallel ©2005 Angeli/Grice logosworld.com

16. Logosworld.com Governance responsibilities

17. Logosworld.com Organisation interaction in a SOA meta model

18. Logosworld.com Sample governance organizational structure

19. Logosworld.com Real Life Analogy of Social Development  Pre-urban village  Every farmer needed to be allrounder smith, miller, baker etc.  Every settlement needed to cater for water, energy and fortification  Superior inventions in one village might not be spread out and be forgotten eventually  Costs for automation and infrastructure very high  Pre-urban village  Every farmer needed to be allrounder smith, miller, baker etc.  Every settlement needed to cater for water, energy and fortification  Superior inventions in one village might not be spread out and be forgotten eventually  Costs for automation and infrastructure very high  City  Sophisticated tasks are delegated to specialists Miller, Baker, Smith etc.  Common and efficient infrastructure  Speedy evolution intensive reuse  Cost efficiency Redundancy is avoidable

20. Logosworld.com Why Wikis Work and Projects Don‘t

21. Logosworld.com Loosing Money in Development  Classical Isolated Tasks  One developer programs end to end + one responsible - needs detail knowledge in all areas - all developers need detail knowhow - likelyhood of redundent work - very few reuse of components - risk of developer autism  Team organisation  Several developer (even on small tasks) - Project know how distributed + experts do expert works + high degree of reuse + communication and collaboration mandatory  Classical Isolated Tasks  One developer programs end to end + one responsible - needs detail knowledge in all areas - all developers need detail knowhow - likelyhood of redundent work - very few reuse of components - risk of developer autism  Team organisation  Several developer (even on small tasks) - Project know how distributed + experts do expert works + high degree of reuse + communication and collaboration mandatory

22. Logosworld.com Societies produced different management strategies Imperative, devote, chaotic Imperative, devote, chaotic ©2005 Angeli/Grice logosworld.com

23. Logosworld.com What The Others Do?  Imperative  Military Works with small teams and linear tasks Suitable within a team but not to control collaboration  Devote  Abbey Only suitable for ambitious, small and sworn in teams Typically found in science and labs  Chaotic  Orchestra The only choice starting from a certain team size Used also for meta management Most projects follow the orchestra principle Often they are in contention with governance ruling  Imperative  Military Works with small teams and linear tasks Suitable within a team but not to control collaboration  Devote  Abbey Only suitable for ambitious, small and sworn in teams Typically found in science and labs  Chaotic  Orchestra The only choice starting from a certain team size Used also for meta management Most projects follow the orchestra principle Often they are in contention with governance ruling

24. Logosworld.com Areas of SOA Benefit

25. Logosworld.com Meta Data Management  metadata provides access to data objects and enables policy-based storage management.  essential to information lifecycle management (ILM)  Key factors that drive the design of a metadata management program  metadata management will benefit your compliance strategy, externally facing and service applications, and internally shared applications.  metadata provides access to data objects and enables policy-based storage management.  essential to information lifecycle management (ILM)  Key factors that drive the design of a metadata management program  metadata management will benefit your compliance strategy, externally facing and service applications, and internally shared applications.