Downloaded 10 times
Uploaded byAlexey Kovalyov
TRANSFORMATION STORY: 100 SYSTEMS vs 30 DEVELOPERS
The document outlines a case study of an organization's agile transformation, moving from over 100 legacy systems to a more efficient system involving 30 agile developers. It details various stages of development, including initial disorganization and gradual improvement in system ownership, team structure, and methodology. The final stage emphasizes autonomy, transparency, and scalability within a network of project teams.
More Related Content
Similar to TRANSFORMATION STORY: 100 SYSTEMS vs 30 DEVELOPERS
TRANSFORMATION STORY: 100 SYSTEMS vs 30 DEVELOPERS
- 1. / 100 LEGACY SYSTEMS vs 30AGILE DEVELOPERS Epic transformation story 2015-12-14 Alexey Kovaliov Head of Information Systems Department
- 2.
- 3. PURPOSE? ● Different organizationalpatterns suitable for Agile ● Case study of the Agile adoption ● ~3500 employee company ● ~90 employee Information Systems unit ● + Subcontractors ● Encourage to adopt Agile in product or industrial companies ● Encourage to experiment and seek for organization efficiency 2015-12-14 3
- 4. Do Not Walkthe Road of 100 LI
- 5. 2 YEARS. 4TRANSFORMATIONS 2015-12-14 5
- 6. 100+ LEGACY SYSTEMS ●Business Support Systems ● Sales Channels ● CRM ● Billing ● Order Management ● Operations Support Systems ● Telco ● Datacenters ● Service centers ● Enterprise Resource Planning ● Finances ● HR ● Corporate compliance ● Data Analytics 2015-12-14 6
- 7. STAGE 0: ZOMBIES& SPAGHETTI ● #.# Headcount per system ● 0.25 – 15.00 ● Utilization 100% ● No resource sharing ● No teamwork ● No task management tools ● No methodology ● Disorganization ● Unmotivated undead ● Good for budgeting ● Worst for scale and prioritization 2015-12-14 7
- 8. STAGE 0: ZEROSCALING 2015-12-14 8
- 9. STAGE 1: SYSTEMFACTORIES ● 3-4 Thematic groups of systems ● System Factory is a sub-unit ● Manager ● System Analysts ● Software Developers ● Testers ● Agile/Scrum ● Integration with Work Order tool ● Automated KPIs ● Scalability problem ● Thick spaghetti 2015-12-14 9
- 10. STAGE 1: FACTORYIN FACTORY 2015-12-14 10
- 11. STAGE 1+: TROOPERS ●Troopers = 2 Dedicated teams ● Software Developers ● Tester ● Fast and adoptable ● Break through with new projects ● Dedicated Agile backlogs ● Requirements QA and acceptance ● Pass the results Harrison ● Harrison = Factory ● Supports legacy ● Owns the systems ● New projects’ results’ QA 2015-12-14 11
- 12. STAGE 2: IN-HOUSESYSTEM FACTORIES ● 50 employee unit moves to TEO ● Easy “as is” integration ● No one left behind ● Not a single idle day ● Same Agile approach ● Ownership of the systems ● Improved scalability ● Internal + External Troopers ● New challenges: ● Redundancies of roles ● Internal/External costs 2015-12-14 12
- 13. STAGE 3: FUNCTIONALSILOS ● Roles Consolidation ● Analysts Planning ● Analysts Support ● Testers Support ● Less Management Roles ● Purified SWD Unit ● Managers ● SWD Teams ● Subcontractors Troopers ● SWD KPIs ● Limited Agile ● Issues with Agile planning 2015-12-14 13
- 14.
- 15. STAGE 4: CELL-BASEDNETWORK ● Market ● All TEO Units ● External Sphere ● 5 Systems Ownership Teams ● Project Managers Team ● KANBAN ● Internal Sphere ● Architect Team ● SWD Teams ● External SWD Teams ● QA Team ● Resource Managers Team ● Scrum/KANBAN 2015-12-14 15
- 16. 2015-12-14 16 STAGE 4:CLOSER LOOK
- 17. BENEFITS ● Autonomy andself-organization of the teams ● 2 level hierarchy for 85 employee organization ● As less management as possible ● External sphere is the King ● Transparency of every team’s tasks and roles ● Single Window principle both for WO and Support ● Extensibility by External Troopers still staying Agile ● Same backlogs for everyone ● Fits into even more sophisticated Technology projects organization ● Hardware ● Telco infrastructure ● Business transformations 2015-12-14 17
- 18.
- 19. EVERYBODY LOVES KITTENSMETHODOLOGIES ● Niels Pflaeging ● http://www.betacodex.org/ ● Tons of free materials to download ● Workshops 2015-12-14 19
- 20. EVERYBODY LOVES KITTENSTOOLS 2015-12-14 20 Purpose Tool Strategic Roadmapping Microsoft Excel System Team Roadmapping Work Order Lifecycle In-house build tool Complex Project Management Microsoft Excel Microsoft Project Product Backlog Microsoft Team Foundation Server Sprint Backlog Kanban Boards Sprint Boards Requirements Engineering Microsoft Office (moving to Magic Draw) Support Incidents Lifecycle SiAL
- 21. NEXT? ● Prove itworks and good for the KPIs ● Adopt similar approaches thorough the company 2015-12-14 21
- 22.