Update process?

[Dimetime35c]

Okay I've been wondering. What is the actual process that is used to create a update to the game? Say .23 cause from an outsiders point of view how would you pick what to tackle, I'd try and do everything that needed doing and never get an update out.

[Pecan]

An early agile software development method (DSDM) defined what is known as the MoSCoW rules for defining the scope of a release:

Must Haves - there's no point to the release without any of these

Should haves - important but not essential

Could haves - while we're at it, it's easy to do this

Would likes - write a letter to santa

Once you have a list like that the 'timebox' approach is to take the time it will need (with testing, etc) to include the top/most do-able 'must haves' (which define the release). Add on a bit of time for one or two easier 'should haves' and contingency and say "that's when we'll release". Any unused contingency (you planned well) is used for a 'could have' or maybe even a 'would like' if one of the developers feels like it. If you run out of time you release with what you've got, as long as it includes at least one 'must have'. This approach is particularly useful where you have to co-ordinate and schedule with outside teams/agencies because you're telling them exactly when you'll be ready (if not what they'll get ^^).

An alternative is the 'workbox' approach where you decide on very specific functions that will be included but can't estimate how long it'll take (perhaps you know you have to have multiplayer but you don't even know where to start yet). In this you say "It'll be ready when it's ready" - and people know what to expect, but not when. This is useful if you have long lead-times on things like printing manuals and publicity as they can plan accordingly.

In practice, of course, it's usually a bit of both and, in any case, modern agile methods are designed to allow for changes as you go along.

The older methods came from physical engineering and construction and mean you spend most of your time in planning meetings and by the time you make something it isn't what you'd intended or the customer wants any more.

[incidentally - you might like to ask this in the modding forum - all those poor developers get requests for additions and changes all the time and have to work out what they can do, when]

Edited March 6, 2014 by Pecan

[blizzy78]

all those poor developers get requests for additions and changes all the time and have to work out what they can do, when

Or IF, if you don't mind me adding that.

[FITorion]

From what I've gleaned from watching this game for a while...

They have a meeting ... or a few meetings... where they discuss what they will put into the next update after they've finished the current update. Items consist of must haves and at least one nice to have item. Then they go off and do that and each person or persons tests as best they can their piece. Then everything gets integrated together and it goes to the testing team. Bugfixing... then release.

[sal_vager]

Ted's blog should help here, take a look