Comments on: Lean Principle #2 – Build Quality In

By: Ryan Platte

Ryan Platte — Fri, 17 May 2013 14:06:39 +0000

Refactoring as a regular part of software development keeps design quality high with near-zero inventory of design problems. As features are added, subtle design defects begin to evidence themselves. Developers practiced in continuous refactoring notice these “code smells” and address them inexpensively at the earliest possible moment. Your reference to refactoring seems to assume it’s long after the fact, which would indeed impede flow. XP advocated it as a continuous activity, the inexpensive JIT “middle way” between keeping an inventory of design up front (design before development) and winding up with an inventory of technical debt (design after development).

By: Casey

Casey — Wed, 06 Jul 2011 22:30:40 +0000

I love it. Develop fast, but you have to build quality products.

By: seo melbourne

seo melbourne — Wed, 17 Nov 2010 04:34:54 +0000

Very nice article but i like mostly Agile development methods also encourage automated regression testing.but there are present time variouse technology.

By: miniclip

miniclip — Sun, 19 Sep 2010 20:48:59 +0000

really awesome article i didint think that way but how about xp addiction..

By: kev

kev — Wed, 08 Sep 2010 22:03:15 +0000

re: reasons for paired programming – the primary reason/goal I believe is to allow you to deliver value early and often to your customer. People(developers, testers etc) who accept and adopt pairing will undoubtedly produce higher quality work which in turn will lead to an increase in capability/velocity. I actually pair not only on programming but on emails, on support documents, etc etc as in my experience quality is increased.
Another reason is doing XP/Scrum (not scrumbut) is hard and two heads are better than one…especially when you first start trying TDD..try it and measure your velocity over a couple of sprints and make your own mind up.

By: kev

kev — Wed, 08 Sep 2010 21:56:41 +0000

Great article, I wholeheartedly agree, In my opinion quality is the key to increasing your velocity sustainably, most teams that I observe that struggle to do scrum seem to be affected by the lack of being able to apply the XP disciplines that focus on quality, pairing, tdd, done done..you have to make sure quality is happening right from the start and that it is continually improved, letting quality go by dropping the disciplines leads to legacy problems.

By: Peter Saddington

Peter Saddington — Tue, 07 Sep 2010 11:38:09 +0000

Great article. Wondering if you could elaborate a little more on great reasons for paired programming. Some clients are interested, but have a hard time making the jump! What are the biggest factors?