Manage project reporting, impact capture, ways of work

[Davsarper]

Goal Title

DSH produces required reports and is able to clearly communicate the project impact

Description

Project reports
Impact communication
Mangement repo and roadmap maintenance
Meeting templates and structure

Definition of Done

Quarterly, and after relevant milestones the is a comprnehensive report

Monthly the team is able to communicate and work effectively, progress is clearly communicated during meetings and there is an associated PR or document

Details

• RACI
  • Accountable team or person:
  • Responsible team or person:
  • Informed and consulted people:
• Estimated effort in total FTE: 0.12
  • RAM: 0.05

Resourcing

August

• RPM: 0.05

Task and issue breakdown

Breakdown in specific tasks of maximum a month duration, tasks and issues may be added as necessary
Issues may span across repositories when necessary

• Ways of work: create project and documentation #44

Checklist

• This Story have been agreed with project members, it tackles prioritised work
  • If not: Label as ForPrioritisation so it discussed in the next monthly meeting, do not set a status
• I have filled in the Team Accountabe field
• I have included this Story in the agreed upon Milestone, set status as Planned
  • If not: set status as Backlog, to be Planned via weekly meetings or async discussions
• The work to be done is likely to span over a month
• I have broken down the work in monthly issues and added them above
• I have labeled this issue according to its main project: SATRE, TRESA, CORE DSH (ELA) or other (please agree and create a new label if necessary)
• If known: sum the total effort (points) of tracked issues and add it on the body
• Select a Story level of effort in the project fields

Reporting

5 December to 8 January 2024

Closed PRs, submitted progress report for UK TRE Community and prepared for the new year (planned planning and strategy sessions)

1 November to 4 December

We have dedicated a long Planning meeting to review priorities for December but also for the new year, as well as discussed possible strategies for different strands of work. Also identified items to be brought to the monthly meeting.

Have prepared meeting series for 2024 ans starting to thing which other meetings will be needed i.e. strategy review.

Have updated WoW document in this pending PR, agreed to co-apply to next TTW Book Dash to write and publish usecase.

10 October to 30 October

• A priority has been the programme 6 monthly report that can be found here
• In producing this report we have used the stories monthly reports to populate, it has been highly useful and required less time and improved thoroughness.
  • Some times weekly/monthly reports are "list of actions" and do not capture value/outputs. This is improving as we continue to report weekly, some futher attention will be put into asking for more details when necessary

10 July to 14 August 2023

• The team was involved in discussing the proposed ways of work, it was decided that they needed to be streamlined. To do so the focus has been put in updating the weekly meeting notes and the PM and story accountable persons driving reporting efforts (PM prepares, story/project leaders complete and approve)
  • Ways of work principles have been added as a result
  • The weekly template has been updated to reflect this
  • WaysofWork require furhter changes to reflect the above

[Davsarper]

Questions from the team regarding ways of work (evaluate where to best put this):

• Do we need to open an issue for everything we do? How much time does that take? We already have issues and places to update them, to update in yet another place can be burdensome.
• What about other repos, especially repos not owned by the Turing org?
• Will people appreciate being pinged in our project management repo?
• What happens when we have information we can’t or shouldn’t share publicly?

[jemrobinson]

Plan to capture publication strategy here. This includes:

• Tiers/design paper (on arXiv but not published)
• v4 Implementation paper (on Overleaf but not arXiv or published)
• SATRE work (spread across medium blogs + specification page)

[Davsarper]

October: both ELA and SATE ends, reportng due and 6 monthly

[Davsarper]

Dec planning

Some end of the year report needs done, not really a rpiority. Esp Community call.

Re-viewing PRs, nudge adn re-request.

TTW: co-apply to next bookdash and do it

[harisood]

Jan planning

Focus is not this now, it's mainly strategy planning/review etc