Because software development never stops when the first version of a product is released (bug fixes, minor updates and at some point major new versions and releases) — continuously. Your localization and translation process should follow the same pattern as your software development.
You're already using agile concepts in your software development, right?
Add some agility also in your localization process!
Translations should take place in parallel with agile sprints and in smaller batches. This means translating just a part of a software product and not the whole at once. Even better, translating continuously.
The benefit to developers is clear-cut: align localization efforts with the development cycle by automating and accelerating the steps involved. This way, they can seamlessly integrate their localization processes into their development cycle.
You localize, as a normal part of the development process cycle. No separate localization testing phase. Translation testing is part of normal software testing activity.
The translators can work on text that the developers have just added. There is no wait for a particular milestone.
Keeping translations in sync with development, reduces drastically the project complexity. A project management enjoys this, because it takes lots of tedious work from product managers that they would otherwise have to perform.
tldr; Shorter, faster development cycles, faster time-to-market.
The following team roles are at least included in a typical in-house localization team:
After a successful implementation for the continuous localization workflow, the process will look more or less like this:
While this approach can be implemented together with most translation management systems, there is also a more modern approach...
You should be able to deploy your translation files separated from your software so you can update and manage them independently. Something like a platform, that anyone can directly integrate with.
The process could look like this:
If you do so, you have to make sure you can have more than one version of your translations; at least one for the current released version and one for the current development branch. That way your technical writers and translators can take care of the translations from the first day and keep up with changes with ease. By doing this it is even possible to change or add translations without shipping a new release of your software! You may also want to have some reviewing workflow, auditing, integrated ordering of external translations, etc...
Cool, but isn’t this a little over the top… an extra tooling and deployment — doesn’t all this just add more complexity and effort?
Watch the demo video to learn more:
locize removes the pain in the translation process. No more delays in shipping your software because of missing translations. Translators can keep up with changes from day one. The continuous localization process keeps up with your demanding business.