The responsibilities of this team are described by the Manage product category. Among other things, this means working on GitLab's functionality around user, group and project administration, authentication, access control, and subscriptions.
We plan in monthly cycles in accordance with our Product Development Timeline. Release scope for an upcoming release should be finalized by the
To scope the release, Product is responsible for maintaining a prioritized list of issues. We use this prioritization board as the SSOT. Issues are tagged with the "prioritized" label and stack-ranked in the respective column. We use the following timeline:
24th: Product meets with Engineering Managers for a preliminary issue review. Issues are tagged with a milestone.
28th: Product takes the reviewed scope to the larger team for discussion. This becomes the release scope for the next release.
6th: Product meets with Engineering Managers for a pre-kickoff check-in.
Developers will start the release with assigned issues. If a developer has completed work on an issue, they may open the prioritization board and begin working on the next prioritized issue. Issues should be worked on in priority order (the "prioritized" column will always be sorted by descending priority; the issue at the top is most important).
8th, the Manage team conducts an asynchronous retrospective. You can find current and past retrospectives for Manage in https://gitlab.com/gl-retrospectives/manage/issues/.