Lessons learned outsourcing software development in Ukraine

  • 1,691 views
Uploaded on

Short extract of some of my experiences building software and outsourcing in Ukraine.

Short extract of some of my experiences building software and outsourcing in Ukraine.

More in: Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
1,691
On Slideshare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
0
Comments
0
Likes
1

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n

Transcript

  • 1. OUTSOURCING Lessons learned outsourcing software development in UkraineNicolai Kollner - kollner@gmail.com http://twitter.com/kollner http://dk.linkedin.com/in/nicolaikollner
  • 2. WHY OUTSOURCING?• Access to the right talent and competencies.• Improve competitiveness.• Flexibility when scaling up and down.• Have presence in the region.
  • 3. ORGANIZATION• Integrated organization covering on and offshore.• Cross functional teams.• Daily meetings: Scrum, planning, retrospectives...• Team members can be cross location, but prefer same location.• Typically the Product Owner is off site.• Functional team leads can help scale.
  • 4. RECRUITMENT• Recruiting and retaining top talent is a critical component for success.• In a body-shop setup the vendor handles the screening process of individual candidates.• Evaluating technical skills is done with the vendor and technical leads. Can include interview with whiteboard coding, assignments and other forms of testing.• Personal skills are just as important. Looking for people that can communicate, work in a team and have passion for what they do.• Recruiting for top 5%? Be present locally. Network and be a part of the local community.
  • 5. INFRASTRUCTURE• Video conferencing everywhere.• Wiki’s for knowledge sharing.• Lifecycle management system (TFS, Jira).• Source control.• Dedicated setup for daily scrum.
  • 6. CULTURE Denmark Russia Poland100 75 50 25 0 Power Distance Individualism Masculinity Uncertainty Avoidance Source: http://geert-hofstede.com
  • 7. DO’S AND DON’TS• Open and honest communication. • Don’t let anyone become bystanders.• Avoid the “them and us” mentality • Clear vision and goal set the direction.• Go and see for yourself. • Work toward self-organizing teams.• Recruiting is hard. Get it right. • Prefer discussions over handovers and formal documentation.• Have a global process and organization. • Have the tools in place.• Communicate in one language.
  • 8. ?