Roanoke Code Camp 2009

NOTE: This post is VERY late.  Here's lessons I learned. Next year it will be more timely!
I admit, I am biased but RV.NUG is the best UG ever! Roanoke Code Camp 2009 showed why I think this. 
  • Leadership TEAM. It was the leadership team’s idea to meet for lunch once a week for 8 weeks to plan the event. I thought it was too much to ask; but they wanted to do it because they wanted a great Code Camp and they like networking with each other. 
  • RV.NUG and RVSPUG membership GROUP as the core group of attendees. The UG members promoted the event with enthusiasm. They showed up with enthusiasm early on a spring-like Saturday morning and helped make every attendee welcome. The members know how to network and used their skills throughout the day.
  • Attendees. They showed up with enthusiasm and a passion to learn. They also showed up with appreciation for the opportunity. Many of the presenters say that Roanoke is their favorite place to present and it’s because of the attendees.
  • Presenters. Many are presenters from prior years. They include local talent and talent from as far away as Philadelphia and Minnesota. Each have contributed countless volunteer time learning and preparing presentations simply to share their passion and knowledge with communities (both their own and others). 
  • Volunteers. The volunteers were willing to do anything to help make the event run smoothly – anything from registration to carrying boxes or emptying trash. Many of the attendees became volunteers simply because they saw a need and helped out without being asked. 
  • Contributors. It’s nice to have books to give away in each session; raffle prizes at the close; food to eat all day (and the night before if you’re a presenter or volunteer). 
Thanks to every person that participated. Each and every person was a contributor in making this a great event. 
Now for some proof that I am not totally biased. Here are comments from others on Roanoke Code Camp 2009.
 
Twitter
  • Getting ready to head home from #RoanokeCC. Had a great weekend everyone.
  • Had a great time at #RoanokeCC today. Thanks to everyone that attended my sessions.
  • Home. Great day at #RoanokeCC.
  • Leaving Roanoke Code Camp after party. awesome Code Camp. Farewell my friends in the valley.
  • #RoanokeCC rocked. See you again next year!
  • #RoanokeCC was well worth!
  • Done with my class at #RoanokeCC. It was worth the six hour drive :-)
Speaker Comments
  • Thank you very much for your generous hospitality this weekend.  You and your team put in a great deal of hard work and it showed!  Yesterday’s Roanoke Code Camp was truly the best code camp I’ve attended.  It was a pleasure presenting and teaching my topic.  I would be very happy to present again at the event in the future.  
  • When I got back home last evening, the first thing I told my wife was that Roanoke, VA is the most hospitable place on the planet!  My entire experience, ranging from the Hyatt hotel staff, the folks at Shakers, your user group members, the other speakers, event attendees and even the Virginia Wesleyan baseball team that I ran into at Burger King on the way home (only I could pick the only restaurant along I-81 where an entire college baseball team is stopping for dinner), was one of friendliness.  
 
Attendee Comments
  • My favorite presentation was “everyone I saw”
  • Thank you!
  • Job Well Done RV.NUG/Code Camp Committee!
  • Developers != Mornings, otherwise Great Job
Blog Posts
  • Andrew Duthie
  • Brian Hartsock
    • I attended my first Code Camp this past weekend. Overall, it was a great experience, although for a few reasons you might not expect. I learned a little about new .NET features, but the biggest benefit for me was the networking… Through Code Camp, blogging, and Twitter I have joined a community of developers much larger than Mailtrust’s. More

Photos:

Code Camp Lessons Learned – Post Implementation

Much thought and effort goes into planning and executing a Code Camp. Hopefully these efforts are distributed among a team.  Code Camp team members volunteer their time (while continuing on with their day job and personal life).  During the final days leading to the event, priorities of other items in team members lives get lowered (such as “real job” items and personal items). These items naturally get behind.   While the Code Camp event is rewarding (and fun!) it is also tiring. There is a natural (well-earned) energy drop following the event. 
But, as with any project, there is still work to be done following the implementation. There are post-implementation tasks. The priority of other items (“real job” and personal) naturally increase (since they are now behind) and the Code Camp tasks drop in priority; in some cases, they just don’t get done. 
Expect the team to have very limited time following Code Camp. Therefore, the closeout tasks must be identified early in the planning. Even better, complete as many closeout tasks as possible prior to Code Camp. Minimize the closeout effort.  These are all simple tasks. As with any collection of small effort items; the hardest part is creating the list.
Here’s a list of some closeout items, along with ideas on minimizing the effort required following Code Camp. 
Do as many tasks as possible before Code Camp and assign any remaining tasks (with due dates) in advance of Code Camp.
  • Thank you notes (speakers, volunteers, contributors, attendees)
    • You have been communicating with these groups all along. Draft thank-you emails as you go. (You can add one or two lines after Code Camp if you like, but most of the work can be done prior to the event).
  • Post speaker content to the web
    • Get speaker content early (if possible – even if you only get 2 or 3, it’s helpful).
    • Leave a flash drive in the speaker room so they can easily leave content the day of Code Camp.
    • Have everything in place to easily upload files.
  • Connect prize winners with vendors
    • See thank you notes. Have the emails drafted and ready to go so all you have to do is add the winner’s contact information.
  • Cleanup
    • If you put one person in charge, this usually is not a problem. Everyone wants to leave and we’ve never had a problem getting people to pitch in – IF we have someone asking for help.
«May»
SunMonTueWedThuFriSat
262728293012
3456789
10111213141516
17181920212223
24252627282930
31123456