Internal Hackathons

Agreed goals, rules, sandboxes and a judging rubric, plus the idea backlog, run sheets, demo days and graduation path that turn internal hackathon prototypes into shipped work.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Internal Hackathons, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

203

Starter tasks

⚙️ Software Engineering

Internal Hackathons

Organising hackathons that let engineers explore ideas, with themes, judging, demos and a path for the best prototypes to reach production.

  1. Hackathon goals and executive sponsor
  2. Protected time and budget approval
  3. Choosing an in-person, remote or hybrid format
  4. Hackathon rules, eligibility and team size
  5. Data, security and code ownership guardrails
  6. Sandbox environments and spending caps
  7. Organising crew and role cards
  8. Picking dates around the release calendar
  9. Interest survey and lessons from past events
  10. Year-round hackathon idea backlog
  11. Annual hackathon calendar
  12. Post-event prototype follow-up tracker
  13. Hackathon sponsor review cadence
  14. Six-week announcement and countdown plan
  15. Hackathon retrospective and improvement log
  16. Hackathon project archive and demo library
  17. Participation and outcome metrics
  18. Sandbox teardown and leftover resource sweep
  19. Rapid prototyping for a two-day build
  20. Three-minute demo pitch practice
  21. Judge briefing and score calibration
  22. Team formation facilitation
  23. Scoping an idea to fit the time box
  24. Hackathon starter kits for internal APIs
  25. Mentor rota during the build days
  26. Themes and challenge statements
  27. Judging criteria and scoring rubric
  28. Prizes and recognition within gift policy
  29. Choosing collaboration and demo tooling
  30. Inclusion review for hackathon access
  31. Graduation criteria for prototypes
  32. Kick-off and idea pitch session
  33. Demo day run sheet
  34. Judging session and results sign-off
  35. All-hands showcase of winning projects
  36. One-team pilot hackathon
  37. Cross-functional hackathon with product, design and support
  38. First hackathon as a new engineering manager
  39. Hackathon for a team of under ten engineers
  40. Hackathon across distant time zones
  41. Preparing to take part as an engineer
  42. Making the case under a tight roadmap
  43. Hackathon after a merger or reorganisation
  44. Prototype to production handover path
  45. Security and privacy gate for graduating prototypes
  46. Twelve-month outcome review of the programme
  47. Internal tooling fix-it hackathon
  48. AI-themed hackathon with model access guardrails
  49. Multi-site annual hackathon programme
  50. Captain handbook for future organisers

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Hackathon goals and executive sponsor

This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Teams run hackathons for very different reasons: morale, exploring a new platform, clearing internal tooling pain or finding the next product bet, and an event that tries to do all four usually does none well.

First tasks

  • Write the one reason this hackathon exists in a single sentence
  • Book thirty minutes with the likely sponsor to agree the goal
  • Draft three outcomes you would expect to see six months later
  • Share the goal statement with engineering leads and product managers

Protected time and budget approval

Engineers will not join a hackathon that has to be squeezed around sprint commitments, and a budget that appears after the venue is booked always comes up short. Getting two clear days of protected time and a costed budget approved before announcing anything stops the event collapsing into a lunchtime side activity.

First tasks

  • List every cost line from food and prizes to sandbox cloud spend
  • Add a ten per cent contingency line to the hackathon budget
  • Ask each delivery lead to confirm reduced sprint commitments in writing
  • Arrange on-call cover so no participant carries a pager during the event

Choosing an in-person, remote or hybrid format

Format decides almost everything downstream: venue, food, demo tooling, time zones and who can realistically take part. Comparing the three options against where your engineers actually sit and what the goal needs avoids a hybrid event where remote people quietly drop out by lunchtime on day one.

First tasks

  • Pull a headcount of engineers by office and time zone
  • Score each format against cost, reach and the hackathon goal
  • Write the chosen format and its main trade-off in one paragraph
  • Agree the format with the sponsor before booking anything

Make it yours.

Install Internal Hackathons, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.