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

Journal of Software Maintenance and Evolution

Volumn 22, Issue 1, 2010, Pages 53-80

  Fogelström, Nina Dzamashvili ^a   Svahnberg, Tony Gorschek Mikael ^a   Olsson, Peo ^b  

^a BLEKINGE INSTITUTE OF TECHNOLOGY   (Sweden)

^b ERICSSON RESEARCH   (Sweden)

Author keywords

Agile methods; Case study; Market driven software development; Software product management

Indexed keywords

AGILE DEVELOPMENT; AGILE DEVELOPMENT METHODS; AGILE METHODOLOGIES; AGILE METHODS; AGILE PRACTICES; DIFFERENT DOMAINS; ERICSSON; EXTREME PROGRAMMING; HIGH-QUALITY SOFTWARE; PRODUCT MANAGEMENT; PROJECT ACTIVITIES; SOFTWARE DEVELOPMENT; SOFTWARE PRODUCT DEVELOPMENT; SOFTWARE PRODUCT MANAGEMENT; TIME-TO-MARKET;

ALIGNMENT; COMMERCE; PRODUCT DEVELOPMENT; RESEARCH; SOFTWARE DESIGN;

COMPUTER SOFTWARE;

EID: 76749131749     PISSN: 1532060X     EISSN: 15320618     Source Type: Journal    
DOI: 10.1002/smr.453     Document Type: Article

References (57)

1. Abrahamsson P, Warsta J, Siponen M, Ronkainen J. 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. (Pubitemid 34069382)
6. Carlshamre P. 2002. Release planning in market-driven software product development: provoking an understanding. Requirements Engineering 7(3): 139-151.
7. Carlshamre 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 L. 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 IASTED 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.
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.
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. (Pubitemid 44022574)
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. (Pubitemid 350192225)
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.
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, Faegri TE. 2008. Process fusion: an industrial case study on agile software product line engineering. Journal of Systems and Software 81(6): 843-854.
24. Highsmith J, Cockburn A. 2001. Agile software development: the business of innovation. IEEE. Computer 34(9): 120-122.
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. (Pubitemid 40889805)
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. Leffingwell D. 2007. Scaling Software Agility. Addison-Wesley: Boston, MA.
30. 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.
31. Cunningham W, Manifesto for Agile Software Development. 2001. [cited 200-09-30]; Available from.: http://www.agilemanifesto.org.
32. 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.
33. 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.
34. Middleton P. 2001. Lean software development: two case studies. Software Quality Journal 9(4): 241-252. (Pubitemid 33695924)
35. 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. (Pubitemid 47278268)
36. 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.
37. 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/0, 5449, 436,00.html. 2005.
38. 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.
39. 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.
40. 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. (Pubitemid 351540828)
41. Poppendieck M, Poppendieck T. 2003. Lean Software Development - An Agile Toolkit. Addison-Wesley: Boston, MA.
42. 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.
43. 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.
44. Robson C. 2002. Real World Research: A Resource for Social Scientists and Practitioner-Researchers, 2dn edn. Blackwell Publishers: Oxford.
45. 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.
46. Schwaber K, Beedle M. 2001. Agile Software Development with Scrum. Prentice Hall: Upper Saddle River, NJ.
47. 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.
48. Svensson H, Host M. 2005. Introducing an agile process in a software maintenance and evolution organization. 9th European Conference on Software Maintenance and Reengineering (CSMR 2005). Manchester, UK.
49. 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.
50. 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.
51. 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. (Pubitemid 351561485)
52. 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.
53. Williams L, Cockburn A. 2003. Agile software development: it's about feedback and change. Computer 36(6): 39-43.
54. 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.
55. Wohlin C, Runeson P, Host 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.
56. Womack JP, Jones DT, Roos D. 1991. The Machine That Changed the World: The Story of Lean Production. Harper Perennial: New york.
57. Yin R. 1994. Case http://Case Study Research. SAGE Publications: Thousand Oaks, CA.