Create WP3.7 six month plan for Oct'21 to Mar'22

[tms-epcc]

Topics to consider when creating this 6 month plan

• Rubin in-kind reporting

• in plan to Sep'21 in terms of organisation, practices and procedures

  • what worked well?
  • what did not work well?
  • what can we improve?
  • what should we keep?
  • what should we drop?

• [x] Identify any WP 3.7 task/ milestone/ deliverable dependencies with other LSST:UK WP tasks.

  • Note any such dependencies on relevant Kanban tickets
  • WP2.5.5 DAC-DEV interactions need to be included. When is the next meeting with DAC team?
  • LSST:UK Software Development Requirements eg. Software Management Plan
  • Rubin In-kind coding guidelines

• [x] Review the associated SRD requirements

  • are any changes needed?

• [x] Create a Zenhub Epic for the 6 month period

• [x] create tickets for latest 6 month objectives if necessary

• [x] Shift any outstanding tickets from previous plan if appropriate

  • Can these be broken down into smaller tasks/tickets?

• [x] Review previous 6 month plan Epic kanban

  • close tickets, remove duplicates as necessary

• [x] Is there sufficient effort available for all the chosen tickets?

  • Move tickets to stretch if necessary
  • Is effort still a concern after updating stretch?

• [x] Review risks

  • Is any escalation required?
  • Are there risks for those tasks/ tickets/ dependencies, … on the critical path?

• [x] Review the WP Brief

  • are any updates required?

[tms-epcc]

Risks reviewed at WP3.7 meeting on 07/OCT/21.