Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update engineering_spike.md #90

Closed
wants to merge 2 commits into from
Closed

Update engineering_spike.md #90

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0c064a6
Update engineering_spike.md
eileenruberto Apr 18, 2024
b96ab56
Update engineering_spike.md
eileenruberto Apr 22, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
39 changes: 34 additions & 5 deletions .github/ISSUE_TEMPLATE/engineering_spike.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,16 +2,45 @@
name: Engineering SPIKE
about: 'Start an engineering Spike'
title: 'SPIKE: '
labels: 'OCR'
labels: ''
assignees: ''

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Above on line 5, the label is currently set with the OCR label. So ATM(im pretty sure) this will only apply to issues being made for the OCR board, we probably could just add the dedupe label and it should work for both.

Copy link
Collaborator

@derekadombek derekadombek Apr 19, 2024 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Might be best to replace whats currently in the idwa_dedupe.yml with this new one?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@derekadombek I've removed the OCR label per @bryanbritten's suggestion in Slack:

FWIW I would prefer minimizing the number of "team-specific" resources that we use. The Research Spike Template is a good example of something that could be used across both teams, and would create consistency in how we track the work we're doing. My recommendation would be to simply remove the OCR label and request that any one creating a research spike ticket manually add the label for their team, and then the GH Action that Derek set up will take care of assigning it to the appropriate project.

---

Please describe the reason and goal of this spike
## Topic
Thing you are exploring/researching

**Acceptance Criteria**
Please write up a spike doc and save it to the drive and present the findings either in slack or as a techtalk in the dev sync meeting.
## Background
Brief description of the purpose and goal of this spike that provides enough of the recent history to show what led to this spike. Try to stick to the facts of the situation—beliefs/assumptions go in the Hypothesis section).

## Hypothesis
List any relevant hypotheses relevant to this research spike.

**Problem Hypothesis:**
We believe `state the problem identified` based on `state the supporting data`.

**Solution Hypothesis:**
By `state proposed solution`, we believe `user behavior change`, solving `user problem`.

**Objective**
What are we hoping to achieve with this research spike? How does learning about this contribute to our team’s goals and to end users? Some sample prompts below.

**Additional context**
```
Understanding this topic better will allow us to __________ .
The value of reducing uncertainty here is __________.
Our goal at the end of this research spike is to be able to __________.
The benefit to users (CDC or STLTs) is __________.
```

## Questions
Progress towards reducing uncertainty here will look like answering these questions:

- [Question 1]
- [Question 2]
- [Question 3]

## Acceptance Criteria
Please write up a spike doc and save it to the drive and present the findings either in slack or as a techtalk in the dev sync meeting.

## Additional context

Loading