Showing posts with label Agile Software Development. Show all posts
Showing posts with label Agile Software Development. Show all posts

Saturday, July 21, 2007

What is TDD?

This past week I attended a local ALPN event, and the topic was Test Driven Development (TDD). This was more technical than our usual topics, but I thought it was well presented and answered a lot of questions.

George Dinwiddie
was the presenter and did an excellent job of introducing TDD to a mostly non-technical audience. He started the discussion asking the attendees if they had heard of TDD (most everyone has) and what they thought TDD was. This is where it got interesting.

Not everyone responded, but those that did had a wide variety of answers, anywhere from TDD is another name for unit testing, to TDD is something that developers use to write code.

Here is what TDD is
  • assurance that your code does what you think it does
  • code documentation
  • code 'designer'
TDD has many benefits, but can be hard to adopt - it is a different way of thinking. The basic premise is to write a failing test case first, then write the code to make the test case pass.

It's a great way to improve code quality.

Here is why you should get your team to try it

George pointed out that his code quality has dramatically increased since adopting TDD, and said that he is now producing three times more code in the same time frame.

I've tried it myself and can certainly vouch for my productivity, but it was difficult to get started, and sometimes I don't stick to it as much as I should. As George said, it's important to start slowly, but take the time to be successful - often hard to do when you are under pressure to deliver.

I don't know - maybe I'll pick it up again!

Here is where you can get more information

The web has a lot of information on TDD. The best sites are xprogramming.com, the wikipedia entry and of course, George's blog.

Tuesday, May 15, 2007

SaaS, Innovation and Software Development

Salesforce CEO Mark Benioff was interviewed recently by Information Week, during the Software 2007 conference in Santa Clara. Benioff mentioned that there's "more innovation now then in the last 10 years." That's an interesting comment, more so because innovation seems more subtle today then in the past. What I mean by that is that there were fewer innovations ten years ago, but they were much more dramatic in terms of their impact on our lives. Innovations like browsers, broadband, even Saas (which arguably wasn't new, i.e., time sharing), had a huge impact as they fundamentally changed so much in our personal and professional lives.

So, while much of the innovation then was infrastructural, today we have n times more innovations, in terms of sheer numbers, but they are more subtle and have less "bang" then those in the past. And as this blog relates to software development management, I think this is no more evident that in the software industry. For years, software development has innovated at the infrastructure level; programming languages, faster compilers, better IDEs, new methodologies like Agile (arguably a updated version of RAD). Yet, software development continues to be plagued with cost and schedule overruns, poor quality, and security flaws that seem never ending.

So, I'm wondering how folks feel about this issue. Why isn't the software community that is driving so much of today's innovation, readily embracing innovation ourselves. Why is it that we can't better manage our own process, yet keep innovating for others to better manage their processes, be it sales, marketing, finance, you name it. I'm always amazed when I see folks who call themselves "professional software developers" still relying on Word docs, spreadsheets, and e-mail to manage their dev process. Isn't it time that we began eating our own dogfood, stepped up and embraced better visibility, accountability, and predictability. I mean if we can't even do the basics, like trace tasks from requirements through test cases to defect to source code, how are we supposed to improve the perception of software in the marketplace. Isn't that what software development management is all about.