Project management update

Hey guys!  Last week I had a call with Thalion, a supporter of the game, and a web developer and project manager with 19 years’ experience.  He had some analysis of the way I was working and some suggestions.  

In a way, the bad news is I wasn’t doing anything awful – there wasn’t a simple fix he could see that would drastically speed up production.  The to-do list was well organised, and progress (for a solo developer) was quite good on the basis of what I achieved each day.

Thalion’s suggestions (short term)
He did suggest some improvements to the way I’m organising and managing tasks – mainly going back to using a simple kanban board.  This is something I experimented with before, earlier in development, but I found a bit too finickity to maintain, and I let it fizzle out.

However, Thalion suggested a simplified setup and gave me some new advice on how to use it – some tips on prioritisation, workflow, and which advanced things (like Story Points) I could ignore for the moment.  He thinks it’ll improve efficiency and reporting.

Thalion’s suggestions (future episodes)
Having played the alpha test version of Malaysia, he also suggested that the next episode should get released in smaller chunks (at least as beta tests).  This would allow the community to see what I’m working on, me to get feedback from the community, and might make art taskings more efficient.  I think it’s a good idea and I’ll try it in the next episode.

I can kanban
So today I converted all the remaining tasks to “tickets” and set up a new kanban board.  The game’s illustrator lovely Victoria and I each have about a dozen tickets to work through, then you can play it.  🦀❤️‍🔥