Long-Term Planning of Development Efforts by Roadmapping – A Model and Experiences from Small Software Companies

Success in the software product business requires timely release of new products and upgrades with proper quality and the right features. For this, a systematic approach for managing the contents, timing and roles of future product releases as well as the product architecture is needed. In practice, such an approach is often missing, especially in small companies, due to inexperience, unclear priorities, time-to-market pressures, or the lack of suitable process infra-structure. In this paper, we present a model to visualize product roadmaps developed together with three small software companies and experiences from its use. The model depicts release and development schedules, the composition of individual releases, services that require attention from the developers, changes to the underlying technology and the planned resource usage. We also present lessons learned from the case companies and outline directions for future research.

[1]  Mark T True,et al.  Software Requirements , 2005 .

[2]  Erik Kamsties,et al.  Requirements engineering in small and medium enterprises , 1998, Requirements Engineering.

[3]  Gary DeGregorio,et al.  Technology management via a set of dynamically linked roadmaps , 2000, Proceedings of the 2000 IEEE Engineering Management Society. EMS - 2000 (Cat. No.00CH37139).

[4]  Satish Nambisan,et al.  Why Service Businesses Are Not Product Businesses , 2001 .

[5]  Björn Regnell,et al.  Requirements lifecycle management and release planning in market-driven requirements engineering processes , 2000, Proceedings 11th International Workshop on Database and Expert Systems Applications.

[6]  Inge van de Weerd,et al.  Towards a Reference Framework for Software Product Management , 2006, 14th IEEE International Requirements Engineering Conference (RE'06).

[7]  Jan Bosch,et al.  Design and use of software architectures - adopting and evolving a product-line approach , 2000 .

[8]  Ruth Milkman,et al.  Microsoft Secrets: How the World's Most Powerful Software Company Creates Technology, Shapes Markets, and Manages People , 1995 .

[9]  D. Probert,et al.  Technology Roadmapping for A Service Organization , 2004 .

[10]  Marjo Kauppinen,et al.  Linking the business view to requirements engineering: long-term product planning by roadmapping , 2005, 13th IEEE International Conference on Requirements Engineering (RE'05).

[11]  Ronald N. Kostoff,et al.  Science and technology roadmaps , 2001, IEEE Trans. Engineering Management.

[12]  Jarno Vähäniitty,et al.  Towards an Approach for Managing the Development Portfolio in Small Product-Oriented Software Companies , 2005, Proceedings of the 38th Annual Hawaii International Conference on System Sciences.

[13]  B. Tabrizi,et al.  Defining next-generation products: an inside look. , 1997, Harvard business review.

[14]  Paul Clements,et al.  Software product lines - practices and patterns , 2001, SEI series in software engineering.

[15]  Markku V. J. Maula,et al.  Finnish Software Product Business: Results from the national Software Industry Survey 2002 , 2002 .

[16]  Detlev J. Hoch,et al.  Secrets of Software Success: Management Insights from 100 Software Firms Around the World , 1999 .

[17]  K. Rautiainen,et al.  Towards a conceptual framework and tool support for linking long-term product and business planning with agile software development , 2008, SDG '08.

[18]  DO SMALL SOFTWARE COMPANIES NEED PORTFOLIO MANAGEMENT ? , 2006 .

[19]  Geoffrey A. Moore Crossing the chasm : marketing and selling high-tech products to mainstream customers , 1999 .