Project success: It all starts with configuration management

QA and the configuration management (CM) team must be involved in each project from the very beginning. This allows QA to identify and quantify problems sooner. And it allows the CM team to create a baseline for the project and a repository for all documentation and deliverables, including project plans, project meeting minutes, reviews, walkthroughs and models.

By putting all documents and deliverables under CM, developers, QA and project manages always know that they are looking at the latest and greatest of whatever source they check out of the repository.

    Requires Free Membership to View

This was first published in August 2007

There are Comments. Add yours.

TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.