article

The impact of agile principles on market-driven software product development

Authors:

Nina Dzamashvili Fogelström,

Mikael Svahnberg,

Peo OlssonAuthors Info & Claims

Journal of Software Maintenance and Evolution: Research and Practice, Volume 22, Issue 1

Pages 53 - 80

Published: 01 January 2010 Publication History

Abstract

Agile development methods such as extreme programming (XP), SCRUM, Lean Software Development (Lean SD) and others have gained much popularity during the last years. Agile methodologies promise faster time-to-market, satisfied customers and high quality software. While these prospects are appealing, the suitability of agile practices to different domains and business contexts still remains unclear. In this article we investigate the applicability of agile principles in the context of market-driven software product development (MDPD), focusing on pre-project activities. This article presents results of a comparison between typical properties of agile methods to the needs of MDPD, as well as findings of a case study conducted at Ericsson, an early adopter of agile product development. The results show misalignment between the agile principles and needs of pre-project activities in market-driven development. This misalignment threatens to subtract from the positive aspects of agile development, but maybe more importantly, threaten the overall product development by disabling effective product management. Copyright © 2009 John Wiley & Sons, Ltd.

References

[1]

Abrahamsson P, Warsta J, Siponen M, Ronkainen 1. 2003. New directions on agile methods: a comparative analysis. 25th International Conference on Software Engineering (ICSE'03). IEEE Press.

[2]

Barney S, Aurum A, Wohlin C. Quest for a Silver Bullet: Creating Software Product Value through Requirements Selection. 2006.32nd EUROMICRO Conference on Software Engineering and Advanced Applications (EUROMICRO'06), IEEE Computer Society. Cavtat, Croatia.

[3]

Beck K. 1999. Extreme Programming Explained: Embrace Change. Addison-Wesley: Massachusetts, Boston MA,

[4]

Beck K, Fowler M. 2001. Planning Extreme Programming, The XP series. Addison-Wesley: Boston, MA.

[5]

Boehm B. 2002. Get ready for agile methods, with care. Computer 35(1): 64-69.

Digital Library

[6]

Carlsharnre P. 2002. Release planning in market-driven software product development: provoking an understanding. Requirements Engineering 7(3): 139-151.

[7]

Carlsharnre P, Sandahl K, Lindvall M, Regnell B, Nattoch Dag J. 2001. An industrial survey of requirements interdependencies in software product release planning. Proceedings of the Fifth IEEE International Symposium on Requirements Engineering, Los Alamitos, CA, IEEE.

[8]

Clements P, Northrop 1. 2002; Software product lines: practices and patterns. The SEI Series in Software Engineering. Addison-Wesley: Boston, MA; 608.

[9]

Cohen D, Lindvall M, Costa P. 2004. An introduction to agile methods. Advances in Computers 62: 1-66.

[10]

Dagnino A, Smiley K, Srikanth H, Anton AI, Williams L. 2004. Experiences in applying agile software development practices in new product development. 8th lASTED International Conference on Software Engineering and Applications, Cambridge, MA.

[11]

Dahlstedt A, Karlsson L, Persson A, NattochDag J, Regnell B. 2003. Market-driven requirements engineering processes for software products - a report on current practices. International Workshop on COTS and Product Software RECOTS, held in conjunction with the 11th IEEE International Requirements Engineering Conference, Los Alamitos, CA, IEEE.

[12]

Dybå T, Dingsøyr T. 2008. Empirical studies of agile software development: a systematic review. Information and Software Technology 50(9-10): 833-859.

Digital Library

[13]

Ebert C. Requirements BEFORE the requirements: understanding the upstream impacts. 13th IEEE International Conference on Requirements Engineering (RE'05), IEEE Paris, France. 2005.

[14]

Erickson J, Lyytinen K, Siau K. 2005. Agile modeling, agile software development, and extreme programming: the state of research. Journal of Database Management 16(4): 88-100.

[15]

Fitzgerald B. 1998. An empirical investigation into the adoption of systems development methodologies. Journal of Information & Management 34: 317-328.

Digital Library

[16]

Fitzgerald B, Hartnett G, Conboy K. 2006. Customizing agile methods to software practices at Intel Shannon. European Journal of Information Systems 15: 200-213.

Digital Library

[17]

Fricker S, Gorschek T, Myllyperkiö P. 2007. Handshaking between software projects and stakeholders using implementation proposals. Requirements Engineering: Foundation for Software Quality, (REFSQ'07). Springer Berlin/Heidelberg: Trondheim.

[18]

Gorschek T. 2006. Requirements engineering supporting technical product management. School of Engineering-Department of Systems and Software Engineering. Blekinge Institute of Technology: Ronneby. 342.

[19]

Gorschek T, Davis A. 2008. Requirements engineering: in search of the dependent variables. Information and Software Technology 50: 67-75.

Digital Library

[20]

Gorschek T, Wohlin C. 2004. Packaging software process improvement issues-a method and a case study. Software: Practice and Experience 34(14): 1311-1344.

[21]

Gorschek T, Wohlin C. 2006. Requirements abstraction model. Requirements Engineering 11(1): 79-101.

Digital Library

[22]

Greer D, Ruhe G. 2004. Software release planning: an evolutionary and iterative approach. Information and Software Technology 46(4):243-253.

[23]

Hanssen GK, Fægri TE. 2008. Process fusion: an industrial case study on agile software product line engineering. Journal of Systems and Software 81(6): 843-854.

Digital Library

[24]

Highsmith J, Cockburn A. 2001. Agile software development: the business of innovation. IEEE. Computer 34(9): 120-122.

Digital Library

[25]

Ilieva S, Ivanov P, Stefanova E. 2004. Analyses of an agile methodology implementation. 30th Euromicro Conference. IEEE Computer Society Press:

[26]

Karlsson L, Dahlstedt A, Nattoch Dag J, Regnell B, Persson A. 2003. Challenges in market-driven requirements engineering - an industrial interview study. Proceedings of the Eighth International Workshop on Requirements Engineering Foundation for Software Quality (REFSQ'02), Essen, Germany, Universität Duisburg-Essen.

[27]

Karlstrom D, Runeson P. 2005. Combining agile methods with stage-gate project management. IEEE. Software 22(3): 43-49.

Digital Library

[28]

Koch AS. 2005. Agile Software Development Evaluating the Methods for Your Organization. Artech House Publishers: London.

[29]

Layman L, Williams L, Cunningham L. 2004. Exploring extreme programming in context: an industrial case study. Agile Development Conference, Salt lake city, UT; published by IEEE Computer Society Press.

[30]

Leffingwell D. 2007. Scaling Software Agility. Addison-Wesley: Boston, MA.

[31]

Lehtola L, Kauppinen M. 2006. Suitability of requirements prioritization methods for market-driven software product development. Software Process: Improvement and Practice 11(1): 7-19.

[32]

Cunningham W, Manifesto for Agile Software Development. 2001. {cited 200--09-30); Available from http://www.agilemanifesto.org.

[33]

Mann C, Maurer F. 2005. A case study on the impact of scrum on overtime and customer satisfaction. Agile Development Conference (ADC'05). IEEE Computer Society: Denver, CO, published by IEEE Computer Society Press.

[34]

Mannaro K, Melis M, Marchesi M. 2004. Empirical analysis on the satisfaction of IT employees comparing XP practices with other software development methodologies. Extreme Programming and Agile Processes in Software Engineering Lecture Notes in Computer Science. Lecture Notes in Computer Science, Springer: Berlin.

[35]

Middleton P. 2001. Lean software development: two case studies. Software Quality Journal 9(4): 241-252.

[36]

Ngo-The A, Ruhe G. 2008. A systematic approach for solving the wicked problem of software release planning. Soft Computing - A Fusion of Foundations, Methodologies and Applications 12(1): 95-108.

Digital Library

[37]

Noor MA, Rabiser R, Grünbacher P. 2008. Agile product line planning: a collaborative approach and a case study. Journal of Systems and Software 81(6): 868-882.

Digital Library

[38]

North American and European Enterprise Software and Services Survey. Business Technographics. Survey conducted by Forrester Research inc. Available at http://www.Forrester.com/ER/Research/Survey/Excerpt/O, 5449, 436,00.html. 2005.

[39]

Paetsch F, Eberlein A, Maurer F. 2003. Requirements engineering and agile software development. 12th IEEE international Workshops on Enabling Technologies: Infrastructure for Collaborative Enterprises, IEEE, Linz, Austria.

[40]

Petersen K, Wohlin C. 2008. Issues and advantages of using agile and incremental practices. The Eighth Conference on Software Engineering Research and Practice in Sweden (SERPS'08), Karlskrona, Sweden.

[41]

Pettersson F, Ivarsson M, Gorschek T, Ohman P. 2008. A practitioner's guide to light weight software process assessment and improvement planning. Journal of Systems and Software 81(6): 972-995.

Digital Library

[42]

Poppendieck M, Poppendieck T. 2003. Lean Software Development - An Agile Toolkit. Addison-Wesley: Boston, MA.

[43]

Potts C. 1995. Invented requirements and imagined customers: requirements engineering for off-the-shelf software. Proceedings of the Second IEEE International Symposium on Requirements Engineering, Los Alamitos, IEEE.

[44]

Regnell B, Brinkkemper S. 2005. Market-Driven Requirements Engineering for Software Products. In Engineering and Managing Software Requirements, Wohlin C, Aurum A (eds). Springer: Heidelberg, Berlin 287-308.

[45]

Robson C. 2002. Real World Research: A Resource for Social Scientists and Practitioner-Researchers, 2dn edn. Blackwell Publishers: Oxford.

[46]

Saliu O, Ruhe G. 2005. Supporting software release planning decisions for evolving systems. 29th Annual IEEE/NASA Software Engineering Workshop (SEW'05), IEEE, Greenbelt, MD.

Digital Library

[47]

Schwaber K, Beedle M. 2001. Agile Software Development with Scrum. Prentice Hall: Upper Saddle River, NJ.

[48]

Sillitti A, Succi G. 2005. Requirements engineering for agile methods. In Engineering and Managing Software Requirements, Wohlin C, Aurum A (eds). Springer: New York, NY, 309-326.

[49]

Svensson H, Höst M. 2005. Introducing an agile process in a software maintenance and evoluition organization. 9th European Conference on Software Maintenance and Reengineering (CSMR 2005). Manchester, UK.

[50]

Telelogic Focal Point - Software for Product Management and Product Portfolio Management. 2009. {cited 2009-01-22}; Available from: http://www.telelogic.com/corp/products/focalpoint/index.cfm IBM Corporation.

[51]

Tian K, Cooper K. 2006. Agile and software product line methods: are they so different? 1st International Workshop on Agile Product Line Engineering: collocated with the 10th International Software Product Line Conference (SPLC), Baltimore, MD.

[52]

Tomaszewski P, Berander P, Damm L-O. 2008. From traditional to streamline development - opportunities and challenges. Software Process: Improvement and Practice 13(2): 195-212.

Digital Library

[53]

van de Weerd I, Brinkkemper S, Nieuwenhuis R, Versendaal J, Bijlsma L. 2006. Towards a reference framework for software product management. Proceedings of the 14th IEEE International Requirements Engineering Conference (RE'06), IEEE Computer Society, Minneapolis, MN.

Digital Library

[54]

Williams L, Cockburn A. 2003. Agile software development: it's about feedback and change. Computer 36(6): 39-43.

Digital Library

[55]

Wohlin C, Aurum A. 2005. What is important when deciding to include a software requirement in a project or release? International Symposium on Empirical Software Engineering, IEEE, Noosa Heads, Australia.

[56]

Wohlin C, Runeson P, Höst M, Ohlson MC, Regnell B, Wesslén A. 2000. Experimentation in Software Engineering: An Introduction, The Kluwer International Series in Software Engineering. Kluwer Academic: Boston, MA; 204.

[57]

Womack JP, Jones DT, Roos D. 1991. The Machine That Changed the World: The Story of Lean Production. Harper Perennial: New york.

[58]

Yin R. 1994. Case Study Research. SAGE Publications: Thousand Oaks, CA.

Cited By

Singi KKaulgud VSharma VDubash NPodder SGoedicke MBosch JOlsson HTichy MAlmeida E(2017)Test optimization from release insightsProceedings of the 3rd International Workshop on Rapid Continuous Software Engineering10.5555/3105398.3105402(16-19)Online publication date: 20-May-2017
https://dl.acm.org/doi/10.5555/3105398.3105402
Alahyari HBerntsson Svensson RGorschek T(2017)A study of value in agile software development organizationsJournal of Systems and Software10.5555/3063155.3063214125:C(271-288)Online publication date: 1-Mar-2017
https://dl.acm.org/doi/10.5555/3063155.3063214
Rissanen OMünch JTichy MBosch JGoedicke MFitzgerald B(2015)Continuous experimentation in the B2B domainProceedings of the Second International Workshop on Rapid Continuous Software Engineering10.5555/2820678.2820682(12-18)Online publication date: 16-May-2015
https://dl.acm.org/doi/10.5555/2820678.2820682
Show More Cited By

Index Terms

The impact of agile principles on market-driven software product development
1. Software and its engineering
  1. Software creation and management
    1. Software development process management

Index terms have been assigned to the content through auto-classification.

Recommendations

Adopting to Agile Software Development

Abstract Agile software development can be made successful, but there is no well-defined way how to achieve this. The problem is that the successful adoption of agile methods and practices is a complex process and this process should be customizable for ...
The Combination of Agile and Lean in Software Development: An Experience Report Analysis
AGILE '11: Proceedings of the 2011 Agile Conference

There has been a noticeable focus shift from agile methods such as extreme Programming (XP) and Scrum to lean software development in the last several years, which is indicated as â from agile to leanâ . However, the reality may not be as simple or ...
Integrating agile software development into stage-gate managed product development

Agile methods have evolved as a bottom-up approach to software development. However, as the software in embedded products is only one part of development projects, agile methods must coexist with project management models typically of the stage-gate ...

Comments

Information & Contributors

Information

Published In

cover image Journal of Software Maintenance and Evolution: Research and Practice

Journal of Software Maintenance and Evolution: Research and Practice Volume 22, Issue 1

January 2010

78 pages

ISSN:1532-060X

Issue’s Table of Contents

Publisher

John Wiley & Sons, Inc.

United States

Publication History

Published: 01 January 2010

Author Tags

Qualifiers

Article

Contributors

Other Metrics

View Article Metrics

Bibliometrics & Citations

Bibliometrics

Article Metrics

6
Total Citations
View Citations
0
Total Downloads

Downloads (Last 12 months)0
Downloads (Last 6 weeks)0

Reflects downloads up to 16 Oct 2024

Other Metrics

View Author Metrics

Citations

Cited By

Singi KKaulgud VSharma VDubash NPodder SGoedicke MBosch JOlsson HTichy MAlmeida E(2017)Test optimization from release insightsProceedings of the 3rd International Workshop on Rapid Continuous Software Engineering10.5555/3105398.3105402(16-19)Online publication date: 20-May-2017
https://dl.acm.org/doi/10.5555/3105398.3105402
Alahyari HBerntsson Svensson RGorschek T(2017)A study of value in agile software development organizationsJournal of Systems and Software10.5555/3063155.3063214125:C(271-288)Online publication date: 1-Mar-2017
https://dl.acm.org/doi/10.5555/3063155.3063214
Rissanen OMünch JTichy MBosch JGoedicke MFitzgerald B(2015)Continuous experimentation in the B2B domainProceedings of the Second International Workshop on Rapid Continuous Software Engineering10.5555/2820678.2820682(12-18)Online publication date: 16-May-2015
https://dl.acm.org/doi/10.5555/2820678.2820682
Fabijan AOlsson HBosch J(2015)Early Value Argumentation and PredictionProceedings of the 16th International Conference on Product-Focused Software Process Improvement - Volume 945910.1007/978-3-319-26844-6_2(16-23)Online publication date: 2-Dec-2015
https://dl.acm.org/doi/10.1007/978-3-319-26844-6_2
Callele DWnuk KBorg MBurnett MGiese HNguyen TBrun Y(2013)Confounding factors when conducting industrial replications in requirements engineeringProceedings of the 1st International Workshop on Conducting Empirical Studies in Industry10.5555/2662528.2662545(55-58)Online publication date: 19-May-2013
https://dl.acm.org/doi/10.5555/2662528.2662545
Edberg DIvanova PKuechler W(2012)Methodology MashupsJournal of Management Information Systems10.2753/MIS0742-122228041028:4(271-304)Online publication date: 1-Apr-2012
https://dl.acm.org/doi/10.2753/MIS0742-1222280410

View Options

View options

Get Access

Login options

Check if you have access through your login credentials or your institution to get full access on this article.

Full Access

Get this Publication

Media

Figures

Other

Tables

View Issue’s Table of Contents