Best Practices for Software Projects: An Introduction to Task-based Configuration Management
Friday, 22nd September 2006
Published by:  Software development teams are under pressure: complexity is increasing; time-to-market is critical; quality requirements are high; and developers are often distributed. In the course of developing and maintaining software, teams will typically create or modify a large number of objects like source code, images, documents and binaries. A project might include hundreds of changes a day to produce a final release. Unfortunately, a single mistake in a change to a line of code can bring the whole system down, making change tracking and control critical to software development. |
|
|
||||||
Related White Papers:
» 11 Myths About Microsoft Exchange Disaster Recovery
» 5 Phases of OEM Report Development
» 5 High Impact Fail Points, and How to Avoid Them
» .Net Insight eNewsletter
» 5 High Impact Fail Points, and How to Avoid Them
» Introduction to Free Software
