[Openmind 2012] LiMux - the IT-Evolution: Status of Migration by Jutta Kreyss (Architect, LiMux/City of Munich)

Openmind 2012 / Open Knowledge Festival 2012
http://okfestival.org/open-source-software/

Transcript

1. LiMux - the IT-Evolution
   Status of Migration
   Dr. Jutta Kreyss, IT Architect, LiMux (Munich, Germany)
   OKFestival, Helsinki
   19th of September 2012
   

   View Slide

2. Seite 2
   © 2012 Landeshauptstadt München
   Agenda
   Current status of the LiMux project in Munich
   To do's
   Lessons learned
   Open Source Software:
   The „magic square“ of the public sector
   

   View Slide

3. Seite 3
   © 2012 Landeshauptstadt München
   The IT-Organization
   Facts at project start
   ~ 33.000 employees
   (~ 1.000 located in the IT)
   ~ 15.000 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
   

   View Slide

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

   View Slide

5. Seite 5
   © 2012 Landeshauptstadt München
   Migration „on the Fly“
   Officemigration Limux „germ cell“
   ... 2007 2008 2009 2010 2011 2012 2013
   Run
   Concept
   Rollout
   Implementation
   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)
   

   View Slide

6. © 2012 Landeshauptstadt München
   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
   2009: Requirements engineering
   Supporting customer in defining
   requirements
   Establishing requirement analysts
   TRAC as a tool for release- and
   requirementmanagement (Assyst, ITIL®
   processes)
   2010: Communication and documentation
   Defining precise customer responsibilities
   Premature communication of target
   audience-relevant milestones
   Adding unbiased external team members
   for project management and IT-architecture
   Admin documentation:
   LaTech/PDF: ~ 500 pages
   2011: Quality assurance
   Quality plan
   Adding an independent and experienced
   testteam
   Tool: Testlink/TRAC
   Precise definition of bug severity
   Quality gates
   Testcoordination
   

   View Slide

7. © 2012 Landeshauptstadt München
   2012: The magic square of the public sector
   Vendor independance
   Internal skills
   Political framework
   Procurement
   Open Source Software
   

   View Slide

8. Seite 8
   © 2012 Landeshauptstadt München
   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
   

   View Slide

9. www.muenchen.de/limux; email: limux@muenchen.de
   LiMux – Munich's Independence
   

   View Slide