• Wim Codenie
  • Minna Pikkarainen
  • Nick Boucart
  • Jeroen Deleu


Imagine that you are the CEO of a software company creating a software-based product. You have been in business for quite some time, and – where many others have failed – you have managed to bring a product to market that is liked by its customers. Of course, you had your share of difficulties. There were times when serious quality problems threatened the future of the company. There were the many sleepless nights caused by budgets running out of control and even occasions when you were left at the mercy of the development team to have a new release out before the next fair.


Business Model Product Innovation Innovation Activity Software Company Comfort Zone 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


  1. Agile Alliance (2011) Agile Alliance. Accessed Mar 2011
  2. Altshuller G (1984) Creativity as an exact science. Gordon & Breach, New YorkGoogle Scholar
  3. Anderson C (2006) The long tail: why the future of business is selling less of more. Hyperion, New YorkGoogle Scholar
  4. Bartels A (2009) Smart computing drives the new era of IT growth. Forrester ResearchGoogle Scholar
  5. Brooks F (1995) The mythical man-month: essays on software engineering, anniversary edition. Addison-Wesley ProfessionalGoogle Scholar
  6. Casadesus-Masanell R, Ricart J (2007) Competing Through Business. IESE Business School Working Paper No. 713Google Scholar
  7. Codenie W, González-Deleito N, Deleu J, Blagojevic V, Kuvaja P, Similä J (2010) Managing flexibility and variability: a road to competitive advantage. In: Kang KC, Sugumaran V, Park S (eds) Applied software product line engineering. Taylor and Francis, pp 269–313Google Scholar
  8. Creax (2011) Accessed Mar 2011
  9. Desouza KC, Awazu Y (2005) Managing radical software engineers: between order and chaos. In: Proceedings of the 2005 workshop on human and social factors of software engineering, St. Louis, 16 May 2005. HSSE ’05, ACM, New York, pp 1–5Google Scholar
  10. Diener K, Piller F (2010) The market for open innovation: increasing the efficiency and effectiveness of the innovation process, RWTH-TIM GroupGoogle Scholar
  11. Fellowforce (2011) Accessed Mar 2011
  12. Greenspun, P (2002) Managing software engineers. Accessed Mar 2011
  13. Indiegroup (2011) Cognistreamer. Accessed Mar 2011
  14. ISPIM (2011) Professional innovation management. Accessed Mar 2011
  15. ITEA (2006) Information technology for European advancement. Accessed Mar 2011
  16. ITEA (2009) Roadmap for software-intensive systems and services, 3rd edn. Accessed Mar 2011
  17. ITEI (2007) Information technologies supporting the execution of innovation projects. Accessed Mar 2011
  18. KANBAN (2011) Kanban. Accessed Mar 2011
  19. Kim WC (2005) Blue ocean strategy: how to create uncontested market space and make competition irrelevant, 1st edn. Harvard Business Press, BostonGoogle Scholar
  20. LEAN (2011) Lean development. Accessed Mar 2011
  21. Lippoldt D, Stryszowski P (2009) Innovation in the software sector. OECD Publishing, ParisGoogle Scholar
  22. Mann D (2005) TRIZ for software. Accessed Mar 2011
  23. McConnell S (2011) Origins of 10X – how valid is the underlying research? Accessed Mar 2011
  24. Nilay O, Abrahamsson P (2009) building blocks of agile innovation. BookSurge Publishing, North CharlestonGoogle Scholar
  25. Osterwalder A, Pigneur Y (2010) Business model generation. Wiley, Hoboken, NJGoogle Scholar
  26. Pikkarainen M, Boucart N, Alvaro JAH, Kuvaja P, Codenie W, Biot O, Koivumäki T (2010) Impacts of product development strategy on innovation activities in software intensive corporations. In: The proceedings of the XXI ISPIM conference 2010 Bilbao, Spain, 6–9 June 2010. WileyGoogle Scholar
  27. Rutkowski A, Saunders C (2010) Growing pains with information overload. Computer 43(6):94–96CrossRefGoogle Scholar
  28. Shneiderman B (2007) Creativity support tools: accelerating discovery and innovation. Commun ACM 50(12):20–32CrossRefGoogle Scholar
  29. SWEBOK (2004) Guide to the software engineering body of knowledge. Accessed Mar 2011
  30. Tharp A (2007) Innovating: the importance of right brain skills for computer science graduates. SIGCSE Bull 39(3):126–130CrossRefGoogle Scholar
  31. Tourwe T, Codenie W, Boucart N (2009a) Bringing software innovations to market in release-driven organizations, building blocks of agile innovation, CharlestonGoogle Scholar
  32. Tourwe T, Codenie W, Boucart N, Blagojevic V (2009b) Demystifying release definition: from requirements prioritization to collaborative value quantification. In: 15th international working conference on requirements engineering: foundation for software quality, Amsterdam, The NetherlandsGoogle Scholar
  33. von Hippel E (1986) Lead users: a source of novel product concepts. Manag Sci 32(7):791–806. Accessed Mar 2011CrossRefGoogle Scholar
  34. Weyrich C (2005) Siemens’ R&D: tuned in to today’s megatrends. In: Siemens pictures of the future. Accessed Mar 2011

Copyright information

© Springer-Verlag Berlin Heidelberg 2011

Authors and Affiliations

  • Wim Codenie
    • 1
  • Minna Pikkarainen
    • 2
  • Nick Boucart
    • 1
  • Jeroen Deleu
    • 3
  1. 1.Software Engineering GroupSirrisBrusselBelgium
  2. 2.Software Business GroupVTT Technical Research Centre of FinlandOuluFinland
  3. 3.SirrisBrusselBelgium

Personalised recommendations