Backlog and Kanban

Having got Bobbie on my team, renamed the game and formed a brief outline of what needs to be done in the project, it was time to form a giant backlog of what really needs to be done, so we can organise ourselves.


Both myself and Bobbie sat down and worked together to try to write down all the tasks that needed to be done for the project. We did this so we had a clear outline of the amount of tasks needed to be done, the amount of roles needed, and to help us get an idea of what we felt would be feasibly possible. We arranged the backlog into a KanBan structure with a ‘To Do’, ‘Doing’ and ‘Done’ header so throughout the project we would know what we had, hadn’t and were in the process of achieving. Helping us better visualise how the game would be progressing during the project, so we could make alterations to our plan or overall goals if we could see tasks weren’t being completed/ too many tasks etc. Overall just ensuring we keep on track on the project and how it is running and progressing.



As planned previously within our first meeting, Bobbie and I created a Kanban wall of all the tasks we felt needed to be competed during the project to get a game created.











Personally I don’t feel its fully complete and there will be jobs that we will have missed off of the list or haven’t fully expanded, due to our differing work styles (explained below) and the fact that we are unsure of what issues may occur the project and so extra roles of research may nee to be completed to solve problems. But I feel as long as we keep this in mind when forming a timeline for the whole project, leaving extra time to solve issues this shouldn’t become a major issue within the scheme of things and we should keep on track.


From this process it has already made me realise how differently we both work, with Bobbie preferring to briefly write down titles of what needs going eg Character designs, but I prefer to breakdown the tasks into smaller tasks of what I would actually do, eg Initial Character designs, experiments, digital drawings, feedback, and refinement of designs, so I know exactly what that means and what either myself of Bobbie would need to do for it. So I think this shows I like to plan everything to a T and ensure I know exactly what needs doing, whereas Bobbie works best just knowing an outlined plan of the project. This contrasting work style may cause some planning or communication issues later down the line, with one not understanding what the other is doing and so may miss something out or do work which isn’t right/ necessary. However I think as long as we ensure we both verbally communicate daily and try to listen and understand what the other is doing we should hopefully avoid any major issues.



  • Discussion and finalisation of roles – Though we had briefly discussed our roles with Bobbie taking more of a coding lead and myself an art one, however I believe we need to finalise these roles exactly, especially now we have marketing and project managing roles involved too. So I feel a dicussion between us highlighting what we feel are strengths are and what we are willing to do will help us define what each othrs roles are, ensuring we don’t become confused in the future.
  • Sprint 1 Plan – After forming the backlog and our goals for the game, myself and Bobbie wil need to discuss what needs to be achieve first within the starting sprint.
  • Project Timeline – Having completed the backlog and knowing when the deadline is I feel we need to start solidifying down a timeline for the project, working out what we want to achieve overall and setting benchmarks throughout the project to meet these deadlines.