Use a best-practice Configuration Management process |
 |
 |
 |
| Written by Graham Stoney | |||
|
The more people you have working on a code base, the more important it is that you have a process in place which has sensible policies. The best development process is lightweight and actively assists the developers to work as a team and get their job done; poor processes on the other hand get in the way of developers work or impose unnecessary bureaucratic overheads. The closest description I've seen to my ideal development process is an excellent white paper from Perforce, called High-level Best Practices in Software Configuration Management. You also need to have tool support for the process that you want to use. It's pointless choosing a process for which no tool exists, and there are plenty of tools out there that support best-practise development models, like concurrent development and issue-driven workflows. Look at which tools are out there, and pick the one that best supports the model you want to use. Social Bookmark this page:         
|