This post about five forces analysis originally appeared on my old blog and Gamasutra. I find that it’s as relevant today as it was then. Mobile is still a hot bed of both independent and publisher-backed development. And for good reason. There is a massive addressable market and mobile devices have high user engagement. Mobile also supports smaller test launches and rapid iteration, meaning that developers and publishers can treat mobile games less like products and more like businesses. Add to that the lack of any marginal production or distribution costs, and you have a super-sexy platform. And that’s exactly the problem. Mobile is so attractive and so accessible that the market place is perhaps the purest example of “perfect competition”, the yin to a monopoly’s yang.
The video games industry is a fertile breeding ground for anxiety and stress. Almost every game is an entrepreneurial endeavor. Expeditionary. And uncertain. Uncertain schedules, uncertain results, uncertain job security. It’s not for the faint of heart. In this article, I’m going to take a break from the usual managerial tone of Breaking The Wheel in order to focus on something more important than any game: your mental health.
This post is a bit of a capstone. It utilizes all of the tools to make video games scientifically that I covered in the Parts 1-6 of “Game Planning With Science”. Make sure you’ve reviewed those weighty tomes before digging in here. In this post, I’m going to walk you through how to utilize capacity charts, story points, user stories, variance, and the central limit theorem to forecast development time lines.
There’s a saying in data science: Garbage In, Garbage Out (or GIGO, if you prefer). The most advanced formulas and models won’t provide outputs worth a dead cat if you don’t have high quality inputs. When it comes to something as difficult and uncertain as feature planning and estimation, that’s quadruply so. In this post I’m going to walk you through the system I’ve used successfully, how it works, and why. And it’s all based on the counter part to the story points from Part 5, user stories.
In Part 4 of “Game Planning With Science!”, I covered the central limit theorem, and how we can use it for forecasting feature development. At the end of the post I acknowledged that it’s no mean feat to track the time per individual feature without some heavy duty project management software and a team that is superlatively disciplined about tracking their time. In Part 5, I’m going to give you my favorite tool for getting around this problem: Story Points.
In Part 4 of “Game Planning With Science”, I’m going to wrap up the statistics primer I started in Part 3. This time, I’ll cover one of the most fascinating aspects of statistics: the Central Limit Theorem. Why does one aspect of statistics deserve its own post? BECAUSE IT’S FRIGGIN’ RAD, THAT’S WHY! Also (and probably more importantly) it allows us to make predictions when planning games, even if we don’t have a lot of data.
In parts 1 and 2 of “Game Planning With Science!” I covered the basics of process management and capacity charts. Now, in Part 3, I’m going to step away from direct operations management to discuss some basic concepts of statistics. Riveting, I know. But also essential if you want to be able to forecast accurately and confidently. There will be some heavy lifting in this post, but hang in there. A better understanding of statistics will change the way you see and treat your own data. It will also make you a more informed consumer of the information the rest of the world vomits at you every day.
In Part 1 of Game Planning With Science, I covered the fundamentals of operations management: critical paths, bottlenecks, and Little’s Law. If you haven’t read Part 1 yet, I suggest you do. Unless you’re familiar with the equations behind those concepts, Part 2 will be a little tricky to follow. But if you’re up to speed, read on. In Part 2, I’m going to walk you through how to assemble a capacity chart. You can use capacity charts to optimize your character art pipelines and add resources where they will do the most good.
The fundamental tools of operations science (also called decision science) were designed with factories and warehouses in mind. But they are easily applicable to video game art asset pipelines. In this post, I’ll walk you through the basics of how operation science looks at pipelines, called “process flows” in operations speak.
One of the sources of crunch is the proverbial kitchen sink: throwing too much content and too many features into a design with too short a production schedule. The reasons can be myriad. Features in competing games. Pressure from publishers or marketing departments. Overblown ambition. The instinct makes sense. As the saying goes, nobody sets out to make a bad game and to that end there is a reluctance to cut corners or make omissions that would compromise quality. But, what if there was a way to cut content and features strategically, so as to make your game more competitive and better serve the needs of your fans? Enter: Strategic Design.