tag:blogger.com,1999:blog-11485756.post967803421322867903..comments2011-07-25T22:07:39.176+02:00Thomas Ferris Nicolaisenhttps://profiles.google.com/101470099289717563604noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-11485756.post-8483029409739565562011-05-30T14:58:57.598+02:002011-05-30T14:58:57.598+02:00it was realy wonderful blog..!rohinihttp://gamecloud-ltd.comnoreply@blogger.comtag:blogger.com,1999:blog-11485756.post-33046372919459908232011-05-09T17:36:31.474+02:002011-05-09T17:36:31.474+02:00For those interested, Arrowhead posted <a href="http://pilestedt.tumblr.com/post/5334896526/on-magicka-agile-development" rel="nofollow">a reply to this post here</a>.Thomas Ferris Nicolaisenhttp://www.blogger.com/profile/17464665832399025601noreply@blogger.comtag:blogger.com,1999:blog-11485756.post-18104668109120224732011-04-30T19:29:02.101+02:002011-04-30T19:29:02.101+02:00Hi Clinton, thanks for the comment!<br /><br />Wow, I had no idea there&#39;s a book on the subject, with the exact same title even :)<br /><br />You&#39;re right about that, of course. And the developers openly admit this in retrospect (listening to <a href="http://www.youtube.com/watch?v=YaJgi-NJGuk&amp;feature=list_related&amp;playnext=1&amp;list=SP295A49D9210D37C9" rel="nofollow">their vods with Total Biscuit</a> you pick up a lot of interesting facts).<br /><br />I think all the way through, the devs acted to the best of their knowledge (probably some pressure from the publisher), and as as soon as they realized that quality was below par for the general public, they adapted: focused on increasing stability, daily releasing patches to remove bugs.<br /><br />An interesting example of this is here, quoting from <a href="http://forum.paradoxplaza.com/forum/showthread.php?527513-Changelog-(1.3.5.6)-21th-March" rel="nofollow">these release notes</a>:<br /><br />We&#39;ve got a new patch for you! It&#39;ll take care of Friday&#39;s patch that was...less than stellar... Again, we&#39;re terribly sorry for the inconvenience. We&#39;ll make it up to you...promise!<br /><br />I can also tell you that we&#39;re putting a new patching/testing/verification procedure in place to avoid additional f-ups. We&#39;ll talk more about that in a future community update!<br /><br />(end quote) <br /><br />Even though their values seem to be in the right place, I&#39;m not sure if these devs did, or do TDD, or continuous integration. Would be interesting to find out! I&#39;ll give them a tweet, or a post in their forum.Thomas Ferris Nicolaisenhttp://www.blogger.com/profile/17464665832399025601noreply@blogger.comtag:blogger.com,1999:blog-11485756.post-29997812248045038122011-04-30T16:57:47.366+02:002011-04-30T16:57:47.366+02:00Ferris,<br /><br />Good post! I agree with the values you enjoyed, but wanted to point out that XP done correctly (including TDD practices) should not result in early releases full of bugs. You&#39;re not truly releasing something if it requires patches to finish features. XP focuses on prioritized customer value, which includes stability. This is not to say they are not doing XP, but they should be modifying/improving their practices to ensure they keep up the early/frequent releases that are more stable.<br /><br />Clinton Keith<br />Author, Agile Game DevelopmentClinton Keithhttp://www.blogger.com/profile/07915997396545272453noreply@blogger.com