It’s that time of year again and people are scrambling to put together conference proposals, with fingers crossed, for the annual Agile Conference in August. This year it’s Agile2013 in Nashville and I, like the others, am scrambling.
I have 2 proposals in this year. Just like the last couple years, the open and interactive submission system has been great for tuning my proposals. Unlike the last couple years, there seems there’s nowhere for a hardware fella to hide. No Embedded Agile stage. No Emerging Applications of Agile stage. This year we’ve been thrown in with the big dogs and it’s getting a tad harder to appear relavent.
Case-in-point: I received a review on my hardware TDD talk… a very thoughtful and fair review I might add that I was expecting to see… and I wanted to share just a snippet of it here.
A much bigger issue, and this is an issue with the audience, not the speaker or talk, is that there seems to be low interest in embedded agile programming in general at the national agile conference. We realize this is sort of out of your control, but if we were convinced you would have a full room, it would bump this rating up a ton.
The reason I think this is such a fair review and this an especially fair comment is because the reviewers in this case are spot on. The hardware/embedded crowd the past 2 years has not been especially well represented. And because the conference gets so many high quality proposals from experts around the world, I can see how it’s difficult to squeeze in fringe topics knowing that the appetite for those topics at the conference is… uhh… less than spectacular.
That needs to change and I need your help to change it.
I’ve learned a lot at the 2 agile software conferences I’ve been to. The high point was seeing test-driven development demonstrated by James Grenning in Salt Lake City at Agile2011. Immediately after, I dedicated time to learning TDD and using it to improve the quality of testbench code I write. Now, I use it for almost every new testbench component I build. As much as I can, I also use TDD to add features to legacy code. TDD is easily the most important and most credible technique I’ve experienced at any conference I’ve ever been to, hardware conferences (specifically) included. Had I not been in Salt Lake City, I wouldn’t be doing TDD today and the quality of my code would be garbage, just as it was before.
But that’s just me. I know other hardware developers have attended Agile conferences and I know they’ve been impressed. I also know some of those people read this blog. In fact, if you’re one of those people I’m actually looking at you right now.
To those hardware folks that have had the opportunity to attend Agile software conferences: it’s time to play agile hardware advocate. I’m asking you to share your experience from Agile software conferences and the value you see in attending.
- How has an Agile software conference made you think differently about hardware development?
- What’s one thing you’ve seen that you wouldn’t have seen anywhere else?
- Who have you met that you wouldn’t have met anywhere else?
Don’t spend a whole day on it. Five minutes and a paragraph or two is fine; even just a few bullet notes to get the point across. Paste your experience into the comments section and let people know what they’re missing.
The Agile conference every August and others like it around the world are tremendous opportunities for hardware developers to stock their minds with great new ideas; the kinds of ideas that aren’t created within hardware development. We all need to know that. I’d encourage hardware developers to attend an Agile software conference. Hopefully I can get a little help from a few others in convincing you it’s time well spent.
Yes… I’m still looking at you! Comments please :).