summaryrefslogtreecommitdiff
path: root/.gitlab/issue_templates/Technical Evaluation.md
blob: 680ecb7d9a65c326b663e3f9bab0f6353b312847 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
<!-- Instructions: Use this template for a proof of concept or when a deeper technical evaluation is required. Please weigh tech evaluation issues and follow the instructions below accordingly. --> 

### Topic to Evaluate

<!-- Describe the related issue and challenge we need to establish a proof of concept for-->
* [Link to other Issue](link)

### Tasks prior to evaluation

<!-- Pre-evaluation tasks are critical and should be completed or confirmed by product managers if available -->

- [ ] Clearly document the topic to evaluated in this issue description
- [ ] Determine specific scope including time-bounds for investigation

### Tasks to  Evaluate

<!-- Outline the tasks with issues that you need to evaluate as a part of the implementation issue -->

- [ ] Determine feasibility of the feature
- [ ] Create issue for implementation or update existing implementation issue description with implementation proposal 
- [ ] Set weight on implementation issue
- [ ] If weight is greater than 5, break issue into smaller issues
- [ ] Add task 
- [ ] Add task 

### Risks and Implementation Considerations 

<!-- Identify any risks found in the research, whether this is performance, impacts to other functionality or other bugs -->

### Team

- [ ] Add ~"workflow::planning breakdown" ~"type::feature" and the corresponding `~devops::<stage>` and `~group::<group>` labels.
- [ ] Ping the PM and EM.