Continuous strategy process in the context of agile and lean software development

Tanja Suomalainen, Jenni Myllykoski

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

2 Citations (Scopus)


This extended abstract introduces an ongoing research which elaborates the concept of continuous strategy with an aim to better address the contemporary challenges of strategy process within the field of software development. Theoretically the research draws on the strategy process and practice -literature and on the literature of agile and lean software development when conceptualizing continuous strategy. Empirically the research examines the emerging challenges in software companies' strategy process when they are pursuing continuous practices in software development. The tentative analysis revealed that the practices that stem from the more traditional, structured strategy process are not compatible with the more "continuous planning"-oriented organisational practices. Thus, there seems to be pressure for developing more continuous strategy process and practices. Furthermore, in other organisational processes, especially in team level, the practices relating to continuity are more successfully applied, than in strategic level.
Original languageEnglish
Title of host publicationAgile Processes in Software Engineering and Extreme Programming
Pages371 - 372
ISBN (Electronic)978-3-319-18612-2
ISBN (Print)978-3-319-18611-5
Publication statusPublished - 2015
MoE publication typeA4 Article in a conference publication
Event16th International Conference on Agile Software Development, XP 2015 - Helsinki, Finland
Duration: 25 May 201529 May 2015

Publication series

SeriesLecture Notes in Business Information Processing


Conference16th International Conference on Agile Software Development, XP 2015


  • strategy process
  • continuous planning
  • software development


Dive into the research topics of 'Continuous strategy process in the context of agile and lean software development'. Together they form a unique fingerprint.

Cite this