An Approach to Product Roadmapping in Small Software Product Businesses

Success in software product business requires the release of new products and product upgrades with the right amount of features and quality within an open market window. 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-tomarket pressures, or the lack of suitable process infrastructure. In this paper, we present an approach based on product roadmapping that can aid such companies in their product planning. We also discuss initial experiences from using the approach in three small software companies. The product roadmap expresses the release and development schedules, composition of individual releases, changes to the underlying technology, services requiring attention from product development and the planned resource usage.

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

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

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

[4]  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).

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

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

[7]  Casper Lassenius,et al.  A tentative framework for managing software product development in small companies , 2002, Proceedings of the 35th Annual Hawaii International Conference on System Sciences.

[8]  Rob C. van Ommering.  Roadmapping a Product Population Architecture , 2001, PFE.

[9]  Björn Regnell,et al.  An industrial survey of requirements interdependencies in software product release planning , 2001, Proceedings Fifth IEEE International Symposium on Requirements Engineering.

[10]  Michael A. Cusumano,et al.  Competing On Internet Time: Lessons From Netscape And Its Battle With Microsoft , 1998 .

[11]  Robert E. Hoskisson,et al.  Strategic Management: Competitiveness and Globalization , 1994 .

[12]  Paul Strauss,et al.  Motorola Inc. , 1993 .

[13]  Sergio Bandinelli,et al.  European Software Institute , 1996 .

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

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

[16]  D. Garvin,et al.  Harvard Business School Publishing TN , 1996 .

[17]  Karl E. Wiegers,et al.  Software Requirements , 1999 .

[18]  H. Belloc.  The Free Press , 2002 .

[19]  Steven C. Wheelwright,et al.  New Product Development Imperative, The , 1999 .

[20]  Martin Höst,et al.  An Industrial Case Study on Distributed Prioritisation in Market-Driven Requirements Engineering for Packaged Software , 2001, Requirements Engineering.

[21]  Michael E. Bays.  Software Release Methodology , 1999 .

[22]  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.

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