Post on 05-Jul-2020
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
STAYING GLOBAL IN AN AGILE WORLD
WEDNESDAY, DECEMBER 19TH, 2012. BEGINNING AT 11:00 AM PT
Adam Asnes
CEO & President
Lingoport
aasnes@lingoport.com
Olivier Libouban
Globalization Lead
Lingoport
olibouban@lingoport.com
Richard Sikes
Translation Technology Expert
Localization Flow Technologies
richard.sikes@locflowtech.com
Insights supporting Agile development
• Globalyzer
• Resource Manager
(LRM)
• Dashboard
• i18N Assessments
• Implementations
• Consulting
• Training
• Center of Excellence
What’s in a sprint?
• Changes to U/I content
• Changes to help
• Testing cycle missed
• Engineering overhead
• “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.
What we hear
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
Waterfal l = ~Predictability
Used by permission by Commonplaces, Inc. http://www.commonplaces.com
Software developers got together to
seek a better route to c l ient sat isfact ion .
www.agilemanifesto.org
Agile: iterative, constant change.
Used by permission by Commonplaces, Inc. http://www.commonplaces.com
Credit: Nifflers-Unite
Developers felt that they had come
up with something great!
Localization managers weren’t so
sure!
The results:
• 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.
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
• My individuals are all over
the world, spread out in
diverse time zones.
• Localization is a sequential
process.
• I need my tools: translation
memory, terminology
extraction and
management, workflow
status, query management,
project content distribution
and retrieval.
Developers say… Localizers think…
• Individuals and
interactions over
processes and tools
• Working software over
comprehensive
documentation
• Customer
collaboration over
contract negotiation
• Responding to change
over following a plan
• With no functional
specification, how can my
translators know what the
software is supposed to do
without extensive and time-
consuming
experimentation?
• What codified baseline can
we use to measure the
accuracy of the translation?
Developers say… Localizers think…
• Individuals and
interactions over
processes and tools
• Working software over
comprehensive
documentation
• Customer
collaboration over
contract negotiation
• Responding to change
over following a plan
• Customer collaboration does not help me to solicit project bids.
• Acquiring customer involvement in approval of localized content can be a real can of worms, and this will be multiplied by numerous languages.
Developers say… Localizers think…
• Individuals and
interactions over
processes and tools
• Working software over
comprehensive
documentation
• Customer
collaboration over
contract negotiation
• Responding to change
over following a plan
• Change-tracking is
problematic, especially
when anecdotal.
• Ongoing change causes me
to excessively rely on others
to provide information.
• Change introduces
disruptive unpredictability.
• Change costs time and
money from my budget, not
theirs.
Developers say… Localizers think…
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.
Lingoport
Resource
Manager
Agile is here to stay; localizers need some
help to become agile as well.
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 & Verify
Build L10n Kit
Send for Translation
Verify
Reintegrate
Dashboard & Resources
Questions & Answers
Twitter: #AgileL10n
Adam Asnes
adam@lingoport.com
Olivier Libouban
olivier@lingoport.com
Richard Sikes
richard.sikes@locflowtech.com
Upcoming!
2013 i18N and L10n Conference
& Training
March 13 & 14
Santa Clara, CA
Learn more at:
Lingoport.com/events