5 mistakes of remote work

595 views

Published on

Published in: Technology, Business
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
595
On SlideShare
0
From Embeds
0
Number of Embeds
185
Actions
Shares
0
Downloads
5
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

5 mistakes of remote work

  1. 1. Top 5mistakes while choosing an external team Andrey Stetsenko Recruting | Relocation | Remote
  2. 2. Dnepropetrovsk, Ukraine CEO at Relocateme.eu Expert at IT Recruiting | Relocation | Remote solutions Wrote a code on Delphi & VB in the early 2003 A dreamer Andrey Stetsenko
  3. 3. “Big business doesn’t do it, so why should we?” by 37 signals
  4. 4. 3 Reasons to go “Remote”
  5. 5. Expertise
  6. 6. Availability
  7. 7. Scalability
  8. 8. Cost-reducing I didn’t mention it...did I?
  9. 9. Cost-reducing I didn’t mention it...did I? Hourly rate AdministrationOffice
  10. 10. Top 5mistakes while choosing an external team
  11. 11. Being afraid of going “remote” Mistake #0
  12. 12. Mistake #0 Being afraid of going “remote” Don’t be afraid. Convert your bad experience from the past into the lessons you’ve learnt. Advice
  13. 13. Big players make a good service for you Mistake #1
  14. 14. Big players make a good service for youMistake #1 Choose small to mid providers. It’s better to be a “top” client than “one of dozens”. Advice
  15. 15. Mistake #2 Cost-oriented search
  16. 16. Mistake #2 Cost-oriented search A miser pays twice. Seek for a solution to add value to your product. Look for partners, not “coding” hands. Advice
  17. 17. Mistake #3 “Fixed price” is the only way to work
  18. 18. Mistake #3 “Fixed price” is the only way to work Use “Time & Material” or “Cost+” models. By doing so, you’ll attract way more qualified experts. Advice
  19. 19. Mistake #4 Hiring teams with “really sweet” estimates
  20. 20. Mistake #4 Hiring teams with “really sweet” estimates Don’t believe in miracles. Always make your own estimation and consider both, good and bad scenario. Advice
  21. 21. Mistake #5 Neglecting references
  22. 22. Mistake #5 Neglecting references Always check as many references as it’s possible. That’s the only way to identify the “karma” of dev team. Advice
  23. 23. Thank you for your time!
  24. 24. Blog: Skype: Email: Website: stetsenko.me indigo-it andrey@stetsenko.me www.relocateme.eu Andrey Stetsenko

×