QCon SF Keynote: Techie VC's Talk About Trends & Opportunities
Kevin Efrusy and Salil Deshpande talk about what makes a business successful or not, presenting three actual cases they have been involved with: Hyperic, G2One, SpringSource.
Tracking change and innovation in the enterprise software development community
Posted by Abel Avram on Nov 28, 2008
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:
Agile Development e-Kit: Educational Content from Rational
CollabNet presents Agile ALM virtual conference, April 15, 2010
VersionOne is recognized by Agile practitioners as the leader in Agile project management tools. Companies such as Adobe, BBC, CNN, Dow, HP, IBM, Sony and 3M have turned to VersionOne to help deliver greater value to their customers.
Poor video production, poorly prepared speakers, and misses the central point of TDD - its role as a design tool.
Shameful.
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.
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.
Great presentation! Congratulations!
Kevin Efrusy and Salil Deshpande talk about what makes a business successful or not, presenting three actual cases they have been involved with: Hyperic, G2One, SpringSource.
InfoQ talks to Mark Fisher, project lead for the Spring Integration project, about the framework.
Peter Lubbers explains in this article how HTML5 Web Sockets interact with proxy servers, and what proxy configuration or updates are needed for the Web Sockets traffic to go through.
Neal Ford shows what ThoughtWorks learned from scaling Rails development: infrastructure, testing, messaging, optimization, performance.
Stuart Halloway discusses Clojure and functional programing on the JVM in depth, and touches on the uses of a number of other modern JVM languages including JRuby, Groovy, Scala and Haskell.
Oren Teich and Blake Mizerany talk about the technology behind Heroku and the benefits of the new add-on system.
Chris Riley presents security issues threatening service based systems, examining security threats, presenting measures to reduce the risks, and mentioning available security frameworks.
This talk investigates technical issues encountered when moving to an Agile process.
4 comments
Watch Thread Reply