Software product roadmapping in a volatile business environment

Product roadmapping enhances the product development process by enabling early information and long-term decision making about the products in order to deliver the right products to the right markets at the right time. However, relatively little scientific knowledge is available on the application and usefulness of product roadmapping in software product development context. This study develops a framework for software product roadmapping, which is then used to study the critical aspects of the product roadmapping process. The collection of empirical evidence includes both quantitative and qualitative data which sheds further insight into the complexities involved in product roadmapping. Results revealed that organizations view the product roadmap mainly as a tool for strategic decision making as it aims at showing the future directions of the company's products. However, only a few companies appear to have an explicit approach for handling the mechanisms for creating and maintaining such a roadmap. Finally, it is suggested that the strategic importance of product roadmapping is likely to increase in the future and, as a conclusion, a new type of agility is required in order to survive in the turbulent and competitive software business environment.

[1]  P. Soffer,et al.  A Unified RE Approach for Software Product Evolution : Challenges and research agenda , 2005 .

[2]  Linda Gorchels.  The Product Manager's Handbook: The Complete Product Management Resource , 2000 .

[3]  Peter M. Chisnall,et al.  Questionnaire Design, Interviewing and Attitude Measurement , 1993 .

[4]  王瑞祥.  设计未来技术发展蓝图的有效方法——Technology Roadmapping , 2002 .

[5]  Casper Lassenius,et al.  An experience in combining flexibility and control in a small company's software product development process , 2003, 2003 International Symposium on Empirical Software Engineering, 2003. ISESE 2003. Proceedings..

[6]  Walter F. Tichy,et al.  Proceedings 25th International Conference on Software Engineering , 2003, 25th International Conference on Software Engineering, 2003. Proceedings..

[7]  A. Michael Huberman,et al.  An expanded sourcebook qualitative data analysis , 1994 .

[8]  Richard E. Albright,et al.  A unifying architecture for roadmaps frames a value scorecard , 2003, IEMC '03 Proceedings. Managing Technologically Driven Organizations: The Human Side of Innovation and Change.

[9]  Pamela L. Alreck,et al.  The Survey Research Handbook , 1984 .

[10]  Richard E. Albright,et al.  Roadmapping in the Corporation: Product-Technology Roadmaps Define and Communicate Product and Technology Strategy along with a Longer, Smarter View of the Future , 2003 .

[11]  David A. Beeton,et al.  Exploratory roadmapping for foresight , 2008 .

[12]  Joseph A. Blotner.  PIP: a product planning strategy for the whole family or... how we became the brady bunch , 2004, OOPSLA '04.

[13]  Jukka Kääriäinen,et al.  Requirements engineering Inventory of technologies , 2003 .

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

[15]  R. McCarthy.  Linking technological change to business needs , 2003, IEEE Engineering Management Review.

[16]  Robert Phaal,et al.  Fast-start technology roadmapping , 2000 .

[17]  Robert C. McCarthy.  Linking Technological Change to Business Needs: Roadmapping Offers a Systematic Approach for the Pharmaceutical-Biotechnology Industry to Target Technology Investments in the Drug Delivery Process , 2003 .

[18]  Leah Goldin,et al.  Product management in telecom industry-using requirements management process , 2003, Proceedings 2003 Symposium on Security and Privacy.

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

[20]  Pieter Groenveld,et al.  Roadmapping Integrates Business and Technology: At Philips Electronics, Roadmapping May Be Applied to Systems, to a Product Range, to Individual Projects, to Components, or to Production Processes , 2007 .

[21]  Alistair Sutcliffe,et al.  15th IEEE International Requirements Engineering Conference, RE 2007, October 15-19th, 2007, New Delhi, India , 2008, RE.

[22]  Shawn A. Bohner,et al.  Impact analysis-Towards a framework for comparison , 1993, 1993 Conference on Software Maintenance.

[23]  Brad Wardman,et al.  Voice of the customer , 2013, 2013 APWG eCrime Researchers Summit.

[24]  Stephen Fickas,et al.  Critiquing software specifications , 1988, IEEE Software.

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

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

[27]  Haiyan Zhao,et al.  A feature-oriented approach to modeling requirements dependencies , 2005, 13th IEEE International Conference on Requirements Engineering (RE'05).

[28]  Inge van de Weerd,et al.  Developing a Maturity Matrix for Software Product Management , 2010, ICSOB.

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

[30]  James M Richey,et al.  Evolution of Roadmapping at Motorola , 2004 .

[31]  David Probert,et al.  Customizing the technology roadmapping approach , 2003, PICMET '03: Portland International Conference on Management of Engineering and Technology Technology Management for Reshaping the World, 2003..

[32]  Pieter Groenveld.  Roadmapping Integrates Business and Technology , 1997 .

[33]  A. N. Oppenheim,et al.  Questionnaire Design, Interviewing and Attitude Measurement , 1992 .

[34]  Tsang-Ming Jiang,et al.  Software process disturbances , 2000, Proceedings 24th Annual International Computer Software and Applications Conference. COMPSAC2000.

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

[36]  Robert Phaal,et al.  Technology Roadmapping: Starting-Up Roadmapping Fast , 2003 .

[37]  Bashar Nuseibeh,et al.  Requirements engineering: a roadmap , 2000, ICSE '00.

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

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

[40]  Kari Smolander,et al.  Challenges of Knowledge and Collaboration in Roadmapping , 2006, 2006 International Workshop on Software Product Management (IWSPM'06 - RE'06 Workshop).

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

[42]  Casper Lassenius,et al.  An Approach to Product Roadmapping in Small Software Product Businesses , 2002 .

[43]  R. Phaal,et al.  Developing a technology roadmapping system , 2005, A Unifying Discipline for Melting the Boundaries Technology Management:.

[44]  A. Kameoka,et al.  Creating added value from roadmapping process: a knowledge-creating perspective , 2003, IEMC '03 Proceedings. Managing Technologically Driven Organizations: The Human Side of Innovation and Change.

[45]  Robert Phaal,et al.  Technology roadmapping—A planning framework for evolution and revolution , 2004 .

[46]  D. Probert,et al.  Starting-up roadmapping fast , 2003, IEEE Engineering Management Review.

[47]  Matthew B. Miles,et al.  Qualitative Data Analysis: An Expanded Sourcebook , 1994 .

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

[49]  Abbie Griffin,et al.  The Voice of the Customer , 1993 .

[50]  Richard E. Albright,et al.  How to use roadmapping for global platform products , 2002 .

[51]  Casper Lassenius,et al.  Long-Term Planning of Development Efforts by Roadmapping – A Model and Experiences from Small Software Companies , 2009, 2009 35th Euromicro Conference on Software Engineering and Advanced Applications.

[52]  M. Boban,et al.  Effective requirement specification as a precondition for successful software development project , 2003, Proceedings of the 25th International Conference on Information Technology Interfaces, 2003. ITI 2003..

[53]  Meng Li,et al.  Integrated strategy development: an integrated roadmapping approach , 2003, PICMET '03: Portland International Conference on Management of Engineering and Technology Technology Management for Reshaping the World, 2003..

[54]  Henry Mintzberg,et al.  The Fall and Rise of Strategic Planning , 1994 .

[55]  T. Saaty.  Axiomatic foundation of the analytic hierarchy process , 1986 .

[56]  Thomas A. Kappel,et al.  Perspectives on roadmaps: how organizations talk about the future , 2001 .

[57]  C.J. Holmes,et al.  Reasons for roadmapping: a study of the Singaporean SME manufacturing sector , 2004, 2004 IEEE International Engineering Management Conference (IEEE Cat. No.04CH37574).

[58]  T. Kappel,et al.  Roadmapping in the corporation , 2003, IEEE Engineering Management Review.

[59]  Christen Rose-Anderssen,et al.  New Product Development as a Complex Adaptive System of Decisions , 2006 .

[60]  Robert Phaal,et al.  Morphology Analysis for Technology Roadmapping: Application of Text Mining , 2007 .

[61]  Des Greer,et al.  Software release planning: an evolutionary and iterative approach , 2004, Inf. Softw. Technol..

[62]  Christof Ebert,et al.  Tricks and traps of initiating a product line concept in existing products , 2003, 25th International Conference on Software Engineering, 2003. Proceedings..