upstream, downstream

Post on 23-Feb-2016

197 Views

Category:

Documents

0 Downloads

Preview:

Click to see full reader

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

Upstream, DownstreamGregor KneitzHajnalka Sarvari

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

Upstream, Downstream

UpstreamEngagement with Dev/Test/PM• Globalization• Localizability

DownstreamLocalizing resources and integrating intoproduct

HandoffT/E/PHand-backBuild, test

ConsultingCriteriaTraining

Ready for Loc

Challenges

Different RolesPersonality typesSkill sets

No perfect StructureSeveral models

Upstream Impacts DownstreamHard to quantify RoI

Model Overview: Separation

Cons:• Conflicting

interests• Doesn’t

scale

Pros:• Focus• Technical

depth

R&D

Product Development

Development/Test

World Readiness

Central Functions

Localization

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

Model Overview: Collaboration

Cons:• Need for

constant sync

• Gray areas

Pros:• Proximity• Central

WR team• BalanceCentral

Services

World Readiness

Localization

Release Manageme

nt…

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

Processes definedFundamental criteria establishedLocalization plan

TrainingsBrownbags for the wider organizationKickoff for suppliers

Planning

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

The Outcome:On time sim-ship

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

Conclusion

Quality, Agility and EfficiencyBuilding on people‘s strengths

Clear charter and prioritiesAchievements easily measurable

„One Team“Job satisfaction

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

Collaboration: Challanging to manage, but well worth it

?

감사합니다

Спасибо

Thank you!Merci

Grazie

DankeGraciasObrigado

ありがとう

谢谢

謝謝 Köszönjük

top related