1. Automation Practice under Agile Software L10N Context
Pan Jian-Hua(Jonathan)
HP Software G11N

2. Self Introduction 12 Years in SW L10N Industry
Skype: hppanjianhua
GitHub: (Constructing!)
12 Years in SW L10N Industry
Program/Project Management, Agile(Scrum), L10N tools, L10N Workflow Automation etc.
Python, PowerShell, VBScript(VBA) programming.
Linguistic Master (FuDan University)
PMP certified (expired) /ITIL Foundation certified.

3. Session Goal Not About About
A “general” end-to-end solution to Agile L10N
An innovative Automation framework
About
A case study
How to adopt Agile mind-set and methodology in real Agile L10N life

4. Agenda Key Agile Concepts in My Eye What Agile L10N Means?
Automation = Formidable Enemy?
Case Study
Recap
Q&A

5. Key Agile Concepts in My Eye
“Agile” Mind-Set and Methodology:
“Business Value” consideration
Do “Right” things; do things “Right”
Remove “Waste” from process
Simplify process and work step
Continuous delivery for improvement
Agile Software Dev and Test:
Deliver “workable” software incrementally
Agile Software L10N:
Deliver “well localized” software incrementally

6. What Agile L10N Means? Automation on Software Translation Process.
Continuous Translation Delivery Mode:
L10N drop alignment with RnD “Iteration” plan
(Bi)Weekly pickup and delivery
2-3 days “on-demand” delivery
L10N drop 1
L10N drop 2
L10N drop 3
Iteration 1
Iteration 2
Iteration 3
Iteration 4
Week1
Week2
Week3
Week4
Week5
Week6

7. Automation = Formidable Enemy?
Everyone can play Agile L10N Automation game!
Prerequisite:
Business Value
Technical Feasibility
Process Standardization
Step Break-down

8. Automation = Formidable Enemy?
Methodology
Business-Driven Scope
Practical Technology
Not Reinvent Wheel
Bottom-To-Top
Modularization (step-by-step)
Integration (end-to-end)
Workable then Better

9. Case Study: Fact Sheet
BSM (Business Service Management, a Portfolio Product)
Scope: 7 languages
Translation Tool: SDL Passolo
RnD: ~ 15 teams
Vendors: 4 vendors
Scenario: Continuous translation alignment with RnD iteration

10. Case Study: Challenges
3 days! pre-post 1
L10n drop!
Total ~15 Passolo lpu project files !
Each component R&D works differently: 4 L10N file exchange ways!
All manual work for L10n drop Preparation& Delivery
Q: Where to Start?

11. Case Study: Business Value & Technical Feasibility Analysis
Manual : (pre) + 1(post) = 3 days/drop
Traditional L10N: 3 * 4 = 12 days
Agile L10N: * 14 = 42 days!
Automation: ???
Technical Feasibility:
Source Control Tool CLI (Command Line Interface),
Passolo CLI plus Macro API,
FTP (Python? VB Script? PowerShell?...)

12. Case Study: Standardization & Break down
RnD <-> G11N:
L10N file exchange between RnD and G11N:
StarTeam, Subversion(SVN) – HP, 3rd Party, FTP,
Solution: SVN
G11N <-> Vendor:
L10N file exchange between G11N and Vendor:
, FTP(Vendor), SVN(HP),
Solution: FTP (HP)

13. Case Study: Standardization & Break down
BSM SW Translation Standard Process:
Further Break-Down Step:
SVN: check out, update, commit
Passolo: update, export/import bundle, generate target file.
FTP: initialize folder, upload, download
RnD
(SVN)
G11N
(Passolo)
Vendor
(FTP)

14. Case Study: Modularization and Bottom-up
SVN:
check out (“Sparse Check-out” PowerShell script) NEW!
update (“svn up” cmd)
commit (“svn ci” cmd)
Passolo:
update (Passolo cmd)
export/import bundle (Passolo Macro) NEW!
generate target file (Passolo cmd)
FTP:
initialize folder, upload, download (MS DOS ftp cmd)
Integration:
“One-Click” pre (post) PowerShell script NEW!

15. SVN “Sparse Check-out” “One-Click” Pre(Post) Bundle Process
Case Study: Live Demo
SVN “Sparse Check-out”
“One-Click” Pre(Post) Bundle Process

16. Case Study: Final Result Summary
Manual vs Automation:

17. Case Study: Final Results Summary
“Well Localized” Software!
Early Frequent Delivery
Early Defect Detecting
Early Defect Fixing
Early Defect Verification

18. Case Study: It’s not yet the end...
Daily Monitor the Volume Change
Auto-Translate and Auto-Check
Automatic Drop Notification
Status Reporting Dashboard
Script GUI Support for Easy Configuration …

19. Recap Mandatory under Agile Business consideration
Standard process and break-down step
Practical technology – not reinvent wheel
Bottom-to-top Modularization then Integration
Not “Silver Bullet”
Evolutionary

20. Q&A
Thank You !