Search

The article discusses the potential for cognitive bias to appear in the development of computer software, examining the use of traceability to eradicate the effect of cognitive bias while individuals perform change to design artifacts. Software developers may employ heuristics that are informed by cognitive biases when changing software artifacts, the article states. Other topics include the use of the cognitive aid traceability, simplifying complex inference tasks, the use of anchoring and adjustment, and peoples' initial estimates about a problem.

The article discusses the use of software configuration management to improve the change-management process. According to the author, one of the most common reasons for the failure of software development projects is the continuous evolution of software caused by volatility in customer requirements. Sources of this volatility are diverse, ranging from changes in technology, end-user needs, and dynamic market pressures. The author examines the ways software configuration management can mitigate problems related to these failures. INSET: HOW THE STUDY WAS CONDUCTED.

The article presents a case study of three U.S.-based companies that develop computer software in cooperation with partners in India. The authors discuss the communications, management, and organizational methods used by the companies in the case study. According to the authors, agile software development methods create communications challenges for work teams that are spread out across continents and oceans. One of the companies adopted a formal communications structure; they appointed an individual at each work site to be the "point person" for project communication. All of the companies found that "real-time" communication was important; as a result, onshore and offshore workgroups adjusted their hours to facilitate communication.