Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Actions from previous Retros

2022-11-01: Hack day – dual location in-person event

Actions

2022-03-08: Hack day – Open house

Next time

  1. Clearly decide at the start whether the problem statement your team is working on lends itself to UCD, Agile, etc.

  2. More rapid planning at the start of the day to get a clearer course of action from the start.

  3. Consider JFDI the 1st solution to gain insight to inform how you modify it and/or develop other solutions to the problem statement.

Follow ups

  1. Review ideas - add to backlog / save for future Retros / discard?

  2. Take chatbot idea and run with it - present at Review, with a cross-reference to having had a Hack day.

  3. Hack days are safe spaces to conceive experiments against problems, build them out and have fun. Do we need to review any outputs before presenting relevant ones to users, or do we present the raw outputs in the context of this is a PoC created during a Hack day?

  • No labels

Slack: https://hee-nhs-tis.slack.com/
Jira issues: https://hee-tis.atlassian.net/issues/?filter=14213