Yazılım Proje Yönetimi: Şelale Modeli ve Çevik Yöntemlerin Karşılaştırılması

Yıl 2017, , 335 - 352, 31.07.2017

Cevriye Gencer , Ali Kayacan

https://doi.org/10.17671/gazibtd.331054

Cited By: 13

Öz

Günümüzde
yazılım, günlük eğlencemizden en karmaşık iş süreçlerine kadar hayatımızın her
alanında yerini almış ve etkileri hissedilen bir olgudur. Şirketler, iş
süreçlerinin yönetimi için etkin yazılım sistemlerine ihtiyaç duyarlar ve bu
sistemleri bilgi sistem departmanları vasıtasıyla üretir ya da yazılım
şirketlerinden tedarik ederler. Her iki durumda da yazılımın üretilmesi bir
dizi mühendislik ve proje yönetim sürecini gerektirir. Bu süreçlerin metodoloji
seçiminde, üretilecek yazılımın büyüklüğü, karmaşıklığı ve kullanım maksadı
gibi karakteristik özellikleri, yazılımı üretecek organizasyon ve proje
ekibinin yapısı ve kullanılabilecek kaynaklar önem arz eder. Bu çalışmada,
şelale modeli ile çevik yöntemler arasında, proje yönetimi ve kontrolü,
müşteriler, organizasyon yapısı, proje elemanları, ürün, gereksinimler,
kaynaklar ve risk yönetimi açısından ortaya çıkan durumlar temel alınarak bir
karşılaştırma ortaya konulmakta ve yazılım proje yönetimi metodolojisi seçimi
konusunda önerilerde bulunulmaktadır.

Anahtar Kelimeler

Şelale Modeli, Çevik Yöntemler, Çevik Metodolojiler, Yazılım Proje Yönetimi

Kaynakça

• 1] Büyük Türkçe Sözlük, http://www.tdk.gov.tr , 10.04.2017. [2] I. Sommerville, Software Engineering, Pearson Education Inc., A.B.D., 2011. [3] Project Management Institute-PMI, A Guide to the Project Management Body of Knowledge (PMBOK® Guide), Project Management Institute-PMI, A.B.D., 2013. [4] Proje, https://tr.wikipedia.org/wiki/Proje , 10.04.2017. [5] Proje Yönetimi, https://tr.wikipedia.org/wiki/Proje_y%C3%B6netimi, 10.04.2017. [6] IEEE Computer Society, SWEBOK v3.0 - Guide to the Software Engineering Body of Knowledge, P.Bourque, R.E.Fairley, IEEE Computer Society Products and Services, A.B.D., 2014. [7] Project Management Institute-PMI, Software Extension to the PMBOK® Guide Fifth Edition, Project Management Institute-PMI, A.B.D., 2013. [8] Standish Group International, CHAOS Report, A.B.D, 2015. [9] N.M.A.Munassar, A.Govardhan, “A Comparison Between Five Models Of Software Engineering”, International Journal of Computer Science Issues - IJCSI, Vol 7, Issue 5, 94-101,2010. [10] NATO Science Committee, Report on Software Engineering Conference, P. Naur, B.Randell, Almanya, 1968. [11] W.W.Royce, “Managing The Development of Large Software Systems”, The Proceedings of the WESCON, San Francisco, A.B.D, 328-339, 1970. [12] M.S.Palmquist, M.A.Lapham, S.Miller, T.Chick, I.Ozkaya, Parallel Worlds: Agile and Waterfall Differences And Similarities, Software Engineering Institute, Carneige Mellon University, A.B.D, 2013. [13] A.Farrell, Selecting a Software Development Methodology Based On Organizational Characteristics, Yüksek Lisans Tezi, Athabasca University, School of Computing and Information Systems, 2007. [14] P.Vohra, A.Singh, “A Contrast and Comparison of Modern Software Process Models”, International Conference on Advances in Management and Technology, Patiala, Hindistan, 23-27,2013. [15] A.Endres, “A Synopsis of Software Engineering History: The Industrial Perspective”, Position Papers for Dagstuhl Seminar 9635 on History of Software Engineering, 1996, 20-24 [16] S.Balaji, M.S.Murugaiyan, “Waterfall vs. V-Model vs Agile: A Comparative Study on SDLC”, International Journal of Information Technology and Business Management, Vol.2, No.1, 26-30, 2012 [17] M.A.Awad, A Comparison Between Agile and Traditional Software Development Methodologies, The University of Western Australia, Avustralya, 2005. [18] The Standard Waterfall Model for Systems Development, http://web.archive.org/web/20040403211247/http://asd-www.larc.nasa.gov/barkstrom/public/The_Standard_Waterfall_Model_For_Systems_Development.htm, 15.04.2017. [19] Disciplined Agile Software Development: Definition, http://www.agilemodeling.com/essays/agileSoftwareDevelopment.htm, 20.04.2017. [20] HP Enterprise, Agile is the new normal, A.B.D, 2017. [21] AgileTurkey, 5th Annual Agility Report, Türkiye, 2016. [22] K.Beck, “Embracing Change with Extreme Programming”, IEEE Computer, Vol. 32, 10 (10), 70-77, 1999. [23] K.Schwaber, “Scrum Development Process”, The proceedings of the OOPSLA’95 Workshop on Business Object Design and Implementation. Springer-Verlag, Texas, A.B.D, 117-134, 1995. [24] R.E.Jeffries, “eXtreme Testing: Why Aggressive Software Development Calls for Radical Testing Efforts”, Software Testing & Quality Engineering, Vol. March/April, 23-26, 1999. [25] A. Cockburn, Surviving Object-Oriented Projects, Addison Wesley, A.B.D., 1998. [26] J.Stapleton, DSDM: Business Focused Development, Addison Wesley, İngiltere, 2003.
• [27] J.A. Highsmith, Adaptive Software Development: A Collaborative Approach to Managing Complex Systems, Dorset House Publishing, A.B.D., 2000. [28] P. Coad, J. De Luca, E. LeFebvre, Java Modeling In Color With UML: Enterprise Components and Process, Prentice Hall, A.B.D., 1999. [29] History: The Agile Manifesto, http://agilemanifesto.org/history.html , 20.04.2017. [30] Çevik Yazılım Geliştirme Manifestosu, http://agilemanifesto.org/iso/tr/manifesto.html, 20.04.2017. [31] J.Fair, “Agile versus Waterfall:approach is right for my ERP Project?”, PMI® Global Congress 2012 EMEA , Marsilya, Fransa,2012. [32] VersionOne Inc., 11th Annual State of Agile Report, A.B.D., 2017. [33] Forrester Research Inc., The 2015 State of Agile Development, A.B.D., 2015. [34] F.Harleen, S.Chande, “A Systematic Study on Agile Software Development Methodologies and Practices”, International Journal of Computer Science and Information Technologies, Vol. 5(3), 3626-3637, 2014. [35] M.E.Lapham, R.Williams, C.Hammons, D.Burton, A.Schenker, Considerations for Using Agile in DoD Acquisition, Software Engineering Institute, Carneige Mellon University, A.B.D, 2013. [36] D.Turk, R.France, B.Rumpe, “Assumptions Underlying Agile Software Processes”, Journal of Database Management, Vol. 16, No.4, 62-87, 2005. [37] D.Turk, R.France, B.Rumpe, “Limitations of Agile Software Processes”, 3rd International Confrence on Extreme Programming and Flexible Processes in Software Engineering- XP 2002, Alghero, İtalya, 43-46, 2002. [38] H.Wells, D.Dalcher, H.Smyth, “The adoption of agile management practices in a traditional Project environment: An IT/IS CaseStudy ”, 48th Hawaii International Conference on System Sciences, Hawaii, A.B.D., 4446-4453, 2015. [39] M.E.Sarıdoğan, Yazılım Mühendisliği, Papatya, İstanbul, Türkiye, 2004. [40] G.v.Waardenburg, H.v.Vliet, “When agile meets the enterprise”, Information and Software Technology, 55, 2154-2171, 2013. [41] D.Edberg, P.Ivanova, W.Kuechler, “Methodology Mashups:An Exploration of Processes Used to Maintain Software”, Journal of Management Information Systems, 28, 4, 271-304, 2012. [42] S.Komai, H.Saidi, H.Nakanishi, “Man-Hour Comparison Between Two Methods of Agile and Waterfall in IT System Development”, Proceedings of the 13th International Conference on Innovation and Management, Wuhan, Çin, 829-836, 2016. [43] K.Dikert, M.Paasivaara, C.Lassenius, “Challenges and success factors for large-scale agile transformations: A systematic literatüre review”, The Journal of Systems and Software, 119, 87-108, 2016.
• [44] A.J.Sohi, M.Hertogh, M. Bosch-Rekveldt, R.Blom, “Does lean & agile project management help coping with project complexity?”, 29th World Congress International Project Management Association, Westin Playa Bonita, Panama, 252-259, 2015. [45] R.Hoda, L.K.Murugesan, “Multi-level agile project management challenges: A self-organizing team perspective”, The Journal of Systems and Software, 117, 245-257, 2016. [46] R.Hoda, J.Noble, S.Marshall, “The impact of inadequate customer collaboration on self-organizing agile teams”, Information and Software Technology, 53(5), 521-534, 2011. [47] T.Dingsøyr, C.Lassenius, “Emerging themes in agile software development: Introduction to the special section on contionuous value delivery”, Information and Software Technology, 77, 56-60, 2016. [48] Y.Macit, E.Tüzün, “Uygulama Yaşam Döngüsü Yönetimi Karşılaştırmalı Süreç İncelemesi”, 9uncu Ulusal Yazılım Mühendisliği Sempozyumu, İzmir, Türkiye, 122-133, 2015. [49] S.Canditt, D.Rauh,M.Wittmann, “Brückenschlag: Das V-Model XT mit Scrum inside”, OBJEKTSpektrum, 5, 2010. [50] M.Hoegl, H.G.Gemuenden, “Teamwork Quality and the Success of Innovative Projects: A Theoretical Concept and Empirical Evidence”, Organization Science, 12 (4), 435-449, 2001. [51] Y.Lindsjørn, D.I.K.Sjøberg, T.Dingsøyr, G.R.Bergersen, “Teamwork quality and project success in software development: A survey of agile deveopment teams”, The Journal of Systems and Software, 122, 274-286, 2016. [52] H.Mintzberg, Mintzberg on Management, The Free Press, A.B.D., 1989 [53] M.Bulu, Nasil Bir Organizasyon Yapisina Ihtiyaciniz Var?, http://www.competitiveturkey.org/trial/melih_bulu_yazi/NasilBirOrganizasyonYapisinaihtiyacinizVar.pdf, 01.05.2017. [54] M.H.Calp, M.A.Akcayol, “Yazılım Projelerinde Karşılaşılan Risk Faktörleri ve Risk Yönetim Süreci”, Marmara Fen Bilimleri Dergisi,1, 1-13, 2015. [55] A.Vaidya, “Does DAD Know Best, Is it Better to do LeSS or Just be SAFe? Adapting Scaling Agile Practices into the Enterprise”, PNSQC 2014 Proceedings, Oregon, A.B.D., 21-38, 2014. [56] K.Katz, “In Defense of Waterfall: Deconstructing the Agile Manifesto”, Better Software Confrence & Expo, Las Vegas, A.B.D., 2009. [57] D.West, M.Gilpin, T.Grant, A.Anderson, “Water-Scrum-fall is the reality of agile for most organizations today”, 2011.