Navigation:Michael Milutis |Home |Subscribe |About the Newsletter |Software Best Practices Events |ArchivesSoftware Best Practices InterviewsAbout our ContributorsSoftware Best Practices Reading ListSoftware Best Practices LinksAbout the InstituteAbout the SponsorSoftware ProcessesSoftware MetricsSoftware EstimationIT GovernanceChat LiveSoftware Best Practices Conferences - North AmericaSoftware Best Practices Conferences - EuropeSoftware Best Practices Conferences - Asia PacificSoftware Best Practices WorkshopsSoftware Best Practices Webinars
Home  -  Contact Us  -  Site Map

 Subscribe to RSS
 What is RSS?


The Software Best Practices Conferences

Implementations Workshop



Software ProcessesSoftware MetricsSoftware EstimationIT GovernanceCAI
Subscribe for Free!

All 2010 webinar registration links, topics, and descriptions now available for download!  

Interested in sponsoring or advertising?
Click HERE for details!

ITMPI on Twitter!

The ITMPI is now on Twitter!
Follow us at http://www.twitter.com/itmpi


 
Best Practices in Software Configuration Management
 
 
Quote of the Week
"Large skepticism leads to large understanding. Small skepticism leads to small understanding. No skepticism leads to no understanding."
- Xi Zhist
 
 
Software Configuration Management Audits

A software configuration audit can prove to be a valuable tool to ensure that processes and products are implemented in compliance with the requirements and objectives. In this article, Linda Westfall discusses three types of Software Configuration Audits; Functional Configuration Audit, Physical Configuration Audit and In-Process SCM Audits. Audits provide IT management with an objective verification that the SCM processes are compliant and that software products are being developed and implemented properly. (9 pages)

 
 

Risk-based software configuration control addresses the intricate balance between the developers need for flexibility and the need for stability in maintaining a consistent and standard set of processes. Linda Westfall examines risk-based software configuration control and the techniques that can be used to maintain this delicate balance between flexibility and stability. Selecting the appropriate technique to manage the risk between flexibility and stability should be evaluated on a project by project basis. The software configuration management process should include the documenting and communication of these decisions. (6 pages)

 
 
Bidirectional Requirements Traceability

Traceability is necessary to ensure that the right products are being developed at each phase of the development life cycle. In here article on Bidirectional Requirements Traceability, Linda Westfall explores three key questions; what is traceability, why is traceability a good practice and how is traceability performed. She concludes the article noting that all traceability implementation techniques require the involvement and commitment of a cross-functional team of participants who create and maintain linkages among the various work products. (4 pages)

 
 
Site of the Week
 
 

 

 

 

 

 

 

 



 
 
 
  



For more information on software best practices and IT management, please contact Michael Milutis, the IT Metrics and Productivity Journal Executive Director, at michael_milutis@compaid.com