Instructions for workshop

[brentstineman]

Add instructions to the repository for running hack events. Be sure to include:

• key calls-outs from the previously used PPT
• adding a stock powerpoint for use during hacks
• coach/proctor notes
• suggestions for division of labor within the team
• call out items for the less technical participants

[brentstineman]

Additional feedback from a recent attendee: I would suggest that we put some thought into how we can better incorporate the non-coders into the hack in a way that leverages their skills (ie PM’s). ...

• Update the documentation to make it clear that you just need one person to stand-up the Azure Functions for the rest of the teams to connect to. We figured it out, but it was an unnecessary for me to walk Eti through this when really she just needed to use the paticle build portal to program her device.
• Have an active PM role defined that identifies the things that need to be done. This would mean having some PM-specific docs. But, it would give that person some impactful work to do during the hack. o Identify who(s) going to deploy the function. o Capture the necessary data for the device owners so they can code their game firm-ware (master-key, url, etc.) o Capture feedback from the team.