debian-mirror-gitlab/.gitlab/issue_templates/Productivity Improvement.md

40 lines
1.3 KiB
Markdown
Raw Normal View History

2020-05-24 23:13:21 +05:30
## What is the GitLab engineering productivity problem to solve?
2020-01-01 13:55:28 +05:30
<!--
2020-05-24 23:13:21 +05:30
Please describe the engineering productivity problem that needs to be solved backed by charts from
2020-01-01 13:55:28 +05:30
https://about.gitlab.com/handbook/engineering/quality/engineering-productivity-team/#engineering-productivity-team-metrics.
-->
### Problem identification checklist
- [ ] The root cause of the problem is identified.
- [ ] The surface of the problem is as small as possible.
## What are the potential solutions?
<!--
Please provide potential solutions here. Example solutions could be:
- Dogfood a feature.
- Refactor/improve some workflow code.
- Throw more money at the problem.
Please provide pros/cons and a weight estimate for each solution.
-->
- [ ] All potential solutions are listed.
- [ ] A solution has been chosen for the first iteration: `PUT THE CHOSEN SOLUTION HERE`
## Verify that the solution has improved the situation
<!--
Ideally, looking at the charts from the first part, we should see an improvement
after the implementation is merged/deployed/released.
-->
- [ ] The solution improved the situation.
- If yes, check this box and close the issue. Well done! :tada:
- Otherwise, create a new "Productivity Improvement" issue. You can re-use the description from this issue, but obviously another solution should be chosen this time.
/label ~"Engineering Productivity" ~meta