Skip to content

Commit 9d3dca2

Browse files
AttamuscAttamusc
authored
Merge pull request DataDog#4 from github/attamusc/feat/add-member
feat: Add templates for planning
2 parents 32b27c0 + ee3b2e5 commit 9d3dca2

5 files changed

Lines changed: 176 additions & 0 deletions

File tree

‎.github/ISSUE_TEMPLATE/01_bug-report.md‎

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
---
2+
name: Bug report
3+
about: Create a report to help us improve
4+
title: "[Bug] "
5+
labels: "bug, monolith-platform"
6+
assignees: ""
7+
---
8+
9+
<!-- Please fill in a much as you can of this issue template. It's OK to leave sections blank if you don't have that information.
10+
Describe the bug with as much detail as possible. -->
11+
12+
<!-- Note: If you include screenshots, images, and other visual media, please include alt text or, if there are several of them, a higher level written explanation of what's represented in the images. -->
13+
14+
### Describe the bug
15+
16+
<!-- Please add a brief description of the bug that you found. Please include screenshots if possible. -->
17+
18+
### Expected behavior
19+
20+
<!-- How should things work if the bug wasn't there? What did you expect to happen? -->
21+
22+
### Steps to reproduce
23+
24+
<!-- How can we replicate the bug the same way that you found it? What steps should we take to reach a similar result? Use a numbered list format. -->
25+
26+
### Device information
27+
28+
<!-- Include: device used, operating system and version, browser and version. -->
29+
30+
### Is this bug critical to a feature ship?
31+
32+
<!-- Please include details of how this bug is affecting your work, and whether it's connected to a launch event. Include deadlines, planning, whatever helps us to prioritize this work. -->
33+
34+
### Additional context
35+
36+
<!-- Include any dependencies, and links with relevant information like: research, specs, Figma links, code prototypes, discussion threads, related issues, previous work, etc. -->

‎.github/ISSUE_TEMPLATE/04_initiative-template.md‎

Lines changed: 58 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,58 @@
1+
---
2+
name: New Initiative
3+
about: An Initiative is composed of multiple efforts typically around a unified theme or goal.
4+
title: '[Initiative] '
5+
labels: 'initiative, monolith-platform'
6+
assignees: ''
7+
8+
---
9+
10+
<!-- Note: If you include screenshots, images, and other visual media, please include alt text or, if there are several of them, a higher level written explanation of what's represented in the images. -->
11+
12+
### Problem statement
13+
14+
<!-- **Why** is it important that we work on this initiative? -->
15+
<!-- Example: "Currently, there isn't a consistent way to assure content quality in the product UI, so copy that doesn't follow GitHub's content style guides keeps being shipped." -->
16+
17+
### Project overview
18+
19+
<!-- Briefly outline the tasks which, if completed, would resolve the problem. -->
20+
<!-- Example: "Create automated pull request checks for every UI content change that ping team X when a regression or error is detected." -->
21+
22+
### Goals
23+
24+
<!-- Goals are aspirational. In contrast to problems and exit criteria, goals are not coupled to a single project. Goals often represent perpetual aims and commitments. -->
25+
<!-- Example: "Increase quality of copy and micro-copy in github.com." -->
26+
27+
### Exit criteria
28+
29+
<!-- Exit criteria are specific. When these criteria are met, the project is done, and the problem is resolved. When these criteria cannot be met, the project should be discontinued, as it cannot resolve the problem. -->
30+
<!-- Example: "New pull requests have to pass a check for common content terms." -->
31+
32+
### Team
33+
34+
<!-- Include a list of people responsible for, and working on the initiative. Consider including: design, engineering, research, PM, DRI (directly responsible individual). Use a list format. -->
35+
36+
- **E**ngineering:
37+
- **P**roduct:
38+
- **D**esign:
39+
40+
### Key milestones
41+
42+
<!-- **When** do you expect that each phase of the initiative will be completed. Use a list format:
43+
- **Date** - Deliverable A
44+
- **Date** - Deliverable B
45+
-->
46+
47+
### Tracking
48+
49+
<!-- List of relevant issues to track progress. -->
50+
51+
### Reference
52+
53+
<!-- List of relevant and important links to understand context, problem, previous work, related initiatives, etc. For example: tracking board, related issues, research, specs, Figma links, code prototypes, etc. -->
54+
55+
### Glossary
56+
57+
<!-- If there are terms that may not be familiar to some, include a list here. -->
58+

‎.github/ISSUE_TEMPLATE/05_epic-template.md‎

Lines changed: 67 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,67 @@
1+
---
2+
name: New Epic
3+
about: An Epic completes some bit of meaningful work with a clear exit criteria that can stand on its own
4+
title: "[Epic] "
5+
labels: "epic, monolith-platform"
6+
assignees: ""
7+
---
8+
9+
### Problem Statement
10+
11+
<!-- One or two human readable sentences describing the purpose of the epic, short and 🍭 -->
12+
13+
### Project overview
14+
15+
<!-- Briefly outline the scope of the work that, if completed, would resolve the problem statement. -->
16+
17+
### DRI
18+
19+
<!-- Who is the DRI? -->
20+
21+
### EPD
22+
23+
- **E**ngineering:
24+
- **P**roduct:
25+
- **D**esign:
26+
27+
### Exit Criteria
28+
29+
<!-- How will we know that we've successfully complete the scope of this epic? -->
30+
31+
### Related Issues
32+
33+
<!-- Links to all the issues required to complete this epic -->
34+
35+
### Schedule
36+
37+
<!-- A best guess estimate of the order of operations -->
38+
39+
### Deployment
40+
41+
<!-- How are we going to release this work? Are there stages to that release? -->
42+
43+
### People Plan
44+
45+
- [ ] _Proposed WIP budget. This is the committed number of WIPs that are working on this Epic._
46+
- [ ] _Maximum number of WIPs that can work simultaneously on the Epic. This will be to ensure we don't devote too many people to an Epic in an effort to speed up delivery._
47+
48+
### Risks
49+
50+
<!-- List of known risks, with mitigation plan -->
51+
52+
### Dependencies
53+
54+
<!-- List of known dependencies to complete this work -->
55+
56+
### Ship Date - GA
57+
58+
_MM/DD/YY_
59+
60+
### Supporting Documentation
61+
62+
<!-- Link to the board that is used to track the work and Slack channels used for any relevant discussion. -->
63+
<!-- Optional: links to documents, spreadsheets, issues, etc that are relevant to this Epic. -->
64+
65+
### Considerations
66+
67+
<!-- Additional factors that could be helpful to make explicit -->

‎.github/ISSUE_TEMPLATE/06_batch-template.md‎

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
---
2+
name: New Batch
3+
about: A Batch is a grouping of tasks that share a theme and are significant enough to capture meaningful progress or value, but small enough to complete relatively quickly.
4+
title: '[Batch] '
5+
labels: 'batch, monolith-platform'
6+
assignees: ''
7+
8+
---
9+
10+
### Summary
11+
<!-- Quick summary of the scope of the work to be done, with any clarifying details -->
12+
13+
### Related Issues
14+
<!-- Task list of issues that, when completed, will mean this batch is done -->

‎README.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,4 +16,5 @@ Part of [GitHub](https://github.com/github) > [Engineering](https://github.com/g
1616
| <a href="https://github.com/evaccaro"><img src="https://avatars.githubusercontent.com/evaccaro?s=128&v=4" alt="evaccaro"></a>|[@evaccaro](https://github.com/evaccaro)| Engineer | [UTC-4/5](https://time.is/New_Jersey) | she/her |
1717
| <a href="https://github.com/jakebrady5"><img src="https://avatars.githubusercontent.com/jakebrady5?s=128&v=4" alt="jakebrady5"></a>|[@jakebrady5](https://github.com/jakebrady5)| Engineer | [UTC-7](https://time.is/Arizona) | he/him |
1818
| <a href="https://github.com/mathias"><img src="https://avatars.githubusercontent.com/mathias?s=128&v=4" alt="mathias"></a>|[@mathias](https://github.com/mathias)| Engineer | [UTC-5/6](https://time.is/Wisconson) | he/him |
19+
| <a href="https://github.com/mclark"><img src="https://avatars.githubusercontent.com/mclark?s=128&v=4" alt="mclark"></a>|[@mclark](https://github.com/mclark)| Engineer | [UTC-4/5](https://time.is/ET) | he/him |
1920
| <a href="https://github.com/pudiva"><img src="https://avatars.githubusercontent.com/pudiva?s=128&v=4" alt="pudiva"></a>|[@pudiva](https://github.com/pudiva)| Engineer | [UTC+0/1](https://time.is/United_Kingdom) | she/her |

0 commit comments

Comments
 (0)