3 ms·
Re #2 - fully outsourcing development. I've seen this done successfully and as a matter of fact I was on the team that built the first MVP. I'm sure it's the ex
by jayroh 11y ago
Re #2 - fully outsourcing development. I've seen this done successfully and as a matter of fact I was on the team that built the first MVP. I'm sure it's the exception and not the rule but it can be done if the team that's brought in is super professional and talented. (We were). There are some benefits to this route if done correctly
1. The code left for the eventual, internal, team is pristine, well written, scalable and easy to jump into.
2. Well defined processes are in place.
3. Our company helped find, introduce, and often interview the new employees for our client.
It's worked out well several times but it's certainly not cheap. You get what you pay for.
- jacquesm 11y agoVery neat, you should definitely do a write-up on that, it is super interesting that you found a way to do this.
- jayroh 11y agoA former coworker did a write-up and an interview with one of his former clients and I think it sheds a lot of light on how this can work - https://robots.thoughtbot.com/a-client-project-two-years-later https://robots.thoughtbot.com/a-client-project-two-years-lat...
- jacquesm 11y agoI've been reading that for an hour or so now, you could easily get another 'Soul of a new machine' out of your project. Maybe not as dramatic but that project could easily serve as a benchmark of outsourcing done right. I'm going to sleep now and I'll re-read it tomorrow. Thank you very much for that link.
- jacquesm 11y agoAre you available for some questions? If so could you shoot me an email? (jacques@mattheij.com)