Agile Methods in Game Programming based on Scrum

Abstract

Game programming requirements, which is one of the problems of game programming in recent times, is constantly changing. Therefore, the process we are conducting while programming the game does not keep up with this change leads to the failure of the product we develop or the result of higher costs. Therefore, the use of agile programming, which brings a more dynamic and modern solution to changing environment conditions, is increasing day by day and the project teams are transitioning to these processes. In this thesis, firstly historical development, content, rules and methods of Agile methods are presented with literature researches. In the next section, Grumpy Ball is applied by using Scrum method which is agile programming method. Since the agile methods provide dynamic solutions, an end date cannot be determined Therefore, the aim of this article is to determine the exact date of a game application using agile method. For this reason, our project is divided into specific parts and the last periods given to these parts were compared according to certain criteria. In the light of the results, determinations were made.

Keywords

• agile methods
• game programming process
• game project management
• scrum

References

1. Abrahamsson, P., Salo, O., Ronkainen, J., & Warsta, J. (2017). Agile software development methods: Review and analysis. arXiv preprint arXiv:1709.08439.
2. Baytam, V., & Kalıpsız, O. (2011). Scrum Software Development Model Management Tool ScrumMApp. Fifth National Software Engineering Symposium, September (in Turkey).
3. Beck, K., Beedle, M., Van Bennekum, A., Cockburn, A., Cunningham, W., Fowler, M., & Kern, J. (2001). Manifesto for agile software development.
4. Boehm, B. (2002). Get ready for agile methods, with care. Computer, (1), 64-69.
5. Duru, I. (2014). Design and implementation of mobile applications in agile methods (in Turkey).
6. Grenning, J. (2001). Launching extreme programming at a process-intensive company. IEEE Software, 18(6), 27-33.
7. Highsmith, J. (2002). What is agile software development?. crosstalk, 15(10), 4-10.
8. Hundermark, P. (2009). Do better scrum. ScrumSense: http://www. scrumsense. com/wp-content/uploads/2009/12/DoBetterScrum-v2. pdf.

9. Landaeta, R. E., Viscardi, S., & Tolk, A. (2011, June). Strategic management of scrum projects: An organizational learning perspective. In First International Technology Management Conference (pp. 651-656). IEEE.
10. Lippert, M., Becker-Pecbau, P., Breitling, H., Koch, J., Kornstadt, A., Roock, S., ... & Zullighoven, H. (2003). Developing complex projects using XP with extensions. Computer, 36(6), 67-73.
11. Reifer, D. J., Maurer, F., & Erdogmus, H. (2003). Scaling agile methods. IEEE software, 20(4), 12-14.
12. Sahin, E., Keskin, I., & Koç, H. (2013). Implementation of SCRUM Agile Software Development Method in Software Development Works in an Organization with CMMI-DEV Level-3 Certification. In UYMS (in Turkey).
13. Schwaber, K. (1997). Scrum development process. In Business object design and implementation (pp. 117-134). Springer, London.
14. Schwaber, K., & Sutherland, J. (2009). Scrum guide: developed and sustained. Scrum. org.
15. Sutherland, J. (2004). Agile development: Lessons learned from the first scrum. Cutter Agile Project Management Advisory Service: Executive Update, 5(20), 1-4.
16. Sutherland, J. V., & Schwaber, K. (1995). The SCRUM methodology. In Business object design and implementation: OOPSLA workshop.
17. Sutherland, J., & Schwaber, K. (2010). The Scrum Papers: Nuts, Bolts and Origins of an Agile Process (2007). [18] Süloğlu, S. (2005). When the method is agile (in Turkey).
18. Takeuchi, H., & Nonaka, I. (1986). The new new product development game. Harvard business review, 64(1), 137-146.