Five keys to project knowledge sharing

Stacie Petter, Lars Mathiassen, Vijay Vaishnavi

Research output: Contribution to journalReview article

12 Citations (Scopus)

Abstract

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
Volume9
Issue number3
DOIs
StatePublished - May 1 2007

Fingerprint

Managers

ASJC Scopus subject areas

  • Software
  • Hardware and Architecture
  • Computer Science Applications

Cite this

Petter, S., Mathiassen, L., & Vaishnavi, V. (2007). Five keys to project knowledge sharing. IT Professional, 9(3), 42-46. https://doi.org/10.1109/MITP.2007.44

Five keys to project knowledge sharing. / Petter, Stacie; Mathiassen, Lars; Vaishnavi, Vijay.

In: IT Professional, Vol. 9, No. 3, 01.05.2007, p. 42-46.

Research output: Contribution to journalReview article

Petter, S, Mathiassen, L & Vaishnavi, V 2007, 'Five keys to project knowledge sharing', IT Professional, vol. 9, no. 3, pp. 42-46. https://doi.org/10.1109/MITP.2007.44
Petter S, Mathiassen L, Vaishnavi V. Five keys to project knowledge sharing. IT Professional. 2007 May 1;9(3):42-46. https://doi.org/10.1109/MITP.2007.44
Petter, Stacie ; Mathiassen, Lars ; Vaishnavi, Vijay. / Five keys to project knowledge sharing. In: IT Professional. 2007 ; Vol. 9, No. 3. pp. 42-46.
@article{295bc565c2264c57abf8b5d23f03e4dd,
title = "Five keys to project knowledge sharing",
abstract = "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.",
author = "Stacie Petter and Lars Mathiassen and Vijay Vaishnavi",
year = "2007",
month = "5",
day = "1",
doi = "10.1109/MITP.2007.44",
language = "English (US)",
volume = "9",
pages = "42--46",
journal = "IT Professional",
issn = "1520-9202",
publisher = "IEEE Computer Society",
number = "3",

}

TY - JOUR

T1 - Five keys to project knowledge sharing

AU - Petter, Stacie

AU - Mathiassen, Lars

AU - Vaishnavi, Vijay

PY - 2007/5/1

Y1 - 2007/5/1

N2 - 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.

AB - 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.

UR - http://www.scopus.com/inward/record.url?scp=34249817608&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=34249817608&partnerID=8YFLogxK

U2 - 10.1109/MITP.2007.44

DO - 10.1109/MITP.2007.44

M3 - Review article

AN - SCOPUS:34249817608

VL - 9

SP - 42

EP - 46

JO - IT Professional

JF - IT Professional

SN - 1520-9202

IS - 3

ER -