Lately, I’ve been asked by quite a few people to help them craft a proposal or abstract submission for an agile conference.
I’m lucky in that I’ve been doing this for a while, probably twenty or more years. So, I have a fair amount of experience and success. I’ve also been a program chair in local and national conferences, so I understand what folks are generally looking for in the submission process.
Given that I’ve been repeating myself a lot, I’ve decided to share some lessons in this post so that I can simply reference it when asked. I’m not sharing all of my secrets, but enough to get you going in the right direction.
Kudos to Lee Copeland
But first, I want to say thank you to Lee Copeland. Lee was the program chair for the SQE / TechWell series of conferences (StarEast & West; Better Software, AgileDev, and others) that have been running since the 1990s.
Early on, I was a fledgling speaker and Lee took the time to help me craft my submissions, talks, and speaking abilities. More than that, he showed me patience and had confidence in me. For that, I will be forever grateful and I’m hopeful that he is proud of my journey.