Knowledge-related challenges and solutions in GSD

Päivi Parviainen (Corresponding Author), Maarit Tihinen

    Research output: Contribution to journalArticleScientificpeer-review

    3 Citations (Scopus)

    Abstract

    A number knowledge-related challenges may complicate the work in global software development (GSD) projects. In practice, even a small amount of missing knowledge may cause an activity to fail to create and transfer information which is critical to later functions, causing these later functions to fail. Thus, knowledge engineering holds a central role in order to succeed with globally distributed product development. Furthermore, examining the challenges faced in GSD from a cognitive perspective will help to find solutions that take into account the knowledge needs of different stakeholders in GSD and thus help to establish conditions for successful GSD projects. In this paper, we will discuss these challenges and solutions based on an extensive literature study and practical experience gained in several international projects over the last decade. Altogether, over 50 case studies were analysed. We analysed the challenges identified in the cases from a cognitive perspective for bridging and avoiding the knowledge gaps and, based on this analysis, we will present example solutions to address the challenges during the GSD projects. We will conclude that through understanding both the nature of GSD and the KE challenges in depth, it will be possible for organizations to make their distributed operations successful
    Original languageEnglish
    Pages (from-to)253-266
    Number of pages14
    JournalExpert Systems
    Volume31
    Issue number3
    DOIs
    Publication statusPublished - 2014
    MoE publication typeA1 Journal article-refereed

    Keywords

    • Global software development
    • industrial challenges
    • knowledge engineering

    Fingerprint Dive into the research topics of 'Knowledge-related challenges and solutions in GSD'. Together they form a unique fingerprint.

    Cite this