> I don't think it's possible to have an actual allergy to git, so some training in that area would probably help their productivity. I was going to go back an

> I don't think it's possible to have an actual allergy to git, so some training in that area would probably help their productivity. I was going to go back and add "does he need any training" to my original comment then life got in the way and I promptly forgot! Absolutely do run training; could for example set up a Pluralsight account, run through modules on GIT and any other stacks that are needed. If someone doesn't want to use version control in this day and age then I'd have to agree that'd be my number one priority to get fixed. Understanding feature branches would be a very powerful change. Not sure exactly how applicable this is to your situation but on a general level I'd recommend making them as atomic / small as possible as a way of starting. I.e. by reducing the scope of an issue down to the MVP, then it becomes easier to just get that done - add additional features/requirements as following issues. And then get on to pull requests ASAP so that you can preferably sit together and review / discuss the changes. This would reduce the feedback cycle down to maybe a couple of days, which would greatly help the pace as well. Good luck.