Comments on: Fun Over Features – Manifesto for Agile Game Development http://www.doolwind.com/blog/fun-over-features-manifesto-for-agile-game-development/ Pragmatic Thoughts On Game Development Mon, 30 Aug 2010 16:41:07 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: david http://www.doolwind.com/blog/fun-over-features-manifesto-for-agile-game-development/comment-page-1/#comment-857 david Wed, 17 Mar 2010 22:06:12 +0000 http://www.doolwind.com/blog/?p=470#comment-857 Hi Alistair, I'm still bemused as to what a ScrumMaster is - but i'm assuming it has little to do with rugby league :) Hi Alistair,
I’m still bemused as to what a ScrumMaster is – but i’m assuming it has little to do with rugby league :)

]]> By: guptan http://www.doolwind.com/blog/fun-over-features-manifesto-for-agile-game-development/comment-page-1/#comment-856 guptan Wed, 17 Mar 2010 14:35:45 +0000 http://www.doolwind.com/blog/?p=470#comment-856 fun is a quality measure and it is subjective; how can it be measured and before release itself to find the features:fun :: cost:benefit? using polls? fun is a quality measure and it is subjective; how can it be measured and before release itself to find the
features:fun :: cost:benefit? using polls?

]]> By: Heather McLean http://www.doolwind.com/blog/fun-over-features-manifesto-for-agile-game-development/comment-page-1/#comment-855 Heather McLean Wed, 17 Mar 2010 13:34:42 +0000 http://www.doolwind.com/blog/?p=470#comment-855 Looks like a sound principle to me. :) In the world of business software, I would translate this to "usability over features." I.e., focus on making software that's easy for the customer and does what they want as opposed to throwing in everything and the kitchen sink in the hopes that the customer will like it. I've seen many projects on the road to failure because the management or team wanted to add every "killer feature" on the list instead of paying attention to what's best for the end user. Looks like a sound principle to me. :) In the world of business software, I would translate this to “usability over features.” I.e., focus on making software that’s easy for the customer and does what they want as opposed to throwing in everything and the kitchen sink in the hopes that the customer will like it. I’ve seen many projects on the road to failure because the management or team wanted to add every “killer feature” on the list instead of paying attention to what’s best for the end user.

]]> By: James Bowling http://www.doolwind.com/blog/fun-over-features-manifesto-for-agile-game-development/comment-page-1/#comment-854 James Bowling Wed, 17 Mar 2010 09:28:13 +0000 http://www.doolwind.com/blog/?p=470#comment-854 That's an interesting way to think about it. It's easy to come up with cool feature(creep)s as we go, but thinking about some rough quantification seems like a good strategy. I definitely want to get a simple and streamlined set of features solid and fun before going too crazy with anything else. With the project I'm currently working on, I think we've been doing a decent job of staying focused on the core fun, but still, something worth being aware of. It does make me think to look at features more objectively, and separate out the ones that are part of the core set, from the periphery. That’s an interesting way to think about it. It’s easy to come up with cool feature(creep)s as we go, but thinking about some rough quantification seems like a good strategy.

I definitely want to get a simple and streamlined set of features solid and fun before going too crazy with anything else. With the project I’m currently working on, I think we’ve been doing a decent job of staying focused on the core fun, but still, something worth being aware of.

It does make me think to look at features more objectively, and separate out the ones that are part of the core set, from the periphery.

]]>