@GTD, yes, user stories might be too unspecific for game development, but there’s no law against more exact specifications. In fact if I were to start a SCRUM game project, I’d do two or three sprints on just the initial design before letting any code to be written. The programmers and game designers need to reach an agreement on what the game needs to be like and what is technically possible. At least an agreement to a degree.

Strict and iron fisted bosses can be bad for agile, right, but they can be bad for waterfall or anything actually if they don’t really understand the process or the product. But to have a strict and iron fisted SCRUM Master …

Agile can work with deadlines, and there is no reason why unplanned things should happen during a sprint. These days ‘alpha’ and ‘beta’ are simply marketing terms.

That is comedy gold. Agile works no matter what size your project is. They probably don’t use it because they don’t understand it, when in fact its the perfect system for a games developer with multiple teams. I know, because I’ve used it when working on AAA MMOs.

It’s all about Wargaming bottom line now isn’t it? If historical reality was a priority to Wargaming, the S-tank would a part of the EU/Sweden tank tree from the start.

Considering Wargaming already has spoken about design and testing new ‘larger maps’…. What’s the deal with a claim a new mechanism would have to be built? So what? Isn’t that what computer software designers & gaming directors do for a living: Designing, Testing, Creating/Building, Enabling? New maps mean starting over already. Newly redesigned tank models mean every tank will be redone.

So what’s the hold back on the Swedish S-tank?
Does Serb’s Soviet era fondness & a love of money biased his supposed love for a historical reality of tanking, and what can be considered of an apex of Sweden tank design?

Wonder if that other Russian gaming company can do what Wargaming isn’t interested in doing?
Seriously.

——————-

- S-Tank will not be implemented into WoT, because the developers would have to implement a mechanism especially for it. But if it was ever implemented, it would be a TD.

Waterfall Requirements, Design, Development, Testing, Deployment to consumer

Agile: Design, Test, Integration, Test, Development, Test, repeat.

In short the developers using the Agile method are able to respond to changes faster but use more time iterating on the design.

But hey, I understand; he has an awesome steady job, is extremely knowledgeable about tanks, writes neat articles, makes neat videos. I can see why you would be so jealous of him as to come into the comments section and act like a butthurt little kid.