Lifecycle management in government-driven open source projects: Practical framework

Katja Henttonen, Jukka Kääriäinen, Jani Kylmäaho

    Research output: Contribution to journalArticleScientificpeer-review

    2 Citations (Scopus)


    In many parts of the world, public sector organizations are increasingly interested in collaborating across organizational (and even national) boundaries to develop software solutions under an open licence. However, without sound lifecycle management practices, the full benefits of open collaboration are not achieved and projects fail to achieve sustained success. This paper introduces a lifecycle management model and framework for government-driven open-source projects and reports about its use in a real-life case study. Our focus is on lifecycle management activities which take place between deployment and end-of-life. The framework was developed iteratively through a series of focus group discussions with representatives of public sector organizations. After the framework had been taken into use in our real-life case project, individual qualitative interviews were conducted to collect experiences on its benefits and weaknesses. According to the initial evidence, the deployment of the framework seems to have brought concrete benefits to the project, e.g. by contributing positively to community growth, software quality and inter-organizational learning.
    Original languageEnglish
    Pages (from-to)23-41
    JournalInternational Journal of Information Systems and Project Management
    Issue number3
    Publication statusPublished - 1 Jan 2017
    MoE publication typeA1 Journal article-refereed


    • public information systems
    • open source
    • open-source software
    • free software
    • e-government
    • public sector
    • software
    • lifecycle management
    • software evolution
    • information systems


    Dive into the research topics of 'Lifecycle management in government-driven open source projects: Practical framework'. Together they form a unique fingerprint.

    Cite this