Hi everyone!
I know you probably want more info about the upcoming expansion, but we’ll have to keep a lid on it for the time being. Instead I’m going to give you some information about how we work. Our current team consist of me, Doomdark, 4 programmers (and one of those started last Thursday), 3 scripters, 1 designer, 2 artists and 4 QA. On top of this the talented people from Paradox South are working on a content pack and there is also sound and music in production.
The core team is using a subset of the SCRUM methodology and a lot of focus is put on working more closely with QA than before in order to keep quality as high as possible. Our sprints are 3 weeks, and the final week has a focus on fixing bugs (old and new). Nearing the Gold Master (this is the version of the game we will release), we stop developing new features and focus fully on bug fixing and balancing. Since the Gold Master milestone date and the actual release date usually are a couple of weeks apart, we keep working on bugs and minor improvements for the first patch until the release (and beyond). In some cases (like with Horse Lords) the first patch is released the same day as the expansion, but sometimes it’s better to wait for the initial feedback before releasing a patch. As someone in QA noted for Horse Lords: one day after the release the players have tested the game several more hours than the QA team has done during the development of the expansion.
A tidbit of extra info about the expansion: the changes that go into the patch will fundamentally change how a portion of the game is played.
I know you probably want more info about the upcoming expansion, but we’ll have to keep a lid on it for the time being. Instead I’m going to give you some information about how we work. Our current team consist of me, Doomdark, 4 programmers (and one of those started last Thursday), 3 scripters, 1 designer, 2 artists and 4 QA. On top of this the talented people from Paradox South are working on a content pack and there is also sound and music in production.
The core team is using a subset of the SCRUM methodology and a lot of focus is put on working more closely with QA than before in order to keep quality as high as possible. Our sprints are 3 weeks, and the final week has a focus on fixing bugs (old and new). Nearing the Gold Master (this is the version of the game we will release), we stop developing new features and focus fully on bug fixing and balancing. Since the Gold Master milestone date and the actual release date usually are a couple of weeks apart, we keep working on bugs and minor improvements for the first patch until the release (and beyond). In some cases (like with Horse Lords) the first patch is released the same day as the expansion, but sometimes it’s better to wait for the initial feedback before releasing a patch. As someone in QA noted for Horse Lords: one day after the release the players have tested the game several more hours than the QA team has done during the development of the expansion.
A tidbit of extra info about the expansion: the changes that go into the patch will fundamentally change how a portion of the game is played.
I'd be more curious to learn what CK2's design pillars are, for example.
.png){kind=avatar}
