A copy of this work was available on the public web and has been preserved in the Wayback Machine. The capture dates from 2004; you can also visit <a rel="external noopener" href="http://sern.cpsc.ucalgary.ca:80/~milos/papers/2002/holz_maurer.pdf">the original URL</a>. The file type is <code>application/pdf</code>.
<i title="Springer Berlin Heidelberg">
<a target="_blank" rel="noopener" href="https://fatcat.wiki/container/2w3awgokqne6te4nvlofavy5a4" style="color: black;">Lecture Notes in Computer Science</a>
Agile Software Development has put a new focus on the question of how to share knowledge among members of software development teams. In contrast to heavy-weight, document-centric approaches, agile approaches rely on face-to-face communication for knowledge transfer. Pure face-to-face communication is not feasible when applying agile processes in a virtual team setting. In this paper, we argue that the right approach for virtual software development teams using agile methods lies between a<span class="external-identifiers"> <a target="_blank" rel="external noopener noreferrer" href="https://doi.org/10.1007/978-3-540-40052-3_7">doi:10.1007/978-3-540-40052-3_7</a> <a target="_blank" rel="external noopener" href="https://fatcat.wiki/release/3jczhzae7raqlhgahb4hn2h2vu">fatcat:3jczhzae7raqlhgahb4hn2h2vu</a> </span>
more »... al "none but source code" standpoint, and the multitude of documents proposed by heavy-weight development standards. This paper introduces work on developing a system for the task-based capture and pro-active distribution of recurrent information needs that typically arise for developers, as well as potential ways to satisfy these information needs. Our approach facilitates an incremental organizational learning process to capture and maintain knowledge on what documentation/information is actually needed, such that documentation is created on an "as needed" basis. Keywords: task-oriented knowledge management support, virtual agile teams 1 In fact, the knowledge base maintenance problem was never solved in the 1980'ies for expert system approaches, and prevented them from wide-spread adaptation in industry. 2 While pair programming might increase the chances that at least one of the two developers is aware of relevant information, it does not solve the problem in principle.
<a target="_blank" rel="noopener" href="https://web.archive.org/web/20040228194047/http://sern.cpsc.ucalgary.ca:80/~milos/papers/2002/holz_maurer.pdf" title="fulltext PDF download" data-goatcounter-click="serp-fulltext" data-goatcounter-title="serp-fulltext"> <button class="ui simple right pointing dropdown compact black labeled icon button serp-button"> <i class="icon ia-icon"></i> Web Archive [PDF] <div class="menu fulltext-thumbnail"> <img src="https://blobs.fatcat.wiki/thumbnail/pdf/d9/55/d955011c9f1118320999b564c76f209a12510465.180px.jpg" alt="fulltext thumbnail" loading="lazy"> </div> </button> </a> <a target="_blank" rel="external noopener noreferrer" href="https://doi.org/10.1007/978-3-540-40052-3_7"> <button class="ui left aligned compact blue labeled icon button serp-button"> <i class="external alternate icon"></i> springer.com </button> </a>