Comments on: Using ScrumWorks http://server.billhamilton.com:84/wp/scrum/using-scrumworks/ Thu, 15 Dec 2011 05:29:42 +0000 hourly 1 By: Bill Hamilton http://server.billhamilton.com:84/wp/scrum/using-scrumworks/#comment-12 Bill Hamilton Thu, 24 Dec 2009 02:09:16 +0000 http://billhamilton.com/wp/?p=4#comment-12 I agree with you, Nadir. I had lead Scrum projects for over a year prior to taking the class and it's been 3 years since the class during which I've lead other Scrum projects. It's only one of many practices, but the importance of doing it correctly cannot be overlooked, IMHO! I agree with you, Nadir. I had lead Scrum projects for over a year prior to taking the class and it’s been 3 years since the class during which I’ve lead other Scrum projects. It’s only one of many practices, but the importance of doing it correctly cannot be overlooked, IMHO!

]]> By: Nadir Khan http://server.billhamilton.com:84/wp/scrum/using-scrumworks/#comment-11 Nadir Khan Wed, 23 Dec 2009 07:53:35 +0000 http://billhamilton.com/wp/?p=4#comment-11 Your take on Scrum is spot on! but please understand that Scrum itself isn't a complete Agile Practice, you have to supplement Scrum with other practices as well so as to encompass all four principles of the agile manifesto. For instance the most common (i wouldn't use the word best) combination of Agile practices used around the world are Scrum+XP. Both on their own are partially complete, but together they compliment each other's strengths and cover up each others lackings. Scrum only helps you bring discipline into your development process and tries to identify weaknesses early so that you can improve on them, but it doesn't claim to give you a road map to good technical design or good continuous integration methods. It's not supposed to do that, and it doesn't do that. In order to improve your development techniques so as to remain Agile AND at the same time maintain quality you should look into other practices that really address these issues. There are 22 different types of code smells that one should know of. One should also try FDD and TDD and really see how well defined and helpful these are for agile development. All in all, sticking to the premise of your entire article, you're right, two days of training would not make you a ScrumMaster. And even if you do become a really good ScrumMaster, Scrum does not guarentee... nay... claim that it would instill good programming ethics in your developers. My two cents worth. Thanks. Your take on Scrum is spot on! but please understand that Scrum itself isn’t a complete Agile Practice, you have to supplement Scrum with other practices as well so as to encompass all four principles of the agile manifesto.

For instance the most common (i wouldn’t use the word best) combination of Agile practices used around the world are Scrum+XP. Both on their own are partially complete, but together they compliment each other’s strengths and cover up each others lackings.

Scrum only helps you bring discipline into your development process and tries to identify weaknesses early so that you can improve on them, but it doesn’t claim to give you a road map to good technical design or good continuous integration methods. It’s not supposed to do that, and it doesn’t do that. In order to improve your development techniques so as to remain Agile AND at the same time maintain quality you should look into other practices that really address these issues. There are 22 different types of code smells that one should know of. One should also try FDD and TDD and really see how well defined and helpful these are for agile development.

All in all, sticking to the premise of your entire article, you’re right, two days of training would not make you a ScrumMaster. And even if you do become a really good ScrumMaster, Scrum does not guarentee… nay… claim that it would instill good programming ethics in your developers.

My two cents worth.

Thanks.

]]>