I am currently a graduate student, but I was in the industry for a few years before going back to school.
I am in a class which is working on 4 teams of very ambitious projects. As a result of being in the industry, I have many "software engineering" experiences which are lacking of my fellow teammates (they are first using SVN for this semester). They are all very good programmers; But they do not have much experience in making "real stuff".
Since I had a solid view for a project, and my colleagues did not, my idea is that we will spend it on the semester to work on it, as a result of my experience, besides The fact is that I have a somewhat strong personality, I have become a D-Facto Team Lead - established weekly meeting time, assigned to initial tasks, etc.
I want to avoid being so strong with my thoughts that what we should do and how we should do this, so that my colleagues believe that they have no say and They have disappeared and separated.
Here's a question:
By implementing basic best practices (version control, milestones, etc.) and implementing a consistent project approach, your team How can I keep a disciplined, but talented programmer? ?
Edit: Thanks to all those who have answered so far, I think I have emphasized the "software engineering" aspect of things; I am also considering the idea of how to encourage members of my team to contribute to the design, and feel ownership in the project, which for some time " The Square Cog (and friends)
I found That's not the best method to do anything with code: Team Lunch.
Get together in the informal setting, where you get your problems, worries, Talk, etc., it helps team unity in a way that is very less.
As its real code side, to work inside those frameworks which Do the work you want, if you want them to use the ticket, then do for them by the real management side - tell them what the ticket is and you actually manage these things. The move seems to do. Is such that it takes a lot of time, but overall it is less than the cost of communication and coordination is very fast payment.
For version control, tell them why they really get the benefit. Programmers raise ideas and go with them, when they see that they really help them instead of being beaten.