STAYING GLOBAL IN AN AGILE WORLD AM PT WEDNESDAY , DECEMBER 19TH, 2012. BEGINNING AT 11:00 Adam Asnes Richard Sikes CEO & President Translation Technology Expert Lingoport Localization Flow Technologies aasnes@lingoport.com richard.sikes@locflowtech.com Olivier Libouban Globalization Lead Lingoport olibouban@lingoport.com Submit questions using the GoToWebinar Q&A interface or through Twitter with hash-tag: #AgileL10n Connect with Lingoport: Twitter @ https://twitter.com/lingoport 2013 i18N & L10n Conference: See Lingoport.com/events
Insights supporting Agile development • i18N Assessments • Globalyzer • Implementations • Resource Manager • Consulting (LRM) • Training • Dashboard • Center of Excellence
What’s in a sprint? • Changes to U/I content • Changes to help • Testing cycle missed • Engineering overhead
What we hear • “Localization can’t be done in a 3 week sprint!” • Our SaaS product has loyal global users, but we’re missing localization releases because we can’t keep up. • The simple overhead with adding the translations has our developers putting them aside • Even if teams are not Agile, they are generally using some aspects of Agile practices.
Our service project L10n experience • On i18N projects, we typically manage integration of L10n • Always a “bookkeeping” hassle • Are the strings all there? • Need to compare with partial deliveries • String id’s in order? • Verify that the encoding hasn’t been broken • Last minute changes cause more tracking
Problems we can solve • i18N is built into development metrics • L10n visibility into development at the source level • Development has visibility into L10n • Software is great at handling the “bookkeeping stuff” • Speed up L10n access and reintegration into the build
Waterfall = ~Predictability Used by permission by Commonplaces, Inc. http://www.commonplaces.com
Software developers got together to seek a better route to client satisfaction.
www.agilemanifesto.org
Agile: iterative, constant change. Used by permission by Commonplaces, Inc. http://www.commonplaces.com
The results: Developers felt that they had come up with something great! Localization managers weren’t so sure! Credit: Nifflers-Unite
Agile Manifesto Value Statement • Individuals and interactions 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, we value the items on the left more.
Localizers think … Developers say… • Individuals and • My individuals are all over interactions over the world, spread out in processes and tools diverse time zones. • Working software over • Localization is a sequential comprehensive process. documentation • I need my tools: translation • Customer memory, terminology collaboration over extraction and contract negotiation management, workflow status, query management, • Responding to change project content distribution over following a plan and retrieval.
Localizers think … Developers say… • Individuals and • With no functional interactions over specification, how can my processes and tools translators know what the software is supposed to do • Working software ove r without extensive and time- comprehensive consuming documentation experimentation? • Customer • What codified baseline can collaboration over we use to measure the contract negotiation accuracy of the translation? • Responding to change over following a plan
Localizers think … Developers say… • Customer collaboration • Individuals and does not help me to solicit interactions over project bids. processes and tools • Acquiring customer • Working software over involvement in approval of comprehensive localized content can be a documentation real can of worms, and this • Customer will be multiplied by numerous languages. collaboration over contract negotiation • Responding to change over following a plan
Localizers think … Developers say… • Individuals and • Change-tracking is interactions over problematic, especially processes and tools when anecdotal. • Working software over • Ongoing change causes me comprehensive to excessively rely on others documentation to provide information. • Customer • Change introduces collaboration over disruptive unpredictability. contract negotiation • Change costs time and • Responding to change money from my budget, not over following a plan theirs.
Path to Agile Localization Poll #2
Efficient localization requires waterfall-like sequentialization • Testing Resource Files for localization- readiness prior to translation. • Isolating, packaging and transmitting only the resource files that are localization-ready. • Testing of resource files returned from translation prior to checking them into version control. • Careful reintegration of the localized resource files prior to creating localized product builds. • Language independence for localized product builds.
Fitting localization in Agile: square peg in round hole • Having localization personnel at every scrum meeting may not be feasible or appropriate. • Sprints impose scalability limits, especially in more complex or larger projects. • Changes need to be monitored and isolated with surgical precision. • Software engineers should be adding product value, not doing accounting or financial projections.
Agile is here to stay; localizers need some help to become agile as well. Lingoport Resource Manager
Lingoport Resource Manager A solution that provides flexibility and oversight for all stakeholders as software resource files move through the development and localization work streams.
Adam will say a few more words, and then Olivier will show how it is done!
Source Detect changes Reintegrate & Verify Verify Build L10n Kit Send for Translation
Dashboard & Resources
Questions & Answers Twitter: #AgileL10n Upcoming! Adam Asnes 2013 i18N and L10n Conference & Training adam@lingoport.com March 13 & 14 Olivier Libouban Santa Clara, CA olivier@lingoport.com Learn more at: Richard Sikes Lingoport.com/events richard.sikes@locflowtech.com
Recommend
More recommend