1. Become an Agile-ista! Wayne Bourland (Dell) Kåre Lindahl (Venga) Stanislav Kalianov (Schneider Electric) Mika Pehkonen (F-secure)

2. Benefits of Agile

3. InfoDev benefits from agile practices 3

4. Benefits of agile How Agile benefitted my company Faster time to market - more frequent releases, customer feedback. Current release schedule: 4 major releases per year, technology previews bi- weekly (to beta group and select customers). How agile benefitted localization Shift from project management to customer service. Continuous improvement of processes, tools and bug fixing, faster reaction times to anomalies in measurements. Work less stressful with leveled workload; more time for innovation through use of automation. Ownership of work (documentation and localization as a feature).

5. Schneider Electric 5 - StruxureWare for Data Centers : Operations Suite How Agile benefited my company? ●Complete DCIM suite ●Market leader in 3 years ●“… comprehensive, integrated and advanced DCIM suite.” the 451 group ●11 languages ●2 major releases per year ● x3 more localised projects

6. Workflow

7. 7 ●No frequent drops! ●Not even the automated ones ●Keep work in-house ●Locate strings for translation ●Wordcount ●Pseudo-translate ●Test pseudo ●Only go for translation when it’s time

8. Workflow

9. © 2011 Autodesk Traditional Workflow: Localization Process

10. © 2011 Autodesk Continuous Workflow

11. 11 Finance ●Typically two PO per project ●Initial PO, based on estimate ●Final PO, adjustment to real work ●Accurate forecast based on “team velocity”

12. Finance

13. Follow the Money

14. Finance Since the hourly bandwidth (50% of word volume in 2011) is common to all internal customers and a predictable cost, and customer specific incremental changes (deltas) are in general very small (5-300 words), there is no benefit to per project/hand-off internal or external billing. The time savings in administrative overhead used towards improvements in quality, automation.

15. Technology

16. © 2011 Autodesk Automating the WorldServer Workflows

17. Process, technology and philosophy Single-sourcing, XML, TMX, variables Python: Building links between systems and tools, automated checks and fixes. Quality: Focus away from over-processing imperfections and irrelevant feedback to ensuring usability. Translation tools: Elimination of ICE matches and 100% matches essential, preferably by scripts through command line. Automated building important. Translation: Moving towards giving as much freedom to translator/vendor as possible, organizing innovation time for translators. Focus away from words towards interactions. TMS: Improved workflow, enabling self-organization on translation side.

18. 18 Technology ●Documentation ●Emphasis on sharing ●Means of agreement ●Planning ●Plan for “project in general” ●Communicate well in advance ●Have “white holes” in our plans ●Freedom ●In defined limits ●Wiki ●Internal – Plan, QA, ●Customer – Doc, Support ●Agile planning tools ●Continuous build system ●Social networking

19. Thank you! For more information or if you just want to chat… Mika Pehkonen - mika.pehkonen@f-secure.commika.pehkonen@f-secure.com Stanislav Kalianov - Stanislav.Kalianov@schneider-electric.comStanislav.Kalianov@schneider-electric.com Wayne Bourland - Wayne_Bourland@dell.comWayne_Bourland@dell.com Kåre Lindahl – kare.lindahl@vengacorp.comkare.lindahl@vengacorp.com