Sprint Planning

• Triage all new issues into Build or Icebox
• Identify any bugs with severity greater than or equal to s.medium and triage into Sprint as needed.
• Review Roadmap to identify next theme in queue.
• Review sub-issues associated with theme.
  • Identify any dependencies or gaps.
  • Prioritize.
  • Review cost estimate.
  • Review capacity based on schedule.
  • Identify any issues that may need to be deferred based upon remaining schedule.
• Review team capacity to make sure we can complete open tasks.

---

Release Planning

• Triage and prioritize new issues.
• Review and prioritize Icebox (with help from SWG as needed)
• Identify any high priority issues
• Identify release themes
  • Identify gaps or dependencies for themes and sub-issues
• Add issues and themes to release
• Review capacity to ensure scope for release

---

Build Transitions

When transitioning from one build to another (e.g., B17 to B18), the following tasks need to be completed:

1. Update Issue Templates

Update the build label references in issue templates across the following repositories:

• NASA-PDS/.github
• NASA-PDS/pds4-information-model
• NASA-PDS/operations

Action: Replace all references to the current build label (e.g., B17) with the new build number (e.g., B18) in these issue template files.

2. Update GitHub Actions Workflow

Update the move-to-next-iteration.yml workflow file to reference the new build's GitHub project ID.

Action: Change the project ID in the workflow to match the new build's project:

• Example: B17 project had GitHub project ID 22, B18 has GitHub project ID 25

3. Handle Task Spillover

Identify any tasks or themes that were started in the previous build but will continue into the new build implementation period.

Action: For each continuing task/theme:

1. Add the task-spillover label to the issue
2. Add the new build label (e.g., B18) to the issue

Note: GitHub Actions will automatically add these issues to the new build's project board once the labels are applied.