Comparing the Kanban and Waterfall Methodologies

 

When working with a team in the games industry it is a good idea to control and monitor the production process. Having a structure in place that dictates the speed that work is completed and what is to be prioritised helps to make the development process as smooth and predictable as possible. There are many different project management methodologies that teams can choose from that offer tried and tested ways to work efficiently. Two examples of this are the Kanban and Waterfall methodologies. These methodologies offer two dissimilar methods of project management; Kanban is a more flexible method whereas Waterfall is a simpler, rigid method. There is no ‘best’ methodology. It is important to pick a methodology that works with your project and team.

 

Kanban is a methodology based on Agile principles. What this means, in short, is that the production process is “a flexible, iterative design and build process”. (Digital Project Manager, Ben Aston 15/1/21) It encourages teams to adapt to changes in production rather than stick to a rigid plan. Kanban focuses on having a clear backlog of tasks, limiting work in progress and identifying issues with the production process to change. In practice, Kanban teams will often use sites like Trello to clearly organise work into ‘to-do’, ‘doing’ and ‘done. This makes it easy to see what needs to be done and helps to create a steady output of completed work. Kanban also has a focus on the time it will take to complete tasks, called ‘Lead Time’: “how long it takes, after being briefed, to deliver” (Digital Project Manager, Ben Aston 15/1/21). Compared to similar methodologies such as Scrum, it offers a more relaxed approach to following Agile principles; “flexible enough to continuously adapt ; still robust enough to avoid people disperse their energy around” (Nicolas Carlo, 26 Jan 2016 “Kanban and Game Development with Trello”)

 

Waterfall, on the other hand, contrasts Kanban by not following Agile principles. It is a very simple methodology with a focus on strong planning and a rigid structure. The production is extensively planned from start to finish without deviation. Tasks are put in phases and completed in order, requiring all the work in one phase to be completed before moving on. Unlike Kanban, there is no room for changes or reflection. If it becomes apparent that something was not well designed in the concept phase, it is very difficult to change it at a later phase. Waterfall may sound like a useless methodology, but it can work for some projects that would not benefit from using Agile. Projects that are low risk or that are not trying to create a very original idea do not have much need for Agile. “I think you can throw out any game development scenario where you are striving to achieve fun that isn't a full clone of something that is already proven to be fun” (Eric Preisz, Gamasutra.com, 21/11/12 ). Having a low risk project can include making a product that is already proven, such as a sequel of a game or one that uses many proven ideas. Waterfall also makes it easier to see the budget, timeline and scope, something that methods like Kanban might have issues with due to frequent iteration and looser planning. 

 

To summarise, the Kanban and Waterfall methodologies arevery different methodologies from each other that can both work in specific circumstances. However, I think that Kanban is the more appropriate methodology for game development. The use of Agile principles encourage frequent reflection, iteration and changes that will more often than not create a better end product. It would work especially well for indie developers with a higher risk project, or companies that are not relying on replicating ideas or producing sequels. Waterfall does have it’s place in smaller, low risk projects; but in most cases leaves little room for creativity or making vital changes for the sake of sticking to a rigid structure. 

 

Eric Preisz, Gamasutra.com, “Waterfall Game Development Done Right” 21/11/12 https://www.gamasutra.com/view/feature/181992/waterfall_game_development_done_.php

 

Nicolas Carlo, 26/1/16 “Kanban and Game Development with Trello” https://www.nicoespeon.com/en/2016/01/kanban-game-development-trello/)

 

Ben Aston, 15/1/21, Digital Project Manager.com “9 Of The Most Popular Project Management Methodologies Made Simple”

https://thedigitalprojectmanager.com/project-management-methodologies-made-simple/