15.7 Runner Group iteration plan

The details in this issue cover the top priority work items for the Runner team for the 15.7 release.

Kickoff Video

🟢 15.7 Iteration Planning Schedule

  • Oct 17: PM creates Slack channel for iteration planning and invites Elliot, Gina, Zeff @DarrenEastman
  • Oct 17: PM identifies the candidate features for 15.7. It is **not **required that the issue include a proposed solution or implementation plan. @DarrenEastman
  • Oct 17: QA validates candidate bugs for Runner Core. @zeffmorgan
  • Oct 24: Engineering starts refining issues in the iteration plan. @erushton
  • Oct 31: EM Ready to prioritize maintenance work @erushton
  • Nov 7: Refinement - all issues have a proposal or proposed solution. This also includes a response/counter to the “size” of the list (what we think we can commit to, what needs to get pushed out) - first draft.
  • Nov 11: Refinement due - with iteration allowing for any carryover from prior milestone - lock in our “say” for the say/do ratio.
  • Nov 14: Assign issues to developers. @erushton
  • Nov 15: PM & design lead records the Runner group kickoff video. @DarrenEastman @gdoyle
  • Nov 22: Start work on 15.7
  • Dec 17: Code freeze 15.7. Calculate the say/do ratio.
  • Dec 22: Ship 15.7.

Forced Prioritization + FedRamp

Note on priority: The top priority in each iteration plan is first to 100% resolve any issues in this list:

Next Runner Token Architecture project

Runner Core 🏃

Note on priority: The top priority in each iteration plan is first to resolve open security 🔒 issues.

Bugs - missed previous milestone 🐛

Bugs - candidate bugs for this milestone 🐛

Features

Maintenance 🏚️

R&D / Spikes 🤔

Runner Fleet 🎢

Bugs 🐛

Features

User Experience ✈️ 🖌️

R&D / Spikes 🤔

Edited by Georgi N. Georgiev | GitLab