@@ -208,7 +208,7 @@ The shared services and components below are extracted from the GitLab [product
| Email - Outbound | | | |
| Elasticsearch | Centralized with Specific Team | @changzhengliu<br/>Global Search | |
| GitLab K8S Agent | Centralized with Specific Team | @nicholasklick<br/>Configure | |
| GitLab Pages | Centralized with Specific Team | @vshushlin<br/>[Knowledge](/handbook/engineering/devops/plan/knowledge/) | |
| GitLab Pages | Centralized with Specific Team | @armin.pasalic<br/>[Planner Intelligence](/handbook/engineering/devops/plan/planner-intelligence/) | |
| GitLab Rails | Decentralized | | DRI for each controller is determined by the feature category specified in the class. [app/controllers](https://gitlab.com/gitlab-org/gitlab/-/tree/master/app/controllers) and [ee/app/controllers](https://gitlab.com/gitlab-org/gitlab/-/tree/master/ee/app/controllers) |
| GitLab Shell | Centralized with Specific Team | @andrevr<br/>[Create:Source Code](/handbook/engineering/devops/create/source-code/backend/) | [Reference](/handbook/product/categories/#source-code-group-1) |
| HAproxy | Centralized with Specific Team | [Infrastructure](/handbook/engineering/infrastructure-platforms/production-engineering/networking-and-incident-management/) | |
The responsibilities of this collective team are described by the [Plan stage](/handbook/product/categories/#plan-stage). Among other things, this means
working on GitLab's functionality around issues, boards, milestones, to-do list, issue lists and filtering, roadmaps, time tracking, requirements management, notifications, value stream analytics (VSA), wiki, and pages.
@@ -16,7 +16,7 @@ working on GitLab's functionality around issues, boards, milestones, to-do list,
In GitLab issues, questions should start by @ mentioning the Product Manager for the [corresponding Plan stage group](/handbook/product/categories/#plan-stage). GitLab team-members can also use [#s_plan](https://gitlab.slack.com/messages/C72HPNV97).
For UX questions, @ mention the Product Designers on the Plan stage; [Nick Leonard](https://gitlab.com/nickleonard) for Plan:Project Management, [Nick Brandt](https://gitlab.com/nickbrandt) for Plan:Product Planning, and [Libor Vanc](https://gitlab.com/lvanc) for Plan:Optimize. Plan:Knowledge should follow the [process for groups without a designer](/handbook/product/product-processes/).
For UX questions, @ mention the Product Designers on the Plan stage; [Nick Brandt](https://gitlab.com/nickbrandt) for Plan:Portfolio Planning. Plan:Planner Intelligence should follow the [process for groups without a designer](/handbook/product/product-processes/).
### How we work
@@ -267,10 +267,10 @@ An example of a valid single OKR hierarchy is:
```mermaid
flowchart TD
A[Plan Objective] --> B(Project Management KR)
A --> C[Product Planning KR]
A[Plan Objective] --> B(Work Items KR)
A --> C[Portfolio Planning KR]
A --> D[Optimize KR]
A --> E[Knowledge KR]
A --> E[Planner Intelligence KR]
A --> K[Principal Engineer KR]
A --> L[SEM KR]
```
@@ -382,11 +382,11 @@ Issues marked with this label are prioritized alongside those proposing new feat
### UX
The Plan UX team supports [Product Planning](/handbook/product/categories/#product-planning-group), [Project Management](/handbook/product/categories/#project-management-group) and [Optimize](/handbook/product/categories/#optimize-group). Product Planning and Project Management are focused on the work items architecture effort. This page focuses mainly on the specifics of how we support this, since it requires alignment and cross-group collaboration.
The Plan UX team supports [Portfolio Planning](/handbook/product/categories/#portfolio-planning-group), [Work Items](/handbook/product/categories/#work-items-group) and [Planning Views](/handbook/product/categories/#planning-views-group). Portfolio Planning and Work Items are focused on the work items architecture effort. This page focuses mainly on the specifics of how we support this, since it requires alignment and cross-group collaboration.
#### UX issue management, weights and capacity planning
Product Planning, Project Management and Optimize will create issues for UX work and pre-pend the title with [UX]. Here is an example - https://gitlab.com/groups/gitlab-org/-/epics/10224#note_1337213171+
Portfolio Planning, Work Items and Planning Views will create issues for UX work and pre-pend the title with [UX]. Here is an example - https://gitlab.com/groups/gitlab-org/-/epics/10224#note_1337213171+
- UX issues are the SSOT for design goals, design drafts, design conversation and critique, and the chosen design direction that will be implemented.
- Product requirement discussions should continue to happen in the main Issue or Epic as much as possible.
@@ -550,18 +550,18 @@ The meeting was removed as its functions are now covered in other ways:
@@ -653,13 +653,10 @@ Like all groups at GitLab, a working group is an arrangement of people from diff
Stage Working Groups are focused on initiatives that require collaboration between multiple groups within the stage. The structure of stage working groups is similar to [company-wide working groups](/handbook/company/working-groups/), with DRI and well-defined roles. The initiatives are driven by a stage-level product direction rather than an [Executive Sponsor](/handbook/company/working-groups/#executive-sponsor),
and can be formed of just Functional Leads and members who participate in fulfilling the exit criteria.
#### Active Stage Working Groups
1.[Work Items API Performance](/handbook/engineering/devops/plan/working-groups/work-items-api-performance/)
#### Archived Stage Working Groups
1.[Epic Work Items Migration](/handbook/engineering/devops/plan/working-groups/epic-work-items-migration/)
1.[Work Items API Performance](/handbook/engineering/devops/plan/working-groups/work-items-api-performance/)
### Product Outreach
@@ -720,4 +717,4 @@ By continually monitoring these tables and applying the planned mitigations, we
@@ -39,7 +39,7 @@ Engineering Manager adds the following labels at the start of the milestone:
| `~Deliverable` | We have committed to customers that we will deliver this item in the current milestone. |
| `~Stretch` | We have not committed to deliver the item but will attempt to make progress on it |
It's OK not to take the top item if you are not confident you can solve it, but please post in `#g_knowledge`.
It's OK not to take the top item if you are not confident you can solve it, but please post in `#g_planner-intelligence`.
### Capacity
@@ -49,7 +49,7 @@ When estimating the effort involved in upcoming work, we use the same approach a
{{% include "includes/engineering/plan/estimating-effort.md" %}}
Typically, 3-month rolling average is a good indicator of the team's capacity. Knowledge is a new team and determining capacity will be difficult at the beginning without clear historical data.
Typically, 3-month rolling average is a good indicator of the team's capacity. Planner Intelligence is a new team and determining capacity will be difficult at the beginning without clear historical data.
The PM and EM will work to fit ~Deliverable issues into no more than 75% of the team's capacity and allocate the rest to ~Stretch issues.
@@ -111,7 +111,7 @@ Links to previous examples. Discussions on prior art. Notice examples of the sim
#### Board-Walk (weekly)
Team-members meet to walk the [Build Board](https://gitlab.com/groups/gitlab-org/-/boards/5454834) once a week. 25 minutes are allocated for this sync call but it may be completed much more quickly than that. The EM is DRI and attendance is optional except for PM. It is recorded and shared in the [#g_knowledge Slack channel](https://app.slack.com/client/T02592416/C04R571QF5E). The recording will be made public only if no security or other confidential issues are discussed. The [agenda](https://docs.google.com/document/d/1SZrFiipmH5GX5CYL-nOuc8NNqSs-AXCvHOzajwy06vk/edit?usp=sharing) is available internally and all team-members are encouraged to contribute updates and questions.
Team-members meet to walk the [Build Board](https://gitlab.com/groups/gitlab-org/-/boards/5454834) once a week. 25 minutes are allocated for this sync call but it may be completed much more quickly than that. The EM is DRI and attendance is optional except for PM. It is recorded and shared in the [#g_planner-intelligence Slack channel](https://app.slack.com/client/T02592416/C04R571QF5E). The recording will be made public only if no security or other confidential issues are discussed. The [agenda](https://docs.google.com/document/d/1SZrFiipmH5GX5CYL-nOuc8NNqSs-AXCvHOzajwy06vk/edit?usp=sharing) is available internally and all team-members are encouraged to contribute updates and questions.
The purpose of this meeting is to:
@@ -120,7 +120,7 @@ The purpose of this meeting is to:
- Reprioritize
- Ask for help
DRIs should keep issues up to date with [workflow labels](/handbook/engineering/devops/plan/knowledge/#use-of-labels) and [health status](/handbook/engineering/devops/plan/#keeping-health-status-accurate) on an ongoing basis rather than waiting for this meeting.
DRIs should keep issues up to date with [workflow labels](/handbook/engineering/devops/plan/planner-intelligence/#use-of-labels) and [health status](/handbook/engineering/devops/plan/#keeping-health-status-accurate) on an ongoing basis rather than waiting for this meeting.
#### Planning Meeting (monthly)
@@ -226,12 +226,12 @@ To avoid rework we reach out to other teams early when working on the following
Additional dashboards are available in Grafana that show application performance of parts of the application for which the team is responsible.
-[Plan:Knowledge](https://gitlab.com/groups/gitlab-org/-/boards/1569369?scope=all&utf8=%E2%9C%93&state=opened&label_name[]=group%3A%3Aknowledge) - Apply a milestone filter to see work in the current release
-[Plan:Planner Intelligence](https://gitlab.com/groups/gitlab-org/-/boards/1569369?scope=all&utf8=%E2%9C%93&state=opened&label_name[]=group%3A%3Aplanner%20intelligence) - Apply a milestone filter to see work in the current release
-[#s_plan](https://gitlab.slack.com/archives/s_plan) in Slack
