Vol. 7 No. 4 (2019): Business & Management Studies: An International Journal


Büşra Özdenizci KÖSE
Asst. Prof., Gebze Technical University

Published 2019-09-24


  • Requirements Engineering,
  • Business Analysis,
  • Agile methods,
  • Agile RE,
  • Scrum
  • Gereksinim Mühendisliği,
  • İş Analizi,
  • Çevik metotlar,
  • Çevik RE,
  • Scrum

How to Cite

KÖSE, B. Özdenizci. (2019). RECENT AGILE REQUIREMENT ENGINEERING PRACTICES IN IT PROJECTS: A CASE ANALYSIS. Business & Management Studies: An International Journal, 7(4), 1776–1805. https://doi.org/10.15295/bmij.v7i4.1214


Today, the implementation of high quality and efficient Requirement Engineering (RE) practices in agile software development projects, is gaining great importance. Practitioners and researchers seeks for lighter RE practices that can handle the issues of abstract, unclear and changing requirements, and at the same time that can satisfy the Agile Manifesto philosophy. This study examines importance of RE practices in agile software development projects, and explores which aspects of the RE practices are perceived as most critical and how such aspects are adapted in practice today through two different agile software development projects of a case organization. This study aims to contribute agile RE literature by providing an interpretive analysis on perception of agile RE practices from different perspectives (agile team members, product owners, some top executives). Within this context, this study draws lessons from case studies and presents beneficial agile RE guidelines for practitioners and researchers.


Download data is not yet available.


  1. Ambler, S. W. (2018). Agile Analysis. Agile Modeling. http://www.agilemodeling.com/essays/agileAnalysis.htm#AgileAnalysis (date accessed: 09.08.2019).
  2. Awad, M. A. (2005). A comparison between agile and traditional software development methodologies. University of Western Australia, 30.9.
  3. Beck, K., Beedle, M., Van Bennekum, A., Cockburn, A., Cunningham, W., Fowler, M., Kern, J. (2001). Manifesto for agile software development.
  4. Beck, K., Beedle, M., Van Bennekum, A., Cockburn, A., Cunningham, W., Fowler, M. & Kern, J. (2001). The agile manifesto.
  5. Bjarnason, E., Wnuk, K., & Regnell, B. (2011, July). A case study on benefits and side-effects of agile practices in large-scale requirements engineering. In Proceedings of the 1st Workshop on Agile Requirements Engineering (p. 3). ACM.
  6. Cao, L., & Ramesh, B. (2008). Agile requirements engineering practices: An empirical study. IEEE software, 25(1), 60-67.
  7. Clancy, T. (2014). The Standish Group chaos report. Project Smart.
  8. Collabnet Versione (2019). StateofAgile Report: 13th Annual State Of Agile Report. https://www.stateofagile.com/#ufh-i-521251909-13th-annual-state-of-agile-report/473508.
  9. De Lucia, A., & Qusef, A. (2010). Requirements engineering in agile software development. Journal of emerging technologies in web intelligence, 2(3), 212-220.
  10. Dybå, T., & Dingsøyr, T. (2008). Empirical studies of agile software development: A systematic review. Information and software technology, 50(9-10), 833-859.
  11. Fancott, T., Kamthan, P., & Shahmir, N. (2012, December). Towards next generation requirements engineering. In 2012 International Conference on Social Informatics (pp. 328-331). IEEE.
  12. Flora, H. K., & Chande, S. V. (2014). A systematic study on agile software development methodologies and practices. International Journal of Computer Science and Information Technologies, 5(3), 3626-3637.
  13. IIBA & Agile Alliance. (2015). A Guide to the Business Analysis Body of Knowledge (Babok Guide). International Institute of Business Analysis.
  14. Javanmard, M., & Alian, M. (2015). Comparison between Agile and Traditional software development methodologies. Cumhuriyet Üniversitesi Fen-Edebiyat Fakültesi Fen Bilimleri Dergisi, 36(3), 1386-1394.
  15. Joslin, R., & Müller, R. (2016). The impact of project methodologies on project success in different project environments. International Journal of Managing Projects in Business, 9(2), 364-388.
  16. Käpyaho, M., & Kauppinen, M. (2015, August). Agile requirements engineering with prototyping: A case study. In 2015 IEEE 23rd International requirements engineering conference (RE) (pp. 334-343). IEEE.
  17. Kasauli, R., Liebel, G., Knauss, E., Gopakumar, S., & Kanagwa, B. (2017, September). Requirements engineering challenges in large-scale agile system development. In 2017 IEEE 25th International Requirements Engineering Conference (RE) (pp. 352-361). IEEE.
  18. Kieffer, S., Ghouti, A., & Macq, B. (2017). The agile UX development lifecycle: Combining formative usability and agile methods.
  19. Mersino, A, (2018). Agile Projects are More Successful than Traditional Projects. Vitality Chicago. https://vitalitychicago.com/blog/agile-projects-are-more-successful-traditional-projects/ (date accessed: 09.08.2019).
  20. Musa, F., & Tariq, M. A. (2017). Agile Methodology: Hybrid Approach Scrum and XP. International Journal of Scientific & Engineering Research, 8(4).
  21. Ochodek, M., & Kopczyńska, S. (2018). Perceived importance of agile requirements engineering practices–A survey. Journal of Systems and Software, 143, 29-43
  22. Paetsch, F., Eberlein, A., & Maurer, F. (2003, June). Requirements engineering and agile software development. In WET ICE 2003. Proceedings. Twelfth IEEE International Workshops on Enabling Technologies: Infrastructure for Collaborative Enterprises, 2003. (pp. 308-313). IEEE.
  23. Pantiuchina, J., Mondini, M., Khanna, D., Wang, X., & Abrahamsson, P. (2017, May). Are software startups applying agile practices? The state of the practice from a large survey. In International Conference on Agile Software Development (pp. 167-183). Springer, Cham.
  24. Parker, J. (2013). Requirements Engineering vs. Business Analysis. Enfocus Solutions. http://enfocussolutions.com/requirements-engineering-vs-business-analysis/
  25. Phil, M. (2015). Comparative analysis of different agile methodologies. International Journal of Computer Science and Information Technology Research Vol3, (1).
  26. PMI, Project Management Institute (2008). A guide to the project management body of knowledge (PMBOK® guide)—Fourth edition. Newtown Square, PA: Author.
  27. PMI, Project Management Institute (2015). Business Analysis for Practitioners: A Practice Guide.
  28. Rubin, K. S. (2012). Essential Scrum: A practical guide to the most popular Agile process. Addison-Wesley.
  29. Runeson, P., Host, M., Rainer, A., & Regnell, B. (2012). Case study research in software engineering: Guidelines and examples. John Wiley & Sons.
  30. Schön, E. M., Thomaschewski, J., & Escalona, M. J. (2017). Agile Requirements Engineering: A systematic literature review. Computer Standards & Interfaces, 49, 79-91.
  31. Schön, E. M., Winter, D., Escalona, M. J., & Thomaschewski, J. (2017, May). Key challenges in agile requirements engineering. In International Conference on Agile Software Development (pp. 37-51). Springer, Cham.
  32. Serrador, P., & Pinto, J. K. (2015). Does Agile work?—A quantitative analysis of agile project success. International Journal of Project Management, 33(5), 1040-1051.
  33. Standish Group CHAOS Report (2015). https://www.standishgroup.com/sample_research_files/CHAOSReport2015-Final.pdf (date accessed: 09.08.2019).
  34. Stellman, A., & Greene, J. (2014). Learning agile: Understanding scrum, XP, lean, and kanban. " O'Reilly Media, Inc.".
  35. Sutherland J., (2013). Requirements for Product Owner: Common Pitfalls. Scruminc. https://www.scruminc.com/requirements-for-product-owner-common/
  36. Sutherland, J., & Schwaber, K. (2016). The scrum guide. The definitive guide to scrum: The rules of the game. Scrum. org, 17.
  37. Vallon, R., da Silva Estacio, B. J., Prikladnicki, R., & Grechenig, T. (2018). Systematic literature review on agile practices in global software development. Information and Software Technology, 96, 161-180.
  38. Wagner, S., Méndez-Fernández, D., Kalinowski, M., & Felderer, M. (2018). Agile requirements engineering in practice: Status quo and critical problems. CLEI Electronic Journal, 21(1), 15.
  39. Wojewoda, S. (2015). Standish Group 2015 chaos report.
  40. Yeo, Y. N., & Hahn, J. (2014). The role of project modularity in information systems development.