Not only having an in-house dev team is more natural but also much safer for your organisation. But what to do if, for certain reasons, you have to outsource the Software Development - the heart of nowadays organisations?

1. How to Survive
Outsourcing?

2. Piotr Majchrzak.
Amateur Radio Operator by heart>
CEO by passion
@piotrmajchrzak

3. .I like building antennas.

4. .…and companies.

5. Founder & CEO
Co-Founder

6. .Outsourcing?.

7. .“Software is eating the world.”.
.Marc Andreessen.
Why?

8. And...
A severe shortage of talent.
Rising costs in all areas.
A global price war.
The rise of a freelancer economy.

9. Outsourcing sux?
No, it’s just hard
and nobody will tell you that.

10. How to survive, short answer:
Do not outsource.
(If you can).

11. Outsourcing->Insourcing->
YOUR Remote
Dev Team
Change the mindset

12. solve 7 problems
And then

13. Second thing: solve 7 problems
#1: Nobody tells how to work
with remote Dev Teams

14. Best practice:
Stacey matrix
● Pros who mastered technology
● Requirements understood along
the way (lots of F2F meetings)
● “big enough to scale but
small enough to care”

15. Second thing: solve 7 problems
#2: Wrong perception
of cooperation

16. ● Partnership not client-supplier
relation
● Build trust
● Long term
● Best if your Remote Dev Team
is pre-assembled
Best practice:

17. Second thing: solve 7 problems
#3: Organisation culture
mismatch & cultural gap

18. TIP

19. Second thing: solve 7 problems
#4: Bad communication &
no transparency

20. Second thing: solve 7 problems
#5: No clear mutual goals
and processes adjusted
improperly

21. Second thing: solve 7 problems
#6: Unreliability

22. Second thing: solve 7 problems
#7: Cultivate relation
● Our best practices: Every quarter/half year a general matters about
processes and people
● Team’s 1-3m visits; lots of video conferencing

23. Like antenna is a tool for
communication, outsourcing
is a way to do software dev.

24. Do not waste your life at surviving
at work while you can do amazing
things (with Remote Dev Teams)!

25. Thank you!
Piotr Majchrzak
piotr@xsolve.pl
@piotrmajchrzak
www.xsolve.pl