Organisation av Integrations- & Informationsarbete Öyvind Tönnessen

Agenda Organisationskartor Förankring inom ledning och organisation Center of Excellence/"Integrationsråd" Behovet för integration Vart börjar man (Analys, metoder, A2A, B2B, B2C etc.) Ressursbehov

Project Organisation

Management sponsorship

The Making of the ICC Architecture and Prototype Project Strategic Imperative: The organization, roles and responsibilities of the ICC change at each stage of application integration. The IT organizational model must change as the organization progresses through the application integration phases. The Making of the ICC Architecture and Prototype Project Pilot Project and First Production Deployment Common Practice Architecture Group Project Team Architecture Group Project Team Integration Center Project Team Architecture Group Integration Center Project Team 1. Plan and Justify 2. Pilot Projects 3. Early Adoption

What Skills Are Needed in an Integration Project or in a Mature ICC? Tactical Guideline: When the project starts, the integration team is no longer composed mainly of cooperative architects. Many different skills will be needed for project success. What Skills Are Needed in an Integration Project or in a Mature ICC? Business Analysts Business Modeling* Business Domain Knowledge* Quality Assurance Process* Test scripts Testing tools ICC Administration Maintain All Integration* Documentation* Best Practices* Metadata Management* Development Project Management* Application Knowledge Development Skills Testing Skills Architecture Vision and Integration* Architecture* Selection of New Technology* Platform Architecture Integration Project Product and Application Vendors Application Data Model* Integration Middleware* Pilot Project Support Adapters* Database Administration Data Modeling Expertise Modeling Tools Enterprise Data Knowledge* Internal Marketing Communicating the Vision* Demonstrating the Value* ("Success Stories") Suggesting Projects* Operations and System Administration Middleware Installation and Configuration Server and Network Configuration Systems Management*

The Four Stages of Application Integration 1. Plan and Justify 2. Pilot Projects 3. Early Adoption 4. Broad Adoption Go? Go? Planning Business drivers Technical potential Vision Business case Product selection Proof of concept First Project Choose the project Assess readiness Build the team Ensure success Evaluation Move to production Proliferation Advocacy and education Competency center Failure analysis Process improvement Best practices Toward Maturity Application integration everywhere Mature IT organization Metrics Ongoing education

Engagement Lifecycle - Methodology FastTrack Assessment CSF Pilot Enterprise CoE Workshop SOA Governance SOA Methodology Go-Live Certification Enterprise Integration HealthCheck

Pilot Implementation - example Phase 1- Project Establishment Phase 2 – Analysis Phase 3 – Training Phase 4 – Pilot Phase 5 – Roll-up ”Live” implementations Objective: Secure project resources and common objectives. Objective: provide detailed analysis of infrastructure and architecture for integration platform Objective: Initial training and Knowledge transfer for XXX resources Objective: Implement re-usable pilot and make XXX self-sufficient Objective: Last preparations and roll-ups before putting ”real” projects into development 01.04. 2006 15.04. 2006 01.05. 2006 15.05. 2006 15.07. 2006 01.09. 2006 Establish project organisation Detailed project plan Establish integration Office Roll-up of knowledge Prepare for project take-up Infrastructure analysis HW procurement Architecture analysis Training Knowledge transfer Pilot identification Pilot implementation using methodology MS1 MS2 MS3 Pilot Start Pilot delivered Pilot complete

SOA High Level Rollout

Project resources - example XXX & Partner 1 Project Manager 1-2 Architects 2-4 Developers 1-2 Administrators Business resources Vendor 2 - 3 full-time architect/consultant 0,5 - 1 Tech Project Manager