Araştırma Makalesi
BibTex RIS Kaynak Göster

BİLİŞİM SİSTEMİ YAZILIM GELİŞTİRME SÜRECİNDE KULLANILAN ŞELALE VE SCRUM YÖNTEMLERİNİN KARŞILAŞTIRILMASI VE KARMA YÖNTEMİN İNCELENMESİ

Yıl 2021, Cilt: 7 Sayı: 1, 24 - 43, 07.07.2021

Öz

Günümüzde özel işyerlerinde veya kamuda kısacası her yerde birçok işlem bilgi sistemi ile yapılmaktadır. Dolayısı ile bilgi sistemine olan talep çok artmıştır ve ilerleyen zamanda daha da çok artacaktır. Yönetim bilgi sistemi olsun başka sistemler olsun geliştirme aşamalarında farklı yazılım yaşam döngüsünden geçerek son ürün haline gelmektedir. 1970’li yıllarda ortaya konulan şelale yönteminden günümüzde yoğun bir şekilde kullanılan scrum yöntemine kadar çok farklı çeşidi bulunmaktadır. Ancak günümüzde bilgi sistemine olan talep arttığından dolayı bu talebe hızlı bir şekilde cevap verecek olan çevik yazılım geliştirme yöntemlerine doğru bir geçiş yaşanmaktadır. Bazı durumlarda da her yöntemin iyi yanını alıp karma yöntemler uygulamak daha faydalı olabilmektedir. Bu çalışmanın amacı farklı bilişim sistemi geliştirme yöntemlerinin karşılaştırılması ve bu yöntemlerin karması hakkında değerlendirmeler yapmaktır. Uygulama kısmında ise şelale yönteminden scrum yöntemine geçişte dikkat edilmesi gereken hususlar ele alınmıştır. Ayrıca, her iki yöntemin karması olan yöntem de değerlendirilmiştir.

Kaynakça

  • Agile Extension to the BABOK Guide (2017). International Institute of Business Analysis (IIBA) Agile Alliance.
  • Agile Practice Guide (2017). Project Management Institute, Inc.
  • AgileTurkey (2019). 8th Annual Agility Report. Türkiye, Rap. Agile Turkey:1.
  • Balaji S. ve Murugaiya M. S. (2012). Waterfall vs. V-Model vs Agile: A comparative study on SDLC. International Journal of Information Technology and Business Management, 2(1): 26-30.
  • Beck K., Beedle M. ve Bennekum A. (2001). Çevik yazılım geliştirme manifestosu. http://agilemanifesto.org/iso/tr/manifesto.html (01 Mayıs 2020).
  • Beck K., Beedle M., Bennekum A., Cockburn A., Cunnigham W., Fowler M., Grenning J., Highsmith J., Hunt A., Jeffries R., Kern J., Marick B.,
  • Martin R. C., Mellor S., Schwaber K., Sutherland J., Thomas D. (2001). Çevik yazılımın onki prensibi. http://agilemanifesto.org/iso/tr/principles (01 Mayıs 2020).
  • Bhavsar K., Shah V. ve Gopalan S. (2020). Scrumbanfall: An Agile Integration of Scrum and Kanban with Waterfall in Software Engineering. International Journal of Innovative Technology and Exploring Engineering (IJITEE). 9(4): 2075-2084.
  • Boehm B. ve Turner R. (2003). Rebalancing Your Organization’s Agility and Discipline, Third XP and Second Agile Universe Conference, New Orleans, USA.
  • Business Analysis Body of Knowledge (BABoK) A Guide to Business Analysis Body of Knowledge (2015). International Institute of Business Analysis.
  • Davis B. ve Radford D. (2014). Going Beyond The Waterfall Managing Scope Effectively Across the Project Life Cycle içinde 145-160. Plantation, Florida, USA, J.Ross Publishing.
  • Forrester (2011). Water-Scrum-Fall Is The Reality Of Agile For Most Organizations Today - Manage The Water-Scrum And Scrum-Fall Boundaries To Increase Agility Report., Cambridge, USA, Rep. Forrester:262011.
  • Gencer C. ve Kayacan A. (2017). Yazılım proje yönetimi: şelale modeli ve çevik yöntemlerin karşılaştırılması. Bilişim Teknolojileri Dergisi, 10 (3): 335-352.
  • Guide to the Software Engineering Body of Knowledge (SWEBOK) (2014). IEEE Computer Society.
  • Hewlett Packard (HP) Enterprise. (2017). Agile is the new normal, Adopting Agile project management. (01 Mayıs 2020) https://softwaretestinggenius.com/docs/4aa5-7619.pdf.
  • Mahalakshmi M. ve Sundararajan D. M. (2013). Traditional SDLC Vs scrum methodology – a comparative study. International Journal of Emerging Technology and Advanced Engineering, 3(6): 192-196.
  • Palmquist M. S., Lapham M. A., Miller S., Chick T. ve Ozkaya I. (2013) Parallel Worlds: Agile And Waterfall Differences And Similarities, 1. baskı, Massachusetts, ABD: Carnegle Mellon University.
  • Royce W. W. (1970). Managing The Development of Large Software Systems, IEEE WESCON, 1 (2): 1-9.
  • Schwaber K. ve Sutherland J. (2017) Scrum Kılavuzu - Scrumın Tanımlayıcı Kılavuzu: Oyunun Kuralları, Türkçe’ye çeviren Agile Turkey.
  • Singhto W. ve Phakdee N. (2016). Adopting a combination of Scrum and Waterfall methodologies in developing Tailor-made SaaS products for Thai Service and manufacturing SMEs. 2016 International Computer Science and Engineering Conference (ICSEC), Chiang Mai, Thailand.
  • Software Extension To The PMBOK Guide (2013). Project Management Institute, IEEE Computer Society.
  • Sommerville I. (2016). Software Engineering, Harlow, England, Pearson.
  • Systems and software engineering — Life cycle processes (2018). Requirements engineering ISO/IEC/ IEEE 29148.
  • Systems and software engineering — Life cycle processes (2011). Requirements engineering ISO/IEC/ IEEE 29148.
  • Systems and software engineering — Software life cycle processes (2017). ISO/IEC/ IEEE 12207.
  • Systems and software engineering — System life cycle processes (2015). ISO/IEC/ IEEE 15288.
  • The Standish Group (2018). Chaos Report. The Standish Group, USA, Rep. The Standish Group: 1.
  • Vohra P. ve Singh A. (2013). A contrast and comparison of modern software process models. International Conference on Advances in Management and Technology, Patiala, Hindistan.

COMPARISON OF WATERFALL AND SCRUM METHODS IN INFORMATION SYSTEM SOFTWARE DEVELOPMENT PROCESS AND EXAMINATION OF MIXED METHOD MANAGEMENT

Yıl 2021, Cilt: 7 Sayı: 1, 24 - 43, 07.07.2021

Öz

Nowadays, many transactions are carried out with information systems in private workplaces or public places. Consequently, the demand for the information system has increased and will increase even more in the future. Be it the management information system or other systems, it goes through a different software life cycle in the development stages and becomes the final product. There are many different types, from the waterfall method introduced in the 1970s to the scrum method, which is used extensively today. However, today, due to the increasing demand for the information system, there is a transition towards agile software development methods that will quickly respond to this demand. In some cases, it may be more beneficial to take the good side of each method and apply mixed methods. The aim of this study is to compare different information system development methods and evaluate the mix of these methods. In the application part, the issues to be considered in the transition from the waterfall method to the scrum method are discussed. In addition, the method, which is a mixture of both methods, was also evaluated.

Kaynakça

  • Agile Extension to the BABOK Guide (2017). International Institute of Business Analysis (IIBA) Agile Alliance.
  • Agile Practice Guide (2017). Project Management Institute, Inc.
  • AgileTurkey (2019). 8th Annual Agility Report. Türkiye, Rap. Agile Turkey:1.
  • Balaji S. ve Murugaiya M. S. (2012). Waterfall vs. V-Model vs Agile: A comparative study on SDLC. International Journal of Information Technology and Business Management, 2(1): 26-30.
  • Beck K., Beedle M. ve Bennekum A. (2001). Çevik yazılım geliştirme manifestosu. http://agilemanifesto.org/iso/tr/manifesto.html (01 Mayıs 2020).
  • Beck K., Beedle M., Bennekum A., Cockburn A., Cunnigham W., Fowler M., Grenning J., Highsmith J., Hunt A., Jeffries R., Kern J., Marick B.,
  • Martin R. C., Mellor S., Schwaber K., Sutherland J., Thomas D. (2001). Çevik yazılımın onki prensibi. http://agilemanifesto.org/iso/tr/principles (01 Mayıs 2020).
  • Bhavsar K., Shah V. ve Gopalan S. (2020). Scrumbanfall: An Agile Integration of Scrum and Kanban with Waterfall in Software Engineering. International Journal of Innovative Technology and Exploring Engineering (IJITEE). 9(4): 2075-2084.
  • Boehm B. ve Turner R. (2003). Rebalancing Your Organization’s Agility and Discipline, Third XP and Second Agile Universe Conference, New Orleans, USA.
  • Business Analysis Body of Knowledge (BABoK) A Guide to Business Analysis Body of Knowledge (2015). International Institute of Business Analysis.
  • Davis B. ve Radford D. (2014). Going Beyond The Waterfall Managing Scope Effectively Across the Project Life Cycle içinde 145-160. Plantation, Florida, USA, J.Ross Publishing.
  • Forrester (2011). Water-Scrum-Fall Is The Reality Of Agile For Most Organizations Today - Manage The Water-Scrum And Scrum-Fall Boundaries To Increase Agility Report., Cambridge, USA, Rep. Forrester:262011.
  • Gencer C. ve Kayacan A. (2017). Yazılım proje yönetimi: şelale modeli ve çevik yöntemlerin karşılaştırılması. Bilişim Teknolojileri Dergisi, 10 (3): 335-352.
  • Guide to the Software Engineering Body of Knowledge (SWEBOK) (2014). IEEE Computer Society.
  • Hewlett Packard (HP) Enterprise. (2017). Agile is the new normal, Adopting Agile project management. (01 Mayıs 2020) https://softwaretestinggenius.com/docs/4aa5-7619.pdf.
  • Mahalakshmi M. ve Sundararajan D. M. (2013). Traditional SDLC Vs scrum methodology – a comparative study. International Journal of Emerging Technology and Advanced Engineering, 3(6): 192-196.
  • Palmquist M. S., Lapham M. A., Miller S., Chick T. ve Ozkaya I. (2013) Parallel Worlds: Agile And Waterfall Differences And Similarities, 1. baskı, Massachusetts, ABD: Carnegle Mellon University.
  • Royce W. W. (1970). Managing The Development of Large Software Systems, IEEE WESCON, 1 (2): 1-9.
  • Schwaber K. ve Sutherland J. (2017) Scrum Kılavuzu - Scrumın Tanımlayıcı Kılavuzu: Oyunun Kuralları, Türkçe’ye çeviren Agile Turkey.
  • Singhto W. ve Phakdee N. (2016). Adopting a combination of Scrum and Waterfall methodologies in developing Tailor-made SaaS products for Thai Service and manufacturing SMEs. 2016 International Computer Science and Engineering Conference (ICSEC), Chiang Mai, Thailand.
  • Software Extension To The PMBOK Guide (2013). Project Management Institute, IEEE Computer Society.
  • Sommerville I. (2016). Software Engineering, Harlow, England, Pearson.
  • Systems and software engineering — Life cycle processes (2018). Requirements engineering ISO/IEC/ IEEE 29148.
  • Systems and software engineering — Life cycle processes (2011). Requirements engineering ISO/IEC/ IEEE 29148.
  • Systems and software engineering — Software life cycle processes (2017). ISO/IEC/ IEEE 12207.
  • Systems and software engineering — System life cycle processes (2015). ISO/IEC/ IEEE 15288.
  • The Standish Group (2018). Chaos Report. The Standish Group, USA, Rep. The Standish Group: 1.
  • Vohra P. ve Singh A. (2013). A contrast and comparison of modern software process models. International Conference on Advances in Management and Technology, Patiala, Hindistan.
Toplam 28 adet kaynakça vardır.

Ayrıntılar

Birincil Dil Türkçe
Bölüm Makaleler
Yazarlar

Doğan Yıldız 0000-0002-0946-7251

Erken Görünüm Tarihi 8 Temmuz 2021
Yayımlanma Tarihi 7 Temmuz 2021
Yayımlandığı Sayı Yıl 2021 Cilt: 7 Sayı: 1

Kaynak Göster

APA Yıldız, D. (2021). BİLİŞİM SİSTEMİ YAZILIM GELİŞTİRME SÜRECİNDE KULLANILAN ŞELALE VE SCRUM YÖNTEMLERİNİN KARŞILAŞTIRILMASI VE KARMA YÖNTEMİN İNCELENMESİ. Yönetim Bilişim Sistemleri Dergisi, 7(1), 24-43.