Comments on: GDC 2006: Agile Scrum http://www.codedread.com/blog/archives/2005/12/22/gdc-2006-agile-scrum/ Tue, 17 Jan 2012 21:56:44 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Rob http://www.codedread.com/blog/archives/2005/12/22/gdc-2006-agile-scrum/comment-page-1/#comment-291 Rob Thu, 22 Dec 2005 19:56:55 +0000 http://blog.codedread.com/?p=195#comment-291 I think one theme that I see arising from the XP practices that I've read about so far is that they rely on real dedication, interest and skills on the part of the participants. In other methodologies it's easier to tiptoe around the fact that many people working on a project might not be very highly skilled or that most people see the project as just their job. Being just-a-job reduces enthusiasm and something like a daily heartbeat status meeting could quickly degrade into a bitch session for all the problems with a project. In your examples, you've got a couple people who are enthusiastic and commited. It sounds like XP is a way to enable enthusiastic, commited people to work effectively. As for the unenthusiastic, uncommited and possibly unskilled... well, I guess the methodology's not the root problem there. I think one theme that I see arising from the XP practices that I’ve read about so far is that they rely on real dedication, interest and skills on the part of the participants. In other methodologies it’s easier to tiptoe around the fact that many people working on a project might not be very highly skilled or that most people see the project as just their job. Being just-a-job reduces enthusiasm and something like a daily heartbeat status meeting could quickly degrade into a bitch session for all the problems with a project.

In your examples, you’ve got a couple people who are enthusiastic and commited. It sounds like XP is a way to enable enthusiastic, commited people to work effectively. As for the unenthusiastic, uncommited and possibly unskilled… well, I guess the methodology’s not the root problem there.

]]>