People are sitting at two different tables working on laptops and collaborating. There's a chalkboard with writing on it. The title says Execute a Hackathon to Solve L&D Challenges.
Pricing
Format Member Non-Member
$14.95 $19.95
$0.00 $19.95
Please see the terms of sale for important information about the use of PDFs.
Read More Read Less

Have an L&D challenge that you want to develop new and energizing solutions for? Consider hosting a hackathon. These events aren’t just for tech companies. In a hackathon, teams are challenged to develop solutions to a specific business problem or to create a new process or product. Once they have brainstormed what they consider a winning idea, they develop a prototype. A panel of judges then reviews the solutions and chooses a winner, which ideally then moves forward into implementation. In this issue of TD at Work, John Parsell details how to run a hackathon, including the critical steps, guidance, and resources necessary to prepare for and run a 24-hour hackathon. Further, he:

  • Offers tips on how to capture the spirit, energy, and creativity of a hackathon
  • Shares how to create diverse teams that are equipped to create winning solutions that you can bring to reality
  • Presents case studies and examples of noncoding hackathons to demonstrate how others are successfully leveraging this platform

Job aids included in this issue are a sample hackathon kickoff agenda, scorecard template, and communication checklist.

Book Details
ISBN: 9781952157790
Pages: 20
Publication Date:
Formats: Paperback, PDF
Product Code: 252103
About the Author
See All
2 Comments
Sign In to Post a Comment
Great Insight !!!
Sorry! Something went wrong on our end. Please try again later.
Excellent article! I have heard of hackathon's before and through this article I now feel like I have all that I need to execute one. Thank you for the insights and tips as well as samples in the back of the article John.
Sorry! Something went wrong on our end. Please try again later.
Sorry! Something went wrong on our end. Please try again later.