tag:blogger.com,1999:blog-4160018541260064202011-11-27T16:07:18.557-08:00Nathan Henkelhttp://www.blogger.com/profile/00925948564671310348noreply@blogger.comBlogger71100tag:blogger.com,1999:blog-416001854126006420.post-38263374747263948742007-12-20T23:30:00.000-08:002007-12-20T20:31:53.291-08:00

Whew! I've been really busy. Seems impossible that it's over a month since I posted, but there it is.The week before last, I attented SQE's Agile Development Practices conference in Orlando. The highlight of the conference for me was J. B. Rainsberger's tutorial on Test-Driven Enterprise Code. I'll post my thoughts on that later, but for now I'll just say that I usually consider a conference to

Nathan Henkelhttp://www.blogger.com/profile/00925948564671310348noreply@blogger.com0tag:blogger.com,1999:blog-416001854126006420.post-72004051363488391582007-11-14T10:02:00.000-08:002007-11-14T10:17:15.261-08:00

Borland's marketing communications editor.I just got the following email from Borland:It’s amazing that poor requirements account for 71% of failed software projects*. And, unfortunately, no matter how efficient of a requirements management system you have, it might not be enough to save your projects from joining that statistic. That’s why defining complete and accurate requirements is a

Nathan Henkelhttp://www.blogger.com/profile/00925948564671310348noreply@blogger.com1tag:blogger.com,1999:blog-416001854126006420.post-87752472806082664282007-11-13T22:13:00.000-08:002007-11-13T19:15:32.090-08:00

Information about any project can be divided into four categories:1. Things we know (and know we know)2. Things we know we don't know3. Things we think we know, but don't (i.e. things we're wrong about)4. Things we don't know we don't knowObviously, if you were to try to actually figure out where everything falls, you would put everything into 1 or 2. Everything that should be in 3, you would put

Nathan Henkelhttp://www.blogger.com/profile/00925948564671310348noreply@blogger.com0tag:blogger.com,1999:blog-416001854126006420.post-26555887556719758342007-11-11T21:08:00.000-08:002007-11-12T10:44:23.066-08:00

I don't have any hard evidence to back up this claim, but my guess is that most people think of defect detection when they think of code reviews. And well they should--code reviews are one of the most effective defect-detection methods around, falling just behind high-volume beta testing and prototyping, according to Steve McConnell's Code Complete. If we consider code and design reviews together

Nathan Henkelhttp://www.blogger.com/profile/00925948564671310348noreply@blogger.com0tag:blogger.com,1999:blog-416001854126006420.post-78881334789813088032007-11-05T22:33:00.000-08:002007-11-06T06:50:14.604-08:00

Another way to say that is, the more honest you are, the more agile you will tend to be in your software development. The more personal and interpersonal honesty you practice, the more able you will be to respond to change.If you are honest with yourself, you will admit what you don't know. You'll admit that you don't know the future, and that you're not that good at predicting it. You'll admit

Nathan Henkelhttp://www.blogger.com/profile/00925948564671310348noreply@blogger.com0tag:blogger.com,1999:blog-416001854126006420.post-78903067869617673812007-10-31T20:10:00.000-07:002007-11-02T13:56:34.220-07:00

Metrics, properly used, are a valuable tool for monitoring and improving your software development process. There's a lot of information available about what metrics to gather, what to publish, what not to publish, and how to interpret your findings.Today, however, I want to deal with the problem of intrusive metrics gathering. How much intrusion on a developer's workflow should we allow in the

Nathan Henkelhttp://www.blogger.com/profile/00925948564671310348noreply@blogger.com1tag:blogger.com,1999:blog-416001854126006420.post-278085865726315232007-10-29T17:44:00.000-07:002007-10-31T22:42:57.073-07:00

Kristan Vingrys writes about defect debt on his blog:"On an Agile project defects are fixed as they are found, so no story should be considered complete if there are outstanding defects with it. But this does not mean that defects do not persist."He describes those defects which persist beyond the story to which they pertain (or persist beyond the iteration in which they were created) as "defect

Nathan Henkelhttp://www.blogger.com/profile/00925948564671310348noreply@blogger.com0