Skip to content

Pipeline Execution 17.7 Planning issue

TODO - how to create this item

  • Title this issue Pipeline Execution X.Y Planning issue
  • Update Goals and theme for the issue. These roll up to larger OKRs the team is working on or large initiatives.
  • Add VerifyP1 issues Product would like to prioritize for release, these should contribute to the goals and theme
  • Add VerifyP2 issues that are secondary / Stretch goals or would further contribute to the theme and OKRs
  • Identify any Security, Infrastructure, Bug etc. issues that should prioritized per Global Prioritization
  • Delete this todo list

What's the focus, where can I find issue candidates for the milestone?

Issue Boards

PE workflow board | Issues by Team Member

Current/Upcoming Security issues

Recordings 🎥

  • Refinement Kickoff - TBD
  • Group Kickoff - TBD

Theme: Security & Availability

Goals for the milestone (consider OKR and Yearly Alignment)

  1. Fix Denial of Service Security Issues
  2. Fix Infradev issues that can impact .com availability
  3. Implement a POC for GitHub Integration

Issues of note

This is a breakdown of the issues in the milestone. For more information about how we prioritize check out the handbook page.

Scheduled for 17.7

Deliverable

17.7 Candidates

Please prioritize the following issues for delivery in the milestone

VerifyP1 Issues

VerifyP2 Issues

Planning Tasks

  • PM highlights work for Deliverables, User Experience, Bug Fixes, Security Fixes, Technical Debt sections
  • PM describes how this milestone aligns with the company's OKRs
  • PM notes target percentages for cross functional prioritization
  • By 7th - DRI for milestone refinement assigns issues with ~needs weight label in ~workflow::planning breakdown to engineers for review ahead of the milestone kickoff.
  • By 11th - DRI for milestone refinement follows up with engineers about issues not in ~workflow::read for development
  • By 14th - EM assigns any unassigned issues in the milestone
  • By 16th - The team has discussed potential ~Deliverable and ~Stretch labels and have indicated commitment with a 👍 or 👎 in the planning issue.
  • By 19th - EM reviews ~deliverable and ~stretch labels to assigned to issues.
  • By 19th - EM ensures all issus are assigned.
  • EM / PM remove any remaining issues form ~workflow::planning breakdown
  • Engineers begin working on issues in workflow::ready for development

Reference for How We Plan

Edited by Rutvik Shah