Skip to content
Snippets Groups Projects
Commit 3d8a103a authored by James Hebden's avatar James Hebden
Browse files

Add details about priority labels for Vulnerability Management team

parent 8b2c5a09
No related branches found
No related tags found
Loading
......@@ -6,7 +6,15 @@ description: "Labels used in Vulnerability Management Engineering for scoring an
Vulnerability Management Engineering uses several sizing labels to indicate how much effort is estimated to be involved in adding a feature or addressing a bug described by an issue.
In addition to this, we use weights and milestones. The weights correlate to the labels and this all is designed to make planning out our milestones easy and predictable from a capacity management perspective.
## Labels
## Priority
We use the standard [GitLab Engineering Priority Labels](../../../engineering/infrastructure/engineering-productivity/issue-triage/#priority) to reflect the priority of individual issues. Priority is decided during milestone planning and is informed by company-wide critical projects, customer commitments and Vulnerability Management team priorities. Vulnerability Management team members are expected to follow the priority of issues assigned to them during a milestone and ensure they are working on the highest priority issues first.
## Sizing and estimation (Size labels & issue weight)
A single point of weight on an issue roughly represents a single day of engineering work for a single engineer.
For convenience, we also currently apply labels based on weight to give issues a rough size.
| Estimated Effort | Label | Weight |
|---------------------|----------------|----------------|
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment