| Table of Contents | ||||
|---|---|---|---|---|
|
We decided a Hack day was long overdue! Hack days are great opportunities to do a bunch of things:
practice collaboration outside the normal group of people you collaborate with
test your specialist skills, or, conversely, test your non-specialist skills
challenge a group of people that may not always work together to plan a time-bound task
examine how the team approaches that task - Agile / UCD
(e.g. plan an hour, reconvene, check with client, plan another hour, reconvene, check with client etc /
research, clarify context, confirm problem statement, hypothesise and experiment to a PoC)maintain focus on one task for a whole day
| Table of Contents | ||||
|---|---|---|---|---|
|
Lean coffee 'ideation' session
Using a Mural board to give everyone the opportunity to present any ideas they had that the group could then vote on as the most popular subject for a day of teamwork.
Ideas put forward were attributed to their proposer.
Dot-voting
on the range of ideas (using a neat in-built Mural function).
narrowed the list of ideas down to 5 (all receiving 3 votes each).
followed by sticking names next to the idea each individual wanted to work on during the day.
for the most voted on ideas, the proposer of the idea became the de facto ‘Client’ for that idea. They were still allowed to work on their idea, but would be the first port of call for anyone who had questions about the idea, and could be the user to bounce off when it came to experimentation.
Split into teams
…with some suggestions of things to think about
Split the day into morning (10:45-12:15) and afternoon (13:00-15:30) sections, with AndyN checking in to see if anyone needed any help at the start of each session and from time to time throughout.
Both teams began by asking the ‘Client’ to provide more context to the idea so that the team were all on the same page
Team Alpha: Chatbot
Questions to consider answering about how the day went
Team One Data Wranglers!
Team to add what they did, how they got on, observations, etc
Team to add what they did, how they got on, observations, etc