Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

How Agile helps Localization with an old Dilema

764 views

Published on

Localization is often considered an "after-thought" to development, i.e. planning for localization, if it happens at all, takes place at the very end or after the development cycle.
This presentation is a case study how Agile helped localization to become part of a SAP development Project.

The presentation was given as part of the Localization Institute's PM Certification Workshop in Berlin, June 2015

Matthias Caesar, iLocIT

Published in: Business
  • Be the first to comment

How Agile helps Localization with an old Dilema

  1. 1. Your company logo here This work by iLocIT! is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License “How Agile helps Localization with an old Dilemma!” Matthias Caesar, iLocIT!
  2. 2. Your company logo here This work by iLocIT! is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License Outline - The Project  Localization of SAP Applications at a German DAX30 company  Past  Present  Future  … and why Agile?
  3. 3. Your company logo here This work by iLocIT! is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License + Many HEADs, No owner ad-hoc, ‘after-thought’, no planning, no awareness Past
  4. 4. Your company logo here This work by iLocIT! is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License Main reasons for looking at “Agile” a) The time-to-market for a Change or a Fix is ~200 days due to functional as well as technical system landscape complexity b) There is a back-log of ~200 tickets. Business grows weary of this c) Ping-pong between DEV and QAS systems causes too much disturbances
  5. 5. Your company logo here This work by iLocIT! is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License 5 Put the project (back) on track! But which track, actually?
  6. 6. Your company logo here This work by iLocIT! is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License
  7. 7. Your company logo here This work by iLocIT! is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License Agile and Localization Oh no, this means more frequent and much smaller handoffs, so much more overhead! ….
  8. 8. Your company logo here This work by iLocIT! is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License
  9. 9. Your company logo here This work by iLocIT! is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License The “Agile Manifesto” – the basics “Agile” methodologies value: Individuals and interaction over Processes and tools Working software over Comprehensive documentation Customer collaboration over Contract negotiation Responding to change over Following a plan That is, while there is value in the items on the right, the items on the left are valued more.
  10. 10. Your company logo here This work by iLocIT! is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License “Agile” methods compared to Waterfall Key characteristics of ‘Waterfall’ • Plan-Ceremony driven • Command and control management • Single pass waterfall (Sequential model) • Success = compliancy predictive plan • Progress = ‘deliverables’ – Specs/design/code/reviews/signatures • Resisting/blocking ‘change’ Key characteristics of ‘Agile’ • End-user representative working in one multidisciplinary team with developers and tester(s); preferably co-located • Servant-leadership Subtle control • Iterative-incremental process, MoSCoW, continuous integration, prototyping • Success = business value • Progress = working software • Progressed understanding is factored in immediatelyanalyze design build test A D C T A D C T A D C T A D C T Iterations or‘Sprints’
  11. 11. Your company logo here This work by iLocIT! is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License “Agile” methods compared to Waterfall Key characteristics of ‘Waterfall’ • Plan-Ceremony driven • Command and control management • Single pass waterfall (Sequential model) • Success = compliancy predictive plan • Progress = ‘deliverables’ – Specs/design/code/reviews/signatures • Resisting/blocking ‘change’ Key characteristics of ‘Agile’ • End-user representative working in one multidisciplinary team with developers and tester(s); preferably co-located • Servant-leadership Subtle control • Iterative-incremental process, MoSCoW, continuous integration, prototyping • Success = business value • Progress = working software • Progressed understanding is factored in immediatelyanalyze design build test A D C T A D C T A D C T A D C T Iterations or‘Sprints’
  12. 12. Your company logo here This work by iLocIT! is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License “Agile” terminology, mechanics and principles The core mechanics • Roles Agile Team – Scrum Master – Product Owner – Agile Core Team 3-9 people • Events – Sprint Planning – Daily Scrum – Sprint Review (Demo + Retrospective) • Artefacts – Product Backlog – Sprint Backlog – Progress Trends The core principles • Shared Visual workspace – Remove all physical barriers – Transparency & Visual Management – Face-to-face communication • Self-organizing – Empowered cross-functional Teams – Incremental design and architecture – Inspect & adapt • Empiricism – Closed-loop process control – Knowledge from experience – Detect & eliminate variances
  13. 13. Your company logo here This work by iLocIT! is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License “Agile” terminology, mechanics and principles The core mechanics • Roles Agile Team – Scrum Master – Product Owner – Agile Core Team 3-9 people • Events – Sprint Planning – Daily Scrum – Sprint Review (Demo + Retrospective) • Artefacts – Product Backlog – Sprint Backlog – Progress Trends The core principles • Shared Visual workspace – Remove all physical barriers – Transparency & Visual Management – Face-to-face communication • Self-organizing – Empowered cross-functional Teams – Incremental design and architecture – Inspect & adapt • Empiricism (Pragmatism) – Closed-loop process control – Knowledge from experience – Detect & eliminate variances
  14. 14. Your company logo here This work by iLocIT! is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License Facts on “Agile” methodologies  Gartner (2010): ‘Agile is now a mainstream, mature and proven set of development methods.  SAP AG adopted Agile methodologies internally back in 2009  Gartner (2012): ‘Traditional projects need to look past the development process to find valuable practices in Agile’  SAP (2012) says amongst others: “With an Agile approach you gain buy-in and build confidence through early review cycles: receive early and frequent confirmation on requirements”  SAP AG (2012) claims Agile has been used successfully in projects of various sizes / scope
  15. 15. Your company logo here This work by iLocIT! is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License Agile SAP Ways of Working
  16. 16. Your company logo here This work by iLocIT! is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License What does a Sprint look like?
  17. 17. Your company logo here This work by iLocIT! is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License What roles are impacted by “Agile” Ways of Working? Most Impacted • Business user / ‘Product owner’ • System Architect • ‘SCRUM Master’ • Template Development team member • Testers • Functional Enhancement Project Manager Impacted • Change Manager • Project manager • Trainers • Application Support • Application Operations • Translators • Documenters • Security team • Master Data team • Business analysts Synergies
  18. 18. Your company logo here This work by iLocIT! is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License + almost ONE owner Scheduled Present
  19. 19. Your company logo here This work by iLocIT! is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License
  20. 20. Your company logo here This work by iLocIT! is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License
  21. 21. Your company logo here This work by iLocIT! is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License + Agile! – what change(d)?  Localization became part of the planning  Localization starts with the project (not after)  Localization is needed to meet the goal  Localization workflow (semi-)automated (future) Agile
  22. 22. Your company logo here This work by iLocIT! is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License
  23. 23. Your company logo here This work by iLocIT! is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License + ONE, and only one, OWNER Synchronized Future
  24. 24. Your company logo here This work by iLocIT! is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License
  25. 25. Your company logo here This work by iLocIT! is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License + Good Luck! and… Thank you8 June, 2015 iLocIT Im Papenkamp 20 D-44267 Dortmund p +49.231.9159631 f +49.231.9159694 e info@iLocIT.de @iLocIT @MattKeyzer

×