Hackathon Review Methods


  • Video Camera
    • Lots of information will take several times more than recorded time to just extract usefull data from it. 
  • Microphone
    • Misses what how the code looks at the moment of discussion, will also take several times the recorded time to extract data
  • Notes
    • Handles less data, but extracting data will be easier. <- Prefered way
    • Should be used in conjucture with a camera to take pictures of code

Using: Notes


  • One or two people take notes
  • None of the note-takers are allowed to help any of the participants
    • unless: request is minor
      • minor request takes less than 1 minute to solve and should require the note-taker to more than 1-2 rows of code
  • Important points to note down (always take pictures if extra information can be gained, take note when picture is taken))
    • Problems encountered during development
    • Discussions regarding how to use the car signals
    • Positive experiences, what worked?
    • Negative experiences, what frustrated people?
    • Was there something they wanted to use our SDK for but could not?
    • Was there something they did not understand and needed clarification?
    • When do they request help? Where in the development phase are they?
    • What are the topics of the help requests?
      • Note down all requests that are heard
    • What are the most prominent questions?
      • Note down how often they are asked
    •