Five keys to project knowledge sharing

Stacie Petter, Lars Mathiassen, Vijay Vaishnavi

Research output: Contribution to journalReview articlepeer-review

12 Scopus citations


Some of the answers that can help guide tools selection for knowledge sharing across software projects are discussed. Selecting a knowledge-sharing tool based on convenience could be a formula for using valuable money, time, and resources implementing a tool that ultimately is not used and becomes viewed as a source of frustration within your organization. First, to help understand the intent of knowledge sharing across projects, one should ask why is knowledge sharing suggested and need to determine if the knowledge will be used for developing new knowledge. The next question is whether the software manager will focus on learning know-why, which is the rationale behind the procedures and practices. The final question is what is the time focus of the knowledge to be shared? A combination of tools is necessary to answer these questions and it might be feasible to redefine some tools to provide additional functionality or to answer appropriately.

Original languageEnglish (US)
Pages (from-to)42-46
Number of pages5
JournalIT Professional
Issue number3
StatePublished - May 2007
Externally publishedYes

ASJC Scopus subject areas

  • Software
  • Hardware and Architecture
  • Computer Science Applications


Dive into the research topics of 'Five keys to project knowledge sharing'. Together they form a unique fingerprint.

Cite this