A conceptual model and process for client-driven agile requirements prioritization

2010 4th International Conference on Research Challenges in Information Science - Proceedings, RCIS 2010

Volumn , Issue , 2010, Pages 287-298

  Racheva, Zomitza ^a   Daneva, Maya ^a   Herrmann, Andrea ^b   Wieringa, Roel J ^a  

^a UNIVERSITY OF TWENTE   (Netherlands)

^b TECHNICAL UNIVERSITY OF BRAUNSCHWEIG   (Germany)

Author keywords

Agile development; Grounded theory; Inter iteration decision making process; Requirements prioritization

Indexed keywords

DECISION MAKING; DECISION THEORY; SOFTWARE DESIGN;

AGILE DEVELOPMENT; AGILE SOFTWARE DEVELOPMENT; DECISION MAKING PROCESS; EMPIRICAL INVESTIGATION; GENERIC CONCEPTUAL MODELS; GROUNDED THEORY; PRIORITIZATION PROCESS; REQUIREMENTS PRIORITIZATION;

ITERATIVE METHODS;

EID: 77957307762     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/rcis.2010.5507388     Document Type: Conference Paper

References (44)

1. Cao, L, Ramesh B., Agile Requirements Engineering Practices: An Empirical Study, IEEE Software, Jan/Feb, 2008 pp. 60-67.
2. Barney S., Aurum A, C. Wohlin, A Product Management Challende: Creating Software Product Value through Requirements Selection, Journal of Software Architecture, 54 (2008), pp. 576-593.
3. Petersen K., C. Wohlin, A Comparison of Issues and Advantages in Agile and Incremental development between State of the Art and an Industrial Case, Journal of Systems and Software, 82 (2009), pp. 1479-1490.
4. Agile Journal http://www.agilejournal.com/
5. Augustine, S., Managing Agile Projects, Prentice-Hall, 2005.
6. Bleek, W-G, H. Wolf, Agile Softwareentwicklung: Werte, Konzepte und Methoden. dpunkt, Heidelberg, 2008.
7. Principles behind the Agile Manifesto, 2001, URL: http://agilemanifesto. org/principles.htrn/
8. Beck, K. eXtreme Programming Explained: Embrace Change, Addison Wesley, 2000.
9. Larman, Scaling Lean & Agile Development: Thinking and Organizational Tools for Large-Scale Scrum, Addison-Wesley, 2008.
10. Schwaber, K., Agile Project Management with SCRUM, Microsoft Press, 2004.
11. Charmaz, K. Constructing Grounded Theory: a Practical Guide through Qualitative Research, Thousand Oaks CA, Sage, 2007.
12. Glaser, B. G., Basics of Grounded Theory Analysis: Emergence vs Forcing, Sociology Press Mill Valley, 1992.
13. Strauss, AL., J.M. Corbin, Basics of Qualitative Research - Grounded Theory Procedures and Techniques, Sage, Newbury Park, 1991.
14. Dr Dobb's portal http://www.ddj.coml
15. InfoQ software development community http://www.infoq.com/agile
16. Webster J., R.T. Watson: Analyzing the Past to Prepare for the Future: Writing a Literature Review. MIS Quarterly 26(2): (2002)
17. Highsmit, J. Agile Project Management: Creating Innovative Products
18. Hunt, J., Agile software construction. Springer, London, 2006.
19. Lippert, M., S. Roock, H. Wolf, eXtreme Programming in Action: Practical Experiences from Real World Projects, John Wiley & Sons, 2002
20. Kitchenham, B., Procedures for Undertaking Systematic Reviews, Joint Technical Report, Computer Science Department, Keele University (TRISE-0401) and National ICT Australia Ltd. (0400011 T.l), 2004.
21. Berteig, M., Methods of Prioritization, March 20, 2006 in Agile Advice Online Practitioners Forum, http://www.agileadvice.comlarchives/2006/03/methods- of-prio.html
22. Leffingwell, D., Widrig, D., Managing Software Requirements, 2nd ed. Boston, Addison-Wesley, 2003
23. Tabaka, J., Collaboration Explained: Facilitation Skills for Software Project Leaders. Addison Wesley 2006.
24. Getting Started With Use Case Modeling, An Oracle White Paper, May 2007 http://www.oracle.comltechnology/products/jdev/collateral/papers/10g/ gswUseCaseModeling.pdf
25. Gottesdiener, E., At a Glance: Other Prioritization Methods, EBG Consulting, Inc. www.ebgconsulting.com
26. Karlsson, L., Thelin, T., Regnell. B., Berander, P., Wohlin, C., Pair-wise Comparisons versus Planning Game Partitioning-experiments on Requirements Prioritisation Techniques, Empirical Software Engineering, 12(11), 2007
27. Saaty, T.L., The Analytic Hierarchy Process, McGraw-Hili, New York, 1980.
28. Ahl, V. An Experimental Comparison of Five Prioritization Methods, Master's Thesis, School of Engineering, Blekinge Institute of Technology, Ronneby, Sweden, 2005.
29. Fraser, J., Setting Priorities, April 23, 2002, URL: http://www. adaptivepath.com/ideas/essays/archives/000018.php
30. Crow, K. Customer-focused Development with QFD, URL: http://www.npd- solutions.com/qfd.html. Accessed on August 26, 2009.
31. Wiegers, K., First Things First: Prioritizing Requirements, Software Development, 7(9) 1999.
32. Li, C., Akker, J.M. van den, Brinkkemper, S., Diepen, G. Integrated Requirement Selection and Scheduling for the Release Planning of a Software Product, In Proc. of REFSQ '07, Spinger LNCS, pp. 93-108.
33. Patton, J., Finding the Forest in the Trees, In Proc of the IEEE Conf. on OOPSLA, 2005, pp: 266-274.
34. Center of Quality Management Journal (1993) Special issue on Kano's Methods for Understanding Customer-defined Quality, Vol 2, No 4, Fall 1993
35. Cohn, M. Agile Estimating and Planning, Prentice Hall, 2005.
36. Ambler, S., Complex requirements on an Agile Project, Dr Dobbs, Oct 31, 2008, http://www.ddj.com/architect/211800534?cid=Ambysoft
37. Harris, R. S., M. Cohn, Incorporating Leaming and Expected Cost of Change in Prioritizing Features on Agile Projects. XP 2006: pp. 175-180
38. Clarke, A. Situational Analysis: Grounded Theory after the Postmodern Turn, Thousand Oaks, CA, Sage, 2005.
39. Gottesdiener, E. How Agile Practices Reduce Requirements Risk, Better Software, July/Aug, 2009.
40. Ambler, S.W., Agile Modeling - Effective Practices for eXtreme Programming and the Unified Process, Wiley, New York, 2002
41. Alenljung, B., A. Person, Portraying the Practice of Decision-making in Requirements Engineeribng: a Case Study of large Scale Bespoke Development, Requirements Engineering Journal, 2008, 13, pp. 257-279.
42. Racheva, Z., M. Daneva, K. Sikkel, Value Creation by Agile Projects: Methodology or Mystery? In: Proc. of the Conf. on PROFES, Springer, LNCS, pp.141-155
43. Patton, J. Ambiguous Business Value Harms Software Products, IEEE Software, 25(1), Jan/Feb 2008.
44. Ambler, S., Answering the "Where is the Proof That Agile Methods Work" Question, http://www.agilemodeling.com/essays/proof.htm