Defining continuous planning through a multiple-case study

Tanja Suomalainen

    Research output: Chapter in Book/Report/Conference proceedingConference article in proceedingsScientificpeer-review

    5 Citations (Scopus)


    New and innovative approaches that support continuous development and planning throughout organisations are needed. Continuity is required in all levels of an organisation, from business strategy and planning to software development and operational deployment, as well as between these levels. Continuous planning is one of these activities. However, continuous planning is not commonly adopted and applied throughout organisations and currently involves only a certain level of planning, e.g., release planning. Based on the current literature, continuous planning is a relatively new and not yet fully studied field of research. To augment the knowledge relating to continuous planning, this paper presents a multiple-case study in which the various levels of planning, along with their timeframes, are explored. The research results point out the key activities, as well as the bottlenecks, of continuous planning.
    Original languageEnglish
    Title of host publicationProduct-Focused Software Process Improvement
    ISBN (Electronic)978-3-319-26844-6
    ISBN (Print)978-3-319-26843-9
    Publication statusPublished - 5 Jan 2016
    MoE publication typeA4 Article in a conference publication
    Event16th International Conference on Product-Focused Software Process Improvement, PROFES 2015 - Bolzano, Italy
    Duration: 2 Dec 20154 Dec 2015
    Conference number: 16

    Publication series

    SeriesLecture Notes in Computer Science


    Conference16th International Conference on Product-Focused Software Process Improvement, PROFES 2015
    Abbreviated titlePROFES 2015


    • continuous planning
    • continuous deployment
    • levels of planning


    Dive into the research topics of 'Defining continuous planning through a multiple-case study'. Together they form a unique fingerprint.

    Cite this