Upstream, Downstream

16
Upstream, Downstream Gregor Kneitz Hajnalka Sarvari

description

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 - PowerPoint PPT Presentation

Transcript of Upstream, Downstream

Page 1: Upstream, Downstream

Upstream, DownstreamGregor KneitzHajnalka Sarvari

Page 2: Upstream, Downstream

In this session• Upstream & Downstream Defined• Challenges• Existing Models• Case Studies• Conclusion

Page 3: Upstream, Downstream

Upstream, Downstream

UpstreamEngagement with Dev/Test/PM• Globalization• Localizability

DownstreamLocalizing resources and integrating intoproduct

HandoffT/E/PHand-backBuild, test

ConsultingCriteriaTraining

Ready for Loc

Page 4: Upstream, Downstream

Challenges

Different RolesPersonality typesSkill sets

No perfect StructureSeveral models

Upstream Impacts DownstreamHard to quantify RoI

Page 5: Upstream, Downstream

Model Overview: Separation

Cons:• Conflicting

interests• Doesn’t

scale

Pros:• Focus• Technical

depth

R&D

Product Development

Development/Test

World Readiness

Central Functions

Localization

Page 6: Upstream, Downstream

Model Overview: Integration

Cons:• Loc focus• Roles

merge

Pros:• Loc focus• WR team

with Loc expertise

Central Functions

International

Business Developme

ntLocalizatio

n

World Readiness

Testing

Page 7: Upstream, Downstream

Model Overview: Collaboration

Cons:• Need for

constant sync

• Gray areas

Pros:• Proximity• Central

WR team• BalanceCentral

Services

World Readiness

Localization

Release Manageme

nt…

Page 8: Upstream, Downstream

Case Study: Localizing SQL ServerLocalization strategy definedExtent of LocalizationNew languages – BiDi

Processes definedFundamental criteria establishedLocalization plan

TrainingsBrownbags for the wider organizationKickoff for suppliers

Planning

Page 9: Upstream, Downstream

Case Study: Localizing SQL ServerDistinct rolesWR: Consulting – Office hoursWR: Improvement transitionsLoc: File processing, coordinating with suppliers, testLoc: Status tracking and reporting

OverlapLocalizability and globalization issuesSchedulingShiproom

Execution

Page 10: Upstream, Downstream

The Outcome:On time sim-ship

Page 11: Upstream, Downstream

Case Study: Bug Analysis

Why?Need data to drive changeAssess quality and trends

What?Identify sub-categoriesReview and assignAnalyze ResultClear picture and focus areasPlan for vNext changes

Page 12: Upstream, Downstream

Conclusion

Quality, Agility and EfficiencyBuilding on people‘s strengths

Clear charter and prioritiesAchievements easily measurable

„One Team“Job satisfaction

Page 13: Upstream, Downstream

The Evidence

Word count

UI Total cost

26%240%

13%

Last three versionsSQL 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

Page 14: Upstream, Downstream

Collaboration: Challanging to manage, but well worth it

Page 15: Upstream, Downstream

?

Page 16: Upstream, Downstream

감사합니다

Спасибо

Thank you!Merci

Grazie

DankeGraciasObrigado

ありがとう

谢谢

謝謝 Köszönjük