Defect Bash - Literature Review <s> Benefit <s> Presents the seven basic steps of opportunistic software process evolution. (1) Notice problems in products or outcomes. (2) Choose an important or chronic problem and look for a way to solve it, in whole or in part. (3) Conceive of a new, borrowed or modified process that could solve the problem at an acceptable cost and in an acceptable time frame. (4) Try the new process on a real project. (5) Adjust the process in light of experience and in light of the new problems that were created by the process. (6) If the solution is worth perpetuating, look for a way to make it more efficient or durable by adding infrastructure (such as documentation, training or tool support). Otherwise, try to understand why it doesn't seem to work. (7) Return to step 1. Pay attention to projects on the scale of hours, cubicles, people and episodes. In complex cognitive processes like software development, if process evolution is foiled on the micro scale, it will be foiled utterly. <s> BIB001 </s> Defect Bash - Literature Review <s> Benefit <s> Every bug has a story behind it. The people that discover and resolve it need to coordinate, to get information from documents, tools, or other people, and to navigate through issues of accountability, ownership, and organizational structure. This paper reports on a field study of coordination activities around bug fixing that used a combination of case study research and a survey of software professionals. Results show that the histories of even simple bugs are strongly dependent on social, organizational, and technical knowledge that cannot be solely extracted through automation of electronic repositories, and that such automation provides incomplete and often erroneous accounts of coordination. The paper uses rich bug histories and survey results to identify common bug fixing coordination patterns and to provide implications for tool designers and researchers of coordination in software development. <s> BIB002 </s> Defect Bash - Literature Review <s> Benefit <s> While leadership dominates the attention of many, it is management that drives the work at hand. Julian Birkinshaw and Jules Goddard suggest that you reconsider the management model you practice daily to see if it's really working inside your company. <s> BIB003 </s> Defect Bash - Literature Review <s> Benefit <s> We have used CI (Continuous Integration) and various software testing techniques to achieve a robust C4ISR (Command, Control, Communications, Computers, Intelligence, Surveillance, and Reconnaissance) multi-platform system. Because of rapid changes in the C4ISR domain and in the software technology, frequent critical design adjustments and in turn vast code modifications or additions become inevitable. Defect fixes might also incur code changes. These unavoidable code modifications may put a big risk in the reliability of a mission critical system. Also, in order to stay competitive in the C4ISR market, a company must make recurring releases without sacrificing quality. We have designed and implemented an XML driven automated test framework that enabled us developing numerous high quality tests rapidly. While using CI with automated software test techniques, we have aimed at speeding up the delivery of high quality and robust software by decreasing integration procedure, which is one of the main bottleneck points in the industry. This work describes how we have used CI and software test techniques in a large-scaled, multi-platform, multi-language, distributed C4ISR project and what the benefits of such a system are. <s> BIB004
References mentioning the benefit Finding many defects, bring out both functional and non-functional defects, also shortening the life cycle of the bugs Anonymous 1, 2010; Anonymous 2, 2010; Anonymous 3, 2011; BIB002 Crudden and Lawson, 2011;   Karla, 2007;    QTP, 2012;     The competitive instinct of participants are stimulated and good for team building  BIB003 Wong, 2011; BIB004 Saving money (no need to hire group externals) Crudden and Lawson, 2011 Help in rapid evolution of test scripts BIB001 Acting as acceptance testing and usability testing  . However, this limitation can be overcome by careful planning of defect bash.