In-House Hackathon for Beginners: A 3-Team Progress Board | Run Judging in One Day

Project & Development

In-House Hackathon for Beginners: A 3-Team Progress Board | Run Judging in One Day

Organizers of a first in-house hackathon use this beginner template to track three teams in one table, judge the demos, and pick owners for projects worth keeping. The whiteboard has four pages. Page 1 sets the theme, rules, judging criteria, and a six-step timeline, then introduces the teams. Page 2 is a progress table rewritten every hour, plus places to ask for help and share tips. Page 3 judges each demo with star stamps on three criteria (useful, fun, polished) and picks the winner. Page 4 sorts the projects to keep into four MoSCoW columns with an owner, next step, and deadline. The task board has five columns, from Getting ready to Done, with four parent tasks and three subtasks each. A hackathon is a short, focused event where people build a small tool and show it at the end. Even if you have never run one, just rewrite the e.g. examples in your own words. Stars come from the organizer and people on other teams, so no one favors their own team.

0 Likes 0 Copies Author: WeProcess
in-house hackathon progress tracking judging sheet MoSCoW for beginners
Other language versions
Sign up free and use this template

Once you have a free account, you can copy this template from the marketplace

Whiteboard preview

Preview mode In-House Hackathon for Beginners: A 3-Team Progress Board | Run Judging in One Day
Sign up free and use this template

Whiteboard preview

① Theme, rules, and judging criteria ... ③ Team A ④ Team B ⑤ Team C ⑥ Agreements on updates and asking fo... ⑦ Progress table for teams ③ to ⑤ (re... ⑧ Questions for the organizer ⑨ People who can help ⑩ Tips worth sharing ⑪ Decided at the midday check-in ⑫ Demo judging table based on the pit... ⑬ Feedback on Team A's demo ⑭ Feedback on Team B's demo ⑮ Feedback on Team C's demo ⑯ Winner and reason (count the stars ... ⑱ Owner, next step, and deadline for ... ⑲ Four steps until it is used at work In-House Hackatho... How to use (4 pag... Theme, what we bu... Rules, promises, ... Blockers and ques... Tips and feedback 1/4 Set the theme, me... Ctrl+F / ⌘F : 2/4... → 2/4 2/4 Build side by side ↙ 3/4 Themee.g. Build a small tool in one day that solves a problem at work(hackathon = a short, focused event where you build and then show each other) Rulese.g. Start at 9:30 a.m. and stop building at 4 p.m.Use only tools the company already allows. Judging criteriae.g. Three: useful, fun, and polished.One star per criterion per person, from the organizer and people on other teams. ② From start to d... Start e.g. 9:30 a.m. Read out the theme and rules, introduce the teams Phase 1 e.g. 10 a.m. Settle on one thing to build and start Phase 2 e.g. 12 p.m. Midday check-in, one minute per team (board ⑪) Phase 3 e.g. 1 p.m. to 4 p.m. Polish and prepare the pitch Phase 4 e.g. 4:00 p.m. 5-minute demo per team and judging (board ⑫) Goal e.g. 5:00 p.m. Announce the winner and decide what to keep Members e.g. 2 from sales, 1 from accounting Pain point e.g. Copying quotes takes 30 minutes every time Idea e.g. Turn a web form into a quote table automatically Roles e.g. builder, tester, presenter Members e.g. 1 from admin, 1 from engineering Pain point e.g. Finding a free meeting room takes too long Idea e.g. Post free rooms to the team chat Roles e.g. decide who builds and who tests Members e.g. 2 from accounting, 1 from engineering Pain point e.g. Receipts are typed in by hand every month Idea e.g. Read the amount from a photo of a receipt Roles e.g. builder, tester, presenter Updating the tablee.g. Each team rewrites its row of the progress table (⑦) at the top of every hour Signal for helpe.g. After 15 minutes stuck, stick a note on ⑧ and call the organizer What we build Current status Blockers Pitch line Team A e.g. A quote entry form e.g. The input screen works e.g. Exporting to the table fails e.g. Copying: 30 min to 0 Team B e.g. Free-room alerts e.g. Writing the alert message e.g. None right now e.g. Find a room in one check Team C e.g. Reading receipt amounts e.g. Not yet a prototype e.g. Reading accuracy is low e.g. Half the typing Organizer's view e.g. Keep the three teams' pace even e.g. Only Team C is behind e.g. Visit Team C first e.g. Show only what works for C e.g. Team A stuck for 15 minutes on exporting to the table e.g. Team C cannot raise the reading accuracy Write the team name and what you did when you got stuck When solved, rewrite it in ⑩ as a tip e.g. Spreadsheet formulas: the engineer on Team B e.g. Building screens: the organizer Write your name and what you can help with in one line Raise your hand only when it does not stop your own work e.g. Try the export on just one row first e.g. Take photos in a bright place for better reading Write it so other teams can use it too For solved questions, leave the reason here Narrowing the scopee.g. Team C reads the amount only from bright photosand uses dark photos as an aid for typing by hand Pitch order and timee.g. A, B, then C, 5 minutes per team 3/4 Judge the demos → 4/4 4/4 Hand off the proj... Pitch line Useful Fun Polished Team A e.g. Copying: 30 min to 0 Place a star here Place a star here Place a star here Team B e.g. Find a room in one check Place a star here Place a star here Place a star here Team C e.g. Half the typing Place a star here Place a star here Place a star here What to look for Copy the pitch line from ⑦ Could you use it every week Would you want to use it Did the demo run to the end e.g. Good: the copying finished in an instant e.g. Better if: you could also pick the client name Each person who placed a star writes one item e.g. Good: the alert message is short and easy to read e.g. Better if: it could continue to booking Each person who placed a star writes one item e.g. Good: reading the amount is fast e.g. Better if: it could read dark photos too Each person who placed a star writes one item Winning teame.g. Team A (9 stars)Reason: weekly copying is gone and it can be used at work right away In a tiee.g. Pick the team with more stars for useful ⑰ Sort what to ke... MustEssential e.g. Team A's quote form (someone uses it every week) ShouldShould do e.g. Team B's free-room alert (booking comes later) CouldIf time allows e.g. Team C's amount reader (after raising accuracy) Won'tNot this time e.g. Rolling it out to every department waits for now Owner Next step Deadline Must project Owner: ____ e.g. one person from sales on Team A e.g. Try it on 3 quotes next week e.g. In 1 week Should project Owner: ____ e.g. the admin person on Team B e.g. Send the alerts only to the admin chat e.g. In 2 weeks Could project Owner: ____ e.g. the engineer on Team C e.g. Try reading dark photos e.g. In 1 month Organizer Owner: ____ e.g. the organizer e.g. Ask in week 4 if it is still in use e.g. In 4 weeks Week 1Try it oute.g. The owner uses it 3 times in real work Week 2Fix ite.g. Fix just the two things that bothered people Week 3Write how to use ite.g. Put the steps on one page for people in the same department Week 4Use it at worke.g. The whole department uses it and the organizer asks how it goes → 2/4 Build side by side ↙ 3/4 Judge the demos → 4/4 Hand off the proj...
100%

Drag to move, scroll to zoom

Task board contents

Getting ready 16 items

Kick off the event
Build side by side
Judge the demos
Hand off projects
Write the criteria
Plan the day
Introduce the teams
Update table hourly
Ask for help
Decide at check-in
Present the demos
Place star stamps
Pick the winner
Sort with MoSCoW
Set owner and date
Check it is in use

Building today 0 items

Judging and review 0 items

In use at work 0 items

Done 0 items

Related templates

← Back to templates