Create monthly report for April and agenda

[Davsarper]

Encompassing February and March progress, first report of the "new" re porting period.

It should improve format based on feedback and include as well monthly prioritisation and justification for it so it can be properly discussed.

Refer to https://github.com/alan-turing-institute/data-safe-haven-team/pull/69/files for feedback, as well as the monthly meeting notes https://hackmd.io/jPtV0qljTDG-6K9DDU1mPw

Collate agenda items:

• PI's ways of work proposal
• Review of stories and sprints: too many open ended issues
• Grant/fund opportunities

[Davsarper]

Report feedback

• add dates
• Chronological order for actions rather than reverse
  • Comprenhensive summaries are even better than any list
• Add DoD as much as possible
• it neeeds some discussion space/where to discuss priorities

[Davsarper]

Unresolved conversation from previous report

• Documentation management definition of done
• TRESA story(ies): work with them to create the right reporting structure, define work. Even define our relationship, a prefferential client or a team, what capacity has the research project to dictate their work?
  • Related: they need PM time, even when this ends up in the same person it is two jobs.
• SATRE stakeholder engagement: phrasing and approach of the work to convey our involvement (even if done in conjuction with tre community) - "we are working to open ownership of SATRE to stakeholders through UK TRE (which we are dedicated members of)"
• Stakeholder landscape review definition of done, and general goals need revision. Is it big enough for a story?
• Some reporting and stories need rethinking, and consider if the activities are stories or not (and if not, make room for them in the reporting to recognise them equally)
  • Programme management: lot's of the time we report the work in this story within others
  • Communications
  • Events, like AI UK
  • This ties with report format, but a lot of work can get hidden into a "mere" bullet point
• Track external users and engagement with them, in particular Nottingham. Requires its own story which can imply rephrasing the existing one or splitting
• Action: Make project strategy openly available (add to repo)
• Action: archive this in a folder and somewhere else than a hackmd https://hackmd.io/kh6siuZcTdCxcfYryAvypw)

[Davsarper]

I am (have been) finding it difficult to turn weekly reports into monthly reports, due to lack of clarity on what the short terms goals are and why. We end up with statement on the actions but with little context, to some extent comments from planning meeting should help to this and I could include that into the report (and weekly?)

[Davsarper]

Proposed sprints should be included for consideration https://hackmd.io/@nHslnPpLRmCxPOmQBcOW-g/Byy0S9RKT