-
Notifications
You must be signed in to change notification settings - Fork 13
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #835 from GeorgianaElena/dor
Create a "Engineering work definition of ready" section
Showing
2 changed files
with
55 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,54 @@ | ||
(engineering:definition-of-ready)= | ||
# Engineering work definition of ready | ||
|
||
The engineering team gets many different kinds of work from many different sources. An important question for solving these work items is: _**is something ready to be worked on?**_ | ||
|
||
Answering this question, requires at least the following information: | ||
|
||
- [What kind of work item something is](dor:categorization) | ||
- [Does it have all the information needed for a member of the engineering team to start working on?](dor:ready) | ||
- If it does not, what exactly is the information needed? And who is responsible for providing it? | ||
- Once all the information is provided, is there explicit documentation on what actually needs to be done? | ||
|
||
(dor:categorization)= | ||
## Work categorization | ||
|
||
The following non-exhaustive initial list of the different kinds of tasks that the engineering team performs during a sprint cycle. | ||
|
||
1. [](ready:feature-enablement) | ||
2. [](ready:routine-maintenance) | ||
3. [](ready:new-hub) | ||
4. [](ready:config-change) | ||
5. [](ready:fault-fixing) | ||
6. [](ready:community-review) | ||
7. [](ready:incident-Response) | ||
8. [](ready:routing) | ||
|
||
(dor:ready)= | ||
## Definition of ready | ||
|
||
The following describes what is the information needed for a member of the engineering team to start working on a specific type of work item. | ||
|
||
(ready:feature-enablement)= | ||
### Feature enablement | ||
|
||
(ready:routine-maintenance)= | ||
### Routine maintenance | ||
|
||
(ready:new-hub)= | ||
### New hub | ||
|
||
(ready:config-change)= | ||
### Config change | ||
|
||
(ready:fault-fixing)= | ||
### Fault fixing | ||
|
||
(ready:community-review)= | ||
### Community config change review | ||
|
||
(ready:incident-response)= | ||
### Incident response | ||
|
||
(ready:routing)= | ||
### Routing |
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