InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Presentation: Manager's Introduction to Test-Driven Development

Posted by Abel Avram on Nov 28, 2008

Sections
Process & Practices
Topics
Agile ,
Adopting Agile
Tags
Management ,
TDD ,
Value & Metrics

In this presentation filmed during Agile 2008, Dave Nicolette and Karl Scotland try to introduce non-technical managers to one of the most popular Agile development techniques: Test-Driven Development (TDD). The presentation intends to be a primer for managers who want to understand the value of TDD, and of Agile in general, in software development.

Watch: Manager's Introduction to Test-Driven Development (1h 19 min.)

The presentation starts with Karl showing a simple TDD example used to created an Excel worksheet including some Visual Basic macros. The purpose of this example is to show the difference between a static specification - a piece of paper with some specs - and a working one - code that runs and can be checked for errors.

The audience is then introduced to the various results generated by an increased design debt: increased costs, reduced velocity, raised number of defects, increased time spent on defects, increased support costs.

After demonstrating the value of TDD, Dave gives some advice to managers which do not have the technical skills to drive the implementation of TDD by their development teams:

    • Attend daily stand-up meetings and ask questions
    • Visit the work area and observe the process
    • Ask team members about TDD and how they use it
    • Track the defect curve closely and raise issues
  • This article is part of a featured topic series on Agile

Related Sponsor

In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!

Shoddy and Lame by Bob Marshall Posted
Re: Shoddy and Lame by Ole Friis Posted
Re: Shoddy and Lame by Rafael Guedes Posted
Re: Shoddy and Lame by clarke ching Posted
Original exercise by Ole Friis Posted
  1. Back to top

    Shoddy and Lame

    by Bob Marshall

    Poor video production, poorly prepared speakers, and misses the central point of TDD - its role as a design tool.

    Shameful.

  2. Back to top

    Original exercise

    by Ole Friis

    For those who want to see what inspired the two guys:

    www.clarkeching.com/2006/04/test_driven_dev.html

    Personally, though, I think the exercise is too technical for managers, and it's actually a great example of TDD not automatically giving you a neat solution without a lot of sweat (which is how reality works sometimes, unfortunately :-) )...

    I once saw a very convincing presentation of RSpec by Aslak Hellesøy, and I sat next to a very non-technical colleague. She got really excited about TDD (or, rather, BDD) from the presentation, so I think RSpec is a much better platform for such a presentation than Excel/VBScript. Your opinion may differ.

  3. Back to top

    Re: Shoddy and Lame

    by Ole Friis

    I don't agree. I actually think Karl and Dave give pretty good arguments for managers - remember, the target audience is managers, not us technicians. But even though I'm a technician, I can still use the points from the presentation, as I often have to deal with managers and convince them that TDD is the right thing to do.

  4. Back to top

    Re: Shoddy and Lame

    by Rafael Guedes

    Great presentation! Congratulations!

  5. Back to top

    Re: Shoddy and Lame

    by clarke ching

    Bob wrote:
    > Poor video production, poorly prepared speakers, and misses the central point of TDD - its role as a design tool.

    Bob, to be quite blunt: your comment was rude, thoughtless and unhelpful.

    Clarke

Educational Content

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.