13.10 Planning for Compliance

Boards

Build Board - Build all the things!

Next Up Board - Collaboration time! 🔨 👖

Release Kickoff Video

TBRecorded

Capacity notes

  • Everyone – Friends & Family Day – 2021-02-26
  • @jiaan – 75% – OOO 2021-02-22 to 2021-02-26
  • @aregnery - Vacation 🏂 - 2021-03-01 to 2021-03-05

Objectives & Themes

Defining Success

The work we do should address high-priority customer needs, driving Other GMAU as well as increase our paid GMAU, viewing compliance features

Community Contributions

Deliverables

Legend

  • 📈 - New feature focused on adding value to the end user
  • 👣 - Iterating on an existing feature to improve it or fix a bug
  • 👁 - Backstage improvements or tech debt work
Status Issue Category Theme DRI / Thanks
gitlab-org/gitlab#287845 (closed) Category:Compliance Management @rob.hunt

Stretch Goal(s)

Next Up

To-Do

  • Define an approximate scope for the coming release.
  • Apply appropriate labels to issues:
    • Priority
    • Department
    • Pricing Tier
  • Review the proposed scope with Engineering.
  • Review design objectives with UX.
  • Get feedback and estimates from Engineering, confirming scope for the release.
  • Final verification of issues scheduled for the release.
  • Present selected issues in the Manage Kickoff on the 17th!
  • 🍺
Edited by Sam Kerr