Sample: How to Reflect on a Hackathon

This is a sample article for demonstrating the layout. Replace it with a hackathon you actually joined.

Start with the problem

A useful retrospective begins with a concrete problem. Who was the intended user? What was getting in their way? Why did the team choose this challenge?

Record the decisions

Describe the important tradeoffs in the order they happened, rather than listing tools. For example, a time budget $T$ might be divided among research, building, and the demo:

T = T_{\text{research}} + T_{\text{build}} + T_{\text{demo}}

If the scope changed, explain what evidence led the team to change course.

Show the outcome and reflect

This is a place for screenshots, a demo link, source code, awards, and what you would improve next time. Describe results that someone could verify instead of saying only that the project went well.