Comments on: Agile Chronicles #7: Bugs, Unit Testing, and Throughput

By: JesterXL

JesterXL — Sun, 30 Aug 2009 19:06:52 +0000

@nicemandan My feelings, exactly. I still agree TDD is worth doing on the services. They say you shouldn’t run tests against real webservices. I, however, have found it extremely useful. Since the weakest link in the chain for a RIA is Factories, the service classes that actually hit real back-ends are the 2nd. I can fix the factories, I can’t fix the services. That, and confirming they are in fact a problem, quickly and assuredly, is extremely helpful, both during development and over time.

…everything else? Yeah, exactly, I have to get things done by end of sprint, and if they don’t work in another sprint, saying TDD would of saved me is bs because I wouldn’t of gotten the burn rate I got NOT using TDD.

Then again, I’m still learning, so maybe…..

By: nicemandan

nicemandan — Sun, 30 Aug 2009 18:34:12 +0000

I’m new to TDD as well and I’ve found it incredibly difficult to balance the agile ‘git-er-done’ ethos with TDD.

To build a feature from a decent set of test takes time, but then the pressure to have a working feature ready by the end of a sprint usually overrides having the tests in place.

This negates using TDD at all if the time pressure is such that you end up having to hack a feature together.

It feels to me that these two forces tend to pull the project apart and developers usually withdraw back to the quick hacks they know and do best.

By: Getting Advanced in Flex | der hess

Getting Advanced in Flex | der hess — Sat, 09 May 2009 10:09:49 +0000

[…] Agile Chronicles #7: Bugs, Unit Testing, and Throughput […]

By: Nirth

Nirth — Mon, 05 Jan 2009 05:26:05 +0000

Thanks for this series of articles.

By: Simon Hartley

Simon Hartley — Thu, 01 Jan 2009 13:04:26 +0000

Here’s a link dealing with the pace of development in sprints:
http://www.infoq.com/news/2008/11/sprint-misnomer