LiMux - the IT-Evolution Status of Migration

Transcription

1 LiMux - the IT-Evolution Status of Migration Dr. Jutta Kreyss, IT Architect, LiMux (Munich, Germany) Civil Service Event about FOSS, London 10th of July 2012

2 Agenda Current status of the LiMux project in Munich To do's Lessons learned Open Source Software: The magic square of the public sector Seite 2

3 The IT-Organization Facts at project start ~ employees (~ located in the IT) ~ PC-workstations 51 locations 22 independent IT-departments ~ 140 mio Euro IT-expenses Today: Foundation of Munichs centralized IT (it@m) 01/01/2012: Centralizing plan, build and run and standardization of business application Seite 3

4 Our Main To-Dos Coordination of migration, 2nd and 3rd level support, organization, PM, PMO etc. Project management Specialised software (business services) SAP, DMS, special public sector software packages (backports etc.) Software not included in source distribution: ~ 10% pre-configuration and branding profilesynchronisation, mail, browser, desktop Usability and security requirements Hardening, virus scanner, user rights management... Basic distribution Ubuntu: ~ 90% of all packages Softwaremanagement system GOSa² and FAI Seite 4

5 Migration on the Fly Implementation... Concept Officemigration Limux germ cell Rollout The project LiMux supports the centralised IT department regarding Standardization (infrastructure, operating system, software versioning) Consolidation (Templates, macros, applications) Automatization (software distribution FAI/GOsa) Virtualization (server & desktop) Seite 5 Run

6 Current status: About LiMux PC-workstations Seite 6

7 Business Applications: Four Alternatives to Run Them 25% Open Web based applications, Java processes and applications, available on several operating systems Native Linuxbased programs and applications, included in the LiMux Client Virtual Applications, either virtualised and available on desktop or placed on a terminalserver (Open platform) 30% 15% 10% (Linux-application) (Desktop or terminalserver) Windows (Windows PC) Applications, not yet available on open platform and currently not ready for virtualisation Some business applications are not relevant anymore 15% Not applicable Seite 7

8 Lessons Learned 2008: Requirements are out of control Switch to time-based releases Priorisation of requirements according to measurable criteria Feature freeze at the start of development Moving internal requirement management processes from theory to practice 2010: Communication and documentation 2009: Requirements engineering Supporting customer in defining requirements Establishing requirement analysts TRAC as a tool for release- and requirementmanagement (Assyst, ITIL processes) 2011: Quality assurance Defining precise customer responsibilities Quality plan Premature communication of target audience-relevant milestones Adding an independent and experienced testteam Adding unbiased external team members for project management and IT-architecture Tool: Testlink/TRAC Admin documentation: LaTech/PDF: ~ 500 pages Quality gates Precise definition of bug severity Testcoordination

9 2012: The magic square of the public sector Vendor independance Procurement Open Source Software Political framework Internal skills

10 Summary Get backing within your political framework Be customer focused Standardize, consolidate and optimize Keep an eye on the project's dynamic Communicate, communicate, communicate Seite 10

11 LiMux Munich's Independence