tag:blogger.com,1999:blog-5232592511268803325.post1279004916493781335..comments2018-05-11T13:52:15.128+01:00Comments on Programming for People: 10 Reasons why I like Scrum for GamesTimhttp://www.blogger.com/profile/03240345507294112807noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-5232592511268803325.post-24560520707041883132009-12-01T17:01:46.377+00:002009-12-01T17:01:46.377+00:00Tim,
Good article! I like how you describe how y...Tim,<br /><br />Good article! I like how you describe how your team adopted it and how Scrum created a sense of urgency which hadn't existing. <br /><br />The likely issue with Steve's experience is one seen elsewhere. Teams are often thrust into using Scrum without understanding the principles you outline. This leads to a parroting of the rules of Scrum that don't make sense without the context of the principles. They end up failing with Scrum and blame it, calling it a methodology when in fact it is only a framework, as you point out.<br /><br />Scrum can neither be credited or blamed for a team's success or failure. It's like crediting a hammer for building a good house. Studios build their own methodologies and sometimes their cultures and frameworks do not support communication, self-management and iterative practices. Scrum doesn't find much purchase there.Clinton Keithhttps://www.blogger.com/profile/07915997396545272453noreply@blogger.com