190 likes | 847 Views
Upstream, Downstream. Gregor Kneitz Hajnalka Sarvari. In this session. Upstream & Downstream Defined Challenges Existing Models Case Studies Conclusion. Upstream, Downstream. Upstream Engagement with Dev /Test/PM Globalization Localizability Downstream
E N D
Upstream, Downstream Gregor Kneitz Hajnalka Sarvari
In this session • Upstream & Downstream Defined • Challenges • Existing Models • Case Studies • Conclusion
Upstream, Downstream Upstream Engagement with Dev/Test/PM Globalization Localizability Downstream Localizing resources and integrating into product Consulting Criteria Training Ready for Loc Handoff T/E/P Hand-back Build, test
Challenges Different Roles Personality types Skill sets No perfect Structure Several models Upstream Impacts Downstream Hard to quantify RoI
Model Overview: Separation • Pros: • Focus • Technical depth • Cons: • Conflicting interests • Doesn’t scale
Model Overview: Integration • Pros: • Loc focus • WR team with Loc expertise • Cons: • Loc focus • Roles merge
Model Overview: Collaboration • Pros: • Proximity • Central WR team • Balance • Cons: • Need for constant sync • Gray areas
Case Study: Localizing SQL Server Planning Localization strategy defined Extent of Localization New languages – BiDi Processes defined Fundamental criteria established Localization plan Trainings Brownbagsfor the wider organization Kickoff for suppliers
Case Study: Localizing SQL Server Execution Distinct roles WR: Consulting – Office hours WR: Improvement transitions Loc: File processing, coordinating with suppliers, test Loc: Status tracking and reporting Overlap Localizability and globalization issues Scheduling Shiproom
The Outcome: On time sim-ship
Case Study: Bug Analysis Why? Need data to drive change Assess quality and trends What? Identify sub-categories Review and assign Analyze Result Clear picture and focus areas Plan for vNext changes
Conclusion Quality, Agility and Efficiency Building on people‘s strengths Clear charter and priorities Achievements easily measurable „One Team“ Job satisfaction
The Evidence Last three versions SQL 2012 with 6 FTE • 2 IPM • 1 Software engineer • 1 Content engineer • 2 Test Healthy team • High work health index • 1 attrition over ~2 years Word count Total cost 13% 26% UI 240%
Спасибо 谢谢 Merci Grazie Thank you! ありがとう Danke Gracias Köszönjük 謝謝 감사합니다 Obrigado