Programming for People

Tim, Good article! I like how you describe how y...

2009-12-01T17:01:46.377Z

Tim,

Good article! I like how you describe how your team adopted it and how Scrum created a sense of urgency which hadn't existing.

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.

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.

n00b! :) at least you didn't do a dobbsy and itera...

2009-05-30T22:12:49.585+01:00

n00b! :) at least you didn't do a dobbsy and iterate by poping and pushing every element of the vector. :(

I also mark emails as read before deleting them an...

2008-08-30T16:25:00.000+01:00

I also mark emails as read before deleting them and will never minimize outlook with mail still marked as unread (even if I haven't read them or have no intention of reading them) :)

Sorry - I wasn't saying this happens every time I ...

2008-08-16T15:42:00.000+01:00

Sorry - I wasn't saying this happens every time I estimate - far from it!

I was just celebrating the fact that very occasionally, inspiration helps you do something in minutes that you were expecting to take hours!

Usually for me the task goes the other way ;-) I e...

2008-08-16T12:12:00.000+01:00

Usually for me the task goes the other way ;-) I estimate it at one hour and it ends up taking 6 or 7... :-( I think it also sometimes depends on the nature of the work :-)