Introduce branching to existing project best practice for TFS 2013 -

we have tfs 2013, team project working don't have branches, plain folder structure various solutions in them.

with goal introduce release management, intention create several branche, e.g. development/main/releases

as told cannot 'disturb' project team developers day day work since there other projects being worked on, question, best practice this? create separate team project? how can adopt branching practice without asking developers.

please point direction or share thought on this, appreciated!!

unfortunately you'll have "disturb" development team. have 2 options. 1. come process in isolation , disturb them when goes live. 2. collaborate them on process , work meet requirements. (being able release code production key requirement project, sadly it's obvious never gets added backlog / project plan , treated afterthought)

i recommend option 2. without collaboration you're going end causing resentment you're imposing on devs , they'll fight tooth , nail. without development team being involved you'll miss important make process brittle , difficult maintain.

you'll need buy in developers implement branching strategy have significant impact on them, need understand why you're doing , benefits are, both them , business. don't have of work, need know you're doing , why, need know when changes coming can plan change.

firstly need real alm rangers version control guidance.

secondly need developers read well. responsible maintaining code , merging between branches. need know when , need check in various changes (such hotfixes), , process should follow when code ready release.

finally, regarding question branches should located. better locate branches in same team project rather having dev branch in separate team project.