We decided to hold hack days on a more regular 6-week cycle. For this hack day we decided to hold a remote event, looking at a tech improvement challenge, one Discovery, two-team approach, and to follow the GDS Agile Delivery framework which worked well last Hack day.
General benefits of a hack-day:
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
maintain focus on one task for a whole day
Table of contents
Topic selection processWe came to organising this hack day quite late. As a result we decided to look at our backlog and select something that was an investigation-type ticket that would involve the whole team. Andy Dingley , John Simmons (Deactivated) and Cai Willis assisted Andy Nash (Unlicensed) in organising this one. We decided on investigating the longer term approach to Monitoring and alerting because … | . | |
Subject matter experts. | Team members. | |
Structure of the day
| ||
Hack day Retro |
|---|
Hack day Retros are best carried out at the end of a Hack day, while everything is still fresh in everyone’s minds. Because of time and teleconferencing constraints, this was unfortunately not possible. Many participants were sick / on leave in the following few days. |
Add Comment