For more details about the vision for this area of the product, see the Plan stage page.
From an engineering perspective, we are also responsible for the code backing our GraphQL API. This does not mean we own everything about the API - each team is responsible for implementing its own resources in GraphQL - but we are responsible for the overall stewardship of this API.
|Jake Lear||Backend Engineering Manager, Plan:Project Management|
|Brett Walker||Senior Backend Engineer, Plan:Project Management|
|Mario de la Ossa||Backend Engineer, Plan:Project Management|
|Heinrich Lee Yu||Senior Backend Engineer, Plan:Project Management|
|Alexandru Croitor||Backend Engineer, Plan:Project Management|
|Gabe Weaver||Senior Product Manager, Plan:Project Management|
|Holly Reynolds||Senior Product Designer, Plan:Project Management|
|Marcin Sędłak-Jakubowski||Technical Writer, Plan|
|Donald Cook||Frontend Engineering Manager, Plan|
|Simon Knox||Senior Frontend Engineer, Plan:Project Management|
|Eulyeon K.||Frontend Engineer, Plan|
|Scott Stern||Frontend Engineer, Plan:Project Management|
|Coung Ngo||Frontend Engineer, Plan:Project Management|
|Désirée Chevalier||Software Engineer in Test, Plan:Project Management (primary) & Plan:Portfolio Management (secondary)|
|Mike Long||Product Design Manager, Plan & Manage|
|Justin Farris||Group Manager, Product Management, Plan|
This chart shows the progress we're making on hiring. Check out our jobs page for current openings.
We have a metrics dashboard for the Plan:Project Management backend team. This is intended to track against some of the Development Department KPIs, particularly those around merge request creation and acceptance. Below is a single metric from that dashboard: MR Rate, scoped to this team.
You can see how we work as a stage at the Plan stage page.
For the backend team specifically, we use the standard GitLab engineering workflow. To get in touch with the Plan:Project Management backend team, it's best to create an issue in the relevant project (typically GitLab CE) and add the ~"group::project management" label, along with any other appropriate labels. Then, feel free to ping the relevant Product Manager and/or Engineering Manager as listed above.
For more urgent items, feel free to use #s_plan on Slack.
We use a lightweight system of issue weighting to help with capacity planning, with the knowledge that things take longer than you think. These weights are used for capacity planning and the main focus is on making sure the overall sum of the weights is reasonable.
It's OK if an issue takes longer than the weight indicates. The weights are intended to be used in aggregate, and what takes one person a day might take another person a week, depending on their level of background knowledge about the issue. That's explicitly OK and expected.
These weights we use are:
|1||Trivial, does not need any testing|
|2||Small, needs some testing but nothing involved|
|3||Medium, will take some time and collaboration|
|4||Substantial, will take significant time and collaboration to finish|
|5||Large, will take a major portion of the milestone to finish|
Anything larger than 5 should be broken down if possible.
We're discussing a possible change to the weight scale we use.
We look at recent releases and upcoming availability to determine the weight available for a release.
Estimating bugs is inherently difficult. The majority of the effort in fixing bugs is finding the cause, and then a bug be accurately estimated. Additionally, velocity is used to measure the amount of new product output, and bug fixes are typically fixes on a feature that has been tracked and had a weight attached to it previously.
Because of this, we do not weigh bugs during ~"workflow::planning breakdown". If an engineer picks up a bug and determines that there will be a significant level of effort in fixing it (for example, a large migration is needed, or we need to switch state management to Vuex on the frontend), we then will want to prioritize it against feature deliverables. Ping the product manager with this information so they can determine when the work should be scheduled.
To assign weights to issues in a future milestone, we ask two team members to take the lead each month. They can still ask questions - of each other, of the rest of the team, of the stable counterparts, or anyone else - but they are the initial.
To weight issues, they should:
The rotation for upcoming releases is:
| Release | Weights due | Engineer | Engineer | | — | — | — | — | | 13.5 | 2020-09-13 | | |
Points of weight delivered by the team on the last three milestones, including rolling average. This allows for more accurate estimation of what we can deliver in future milestones. Full chart here.
The Plan:Project Management Build board always shows work in the current release, with workflow columns relevant to implementation. There is an additional column to show in-progress community contributions. Filtering it by ~backend shows issues for backend engineers to work on.
It's OK to not take the top item if you are not confident you can solve it, but please post in #s_plan if that's the case, as this probably means the issue should be better specified.
Everyone at GitLab has the freedom to manage their work as they see fit, because we measure results, not hours. Part of this is the opportunity to work on items that aren't scheduled as part of the regular monthly release. This is mostly a reiteration of items elsewhere in the handbook, and it is here to make those explicit:
When you pick something to work on, please: