Waterfall Game Development Done Right

[Nando]

http://www.gamasutra.com/view/feature/181992/Waterfall_Game_Development_Done_Right.php?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+GamasutraFeatureArticles+%28Gamasutra+Feature+Articles%29


Agile, Agile, Agile. It's hard to disagree with a project management process named "Agile". It's like disagreeing with something named the "Patriot Act" or answering "No" to a department store checkout attendant that asks if you would like to save 20 percent on today's purchase. It's clear: Agile is cool, and every Scrum master certificate mill will agree with that statement.

But what happens when an Agile paradigm isn't appropriate?

"How is that possible?" says the guy with the skinny jeans and the PBR.

There are two scenarios where we think a more "waterfally" approach is appropriate (We'll explain the "more" part later... because no one could ever be purely waterfall if you think the name implies a rigid schedule).

The first is when a project is innately low-risk, and the second is when your stakeholder doesn't wholeheartedly buy into the Agile process. Examples of the second include Kickstarter and the majority of contract work.

more at the link

[Arkhan Asylum]

skinny jeans and pbr made me lol.

Agile development is fucking lame.  Scrum is stupid.

[OldRover]

Honestly, I got bored trying to read that article and couldn't finish it.

[ccovell]

I would say this is just off-topic and needs to be moved.

[Nando]

skinny jeans and pbr made me lol.

Agile development is fucking lame.  Scrum is stupid.

Maybe to you Arkface! it is all relative of course. At work, our dev's and QA Teams switched to an Agile method and it's actually working for us way better this way. They don't fully follow the methodology but it's working

Chris,

I disagree. I think any and all information about development models can help any number of homebrewers; perhaps more towards the younger/green end of the spectrum, but I think relevant none the less.