Skip to content

Instantly share code, notes, and snippets.

@vmariano
Last active October 28, 2022 20:49
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save vmariano/c579f25384af484f40ef7176ac9b431e to your computer and use it in GitHub Desktop.
Save vmariano/c579f25384af484f40ef7176ac9b431e to your computer and use it in GitHub Desktop.
This work as a "template".
The idea is leave the titles, and answer all questions (if apply if not, delete it)
```
Motivation/Context
What is the problem we're trying to solve or the goal we're trying to accomplish?
Is there history behind the issue that should be known?
Are there any relevant confluence pages or docs?
Implementation Plan
Where will we be making changes in code?
What are the technical constraints and how will they be solved?
Any there any new resources or tools we'll need to introduce as a part of this work?
Acceptance Criteria
How will we know when this work is complete?
Are there any out-of-scope items worth mentioning?
Risks
For updates/changes, what could this potentially break? UI, recommendations, orders?
Testing Plan
Which of our testing tools will help us best validate the outcome? Are there any examples that can be provided ahead of time?
Do we need to include QA on this?
Some other housekeeping considerations:
Is it linked to the right epic?
Does the label match the correct repo?
Is the ticket linked to other related tickets? (Should it be marked as blocking something else?)
Should this be broken down into smaller tickets?
Ideally, try to not leave larger tasks (more than 5p)
Does our work rely on other teams to deliver work? Do we need to create tickets for other teams?
```
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment