Skip to content

Commit

Permalink
🔄 Templates: synced local '.github/ISSUE_TEMPLATE/epic_template.md' w…
Browse files Browse the repository at this point in the history
…ith remote '.github/ISSUE_TEMPLATE/epic_template.md'
  • Loading branch information
sovitybot committed Feb 7, 2024
1 parent 336f8ac commit fce0b5c
Showing 1 changed file with 13 additions and 32 deletions.
45 changes: 13 additions & 32 deletions .github/ISSUE_TEMPLATE/epic_template.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,52 +9,33 @@ assignees: ""
# Epic

## Description

_Brief summary of what this Epic is, whether it's a larger project, goal, or user story. Describe the job to be done, which persona this Epic is mainly for, or if more multiple, break it down by user and job story._
<!-- Brief summary of what this Epic is, whether it's a larger project, goal, or user story. Describe the job to be done, which persona this Epic is mainly for, or if more multiple, break it down by user and job story. -->

### Requirements

_Which requirements do you have to be fulfilled?_

- Requirement 1
- Requirement 2
<!-- Which requirements do you have to be fulfilled? -->

## Work Breakdown
<!-- If you already know what needs to be done, plase add a tasklist. -->

_Create Stories which can be converted into issues_

- [ ] Story 1
- [ ] Story 2
- ...
```[tasklist]
### Stories
- [ ] Create Stories which can be converted into issues
```

## Initiative / goal

_Describe how this Epic impacts an initiative the business is working on._
<!-- Describe how this Epic impacts an initiative the business is working on. -->

### Hypothesis

_What is your hypothesis on the success of this Epic? Describe how success will be measured and what leading indicators the team will have to know if success has been hit._
<!-- What is your hypothesis on the success of this Epic? Describe how success will be measured and what leading indicators the team will have to know if success has been hit. -->

## Acceptance criteria and must have scope

_Define what is a must-have for launch and in-scope. Keep this section fluid and dynamic until you lock-in priority during planning._

- Criteria 1
- Criteria 2
- ...
<!-- Define what is a must-have for launch and in-scope. Keep this section fluid and dynamic until you lock-in priority during planning. Please list your criteria below. -->

## Stakeholders

_Describe who needs to be kept up-to-date about this Epic, included in discussions, or updated along the way. Stakeholders can be both in Product/Engineering, as well as other teams like Customer Success who might want to keep customers updated on the epic project._
<!-- Describe who needs to be kept up-to-date about this Epic, included in discussions, or updated along the way. Stakeholders can be both in Product/Engineering, as well as other teams like Customer Success who might want to keep customers updated on the epic project. -->

## Timeline

_What's the timeline for this Epic, what resources are needed, and what might potentially block this from hitting the projected end date._
<!-- What's the timeline for this Epic, what resources are needed, and what might potentially block this from hitting the projected end date. -->

## Need for refinement

_Which questions are open? From whom do you need more input to fully specify the epic?_

- Question 1
- Question 2
- ...
<!-- Which questions are open? From whom do you need more input to fully specify the epic? -->

0 comments on commit fce0b5c

Please sign in to comment.