-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add "user story" issue template (#220)
* Add initial "user story" template * Update .github/ISSUE_TEMPLATE/story.md
- Loading branch information
1 parent
5ab94b0
commit b58815c
Showing
1 changed file
with
64 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,64 @@ | ||
--- | ||
name: Story | ||
about: Suggest a user story for this product | ||
title: '' | ||
labels: story | ||
assignees: '' | ||
projects: ['GSA-TTS/17'] | ||
--- | ||
|
||
## Overview | ||
|
||
As a _, I would like _, so that I can _. | ||
|
||
## Context | ||
|
||
*Optional: Any reference material or thoughts we may need for later reference, or assumptions of prior or future work that's out of scope for this story.* | ||
|
||
- [ ] | ||
|
||
## Acceptance Criteria | ||
|
||
*Required outcomes of the story* | ||
|
||
- [ ] | ||
|
||
## Research Questions | ||
|
||
- *Optional: Any initial questions for research* | ||
|
||
## Tasks | ||
|
||
*Research, design, and engineering work needed to complete the story.* | ||
|
||
- [ ] | ||
|
||
## Definition of done | ||
|
||
The "definition of done" ensures our quality standards are met with each bit of user-facing behavior we add. Everything that can be done incrementally should be done incrementally, while the context and details are fresh. If it’s inefficient or “hard” to do so, the team should figure out why and add OPEX/DEVEX backlog items to make it easier and more efficient. | ||
|
||
- [ ] Behavior | ||
- [ ] Acceptance criteria met | ||
- [ ] Implementation matches design decisions | ||
- [ ] Documentation | ||
- [ ] ADRs (`/documents/adr` folder) | ||
- [ ] Relevant `README.md`(s) | ||
- [ ] Code quality | ||
- [ ] Code refactored for clarity and no design/technical debt | ||
- [ ] Adhere to separation of concerns; code is not tightly coupled, especially to 3rd party dependencies; dependency rule followed | ||
- [ ] Code is reviewed by team member | ||
- [ ] Code quality checks passed | ||
- [ ] Security and privacy | ||
- [ ] Automated security and privacy gates passed | ||
- [ ] Testing tasks completed | ||
- [ ] Automated tests pass | ||
- [ ] Unit test coverage of our code >= 90% | ||
- [ ] Build and deploy | ||
- [ ] Build process updated | ||
- [ ] API(s) are versioned | ||
- [ ] Feature toggles created and/or deleted. Document the feature toggle | ||
- [ ] Source code is merged to the main branch | ||
|
||
## Decisions | ||
|
||
- *Optional: Any decisions we've made while working on this story* |