In my company, I'm the only developer, but we plan on expanding the team by hiring a second programmer. I know there are a lot of implications to that (especially around source control). I've Googled a lot, but haven't found a good tutorial/article on how to grow the team from one to many developers.

Do you have any resources that we could make use of?

  • 4
    "especially around source control"? Even if you're the only dev on a project it still helps a lot to use source control!
    – Jeroen
    Commented Jul 19, 2012 at 7:53
  • @Jeroen but about source control, how do you ensure that the other developper doesn't overwrite your changes?
    – Mathieu
    Commented Jul 19, 2012 at 12:11
  • 2
    You don't need to. Source control keeps an entire history of all changes, and it's very easy to (a) review the other dev's changes and (b) revert or change his/her changes if needed. If you both change the same thing, the last person to "commit" his changes will be required to (and assisted in) resolving any conflicts. That's the beauty of source control!
    – Jeroen
    Commented Jul 19, 2012 at 12:43

2 Answers 2


You are probably looking for Onboarding process in software development companies.

In our company, there is a onboarding process and buddy assignment - to welcome new employee. It is very important to address any questions and provide new employee with company culture, regulation information.

It is also true that success of your onboarding process will be reflected on new employee's productivity and project success as well.

enter image description here

A sample checklist of onboarding steps are described below:

enter image description here

We have also SharePoint wiki page for each project, where new person may get info on project and related documentation.

To improve onboarding process the HR personal generally conducts a survey to get feedback from new employee.


I went into the same question like a year ago. My partner and I run a small consultant company and most of the code was written by myself (he is on the sales team). At some point, the number of projects increased and we noticed it was not only the code we have to care about; there are a lot of things you need to handle (documents, workflows, continous integration, testing, source control, etc) and the best choice you make here, the less headache will be on the near future.

I knew Jira from another job as being a very productive bug tracking system. It is scrum based, but even if scrum is not your thing, it is a great tool to work with. You keep track of every bug, task, new feature and such from one centralized web application and, it can be used either licensed or on a monthly payment basis. Big companies trust Jira for their development, so, why shouldn't small ones do? Taking into account the cost of Jira on demand is now less than an average development cost. For me, this was a no-brainer.

Jira comes with lots of plugins, some are cheap, some are not, some are given at no cost at all. One of those plugings we are using is Fisheye, which is a source control repository compatible with SVN. As of now, we store on Fisheye 7 projects with many thousands of line code. Never had an issue with the Atlassian guys, and their support (jira based of course) totally rocks.

Sharepoint is a great tool as well, but it is not focused for development. It is a CMS, easy to use, but for different porpouses.

Give Jira a try, there are free trials, I'm sure it will fit your needs. Cheers.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.