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

Transcription

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

2 Benefits of Agile Client: Provider Same Time Zone Closer access to SMEs Same Time Zone Closer access to SMEs Better at meeting customer s actual needs Reduce time wasting Steady stream of projects

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 biweekly (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 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 Schneider Electric - StruxureWare for Data Centers : Operations Suite 5

6 Workflow Monday Exporting incremental changes, building kit (Automated, script that polls version control and creates translator s kits + build & import scripts for Wednesday) Sending localization kit (Manual, mostly short instructions and priorities, communication) Tuesday Vendor project management Hourly translation Wednesday Building files from kits (Automated, see Monday) Testing of built files (Automated, mostly technical validity checks) Automated fixes Committing files (Automated) Thursday Bug fixing (Manual, based on scripted and human effort) Friday Improvement/Innovation projects

7 Workflow 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 Translation Pseudo Translation Source Translate Test Fix Fix Test Pseudo-translate Estimate Count New content 7

8 Integrate processes Workflow Steady stream Localization testing and bug resolution Shorter distance between people reduce steps Builds SME and understanding Same time zone Automate as many steps as possible Improve quality and speed Automate pseudo and localization testing

9 Traditional Workflow: Localization Process 2011 Autodesk

10 Continuous Workflow 2011 Autodesk

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

12 Finance Educate Finance Budgeting Purchase orders Why is localization different Estimate volume for year No time for accurate competitive quotes Agree on workable timeline Consider per word and per hour pricing Reporting to validate work done

13 Follow the Money Waterfall Payroll: Agile Payroll: Engineering QA Product Marketing Technical Writers Engineering QA Product Marketing Technical Writers Purchasing Purchasing Localization Provider One PO per major project tens per year Localization Provider One PO per iteration hundreds/thousands per year

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 Standards & Formats Globalization Standards Technology Automation & Integration Reduce steps, e.g. logging bugs in client system Control Language Assets Central TMS File formats & Naming Conventions Reduce manual steps Central Terminology

16 Automating the WorldServer Workflows 2011 Autodesk

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 Technology Documentation Emphasis on sharing Means of agreement Planning Plan for project in general Communicate well in advance Have white holes in our plans Wiki Internal Plan, QA, Customer Doc, Support Agile planning tools Continuous build system Freedom In defined limits Social networking 18

19 Thank you! For more information or if you just want to chat Mika Pehkonen secure.com Stanislav Kalianov electric.com Wayne Bourland Kåre Lindahl