Search

This paper explores the Agile methodologies, Scrum and Kanban, to define their advantages and limitations of use. The methods are compared for their use in software development, specifying which would be a suitable option for a game development process focusing on maximizing productivity and quality of the software. Exploration of use cases and methodology guides are discussed, defining the benefits of choosing Kanban or Scrum for a software development team. Findings show Scrum to be a method that focuses on the verbal communication through sprint meetings and reviews. Kanban is described as a visually driven framework that utilizes a Kanban board and cards for communication. Scrum is a strict method can only implement change after a sprint, while Kanban is more flexible and can make changes at any point in the development process. A hybrid of the two methods, Scrumban, is also investigated and found to be an alternative for users who find aspects of both methodologies to be appropriate for their team. There is a great deal of consideration required for independent game developers as they need to reflect on their team dynamics and situation before determining which methodology is best suited for them. [ABSTRACT FROM AUTHOR]