Update communications.md (#14169)

This commit is contained in:
Sampfluger88 2023-09-27 21:32:46 -05:00 committed by GitHub
parent 952c8ec077
commit 2ffd8ec91d
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
3 changed files with 7 additions and 7 deletions

View file

@ -106,7 +106,7 @@ When the final signature is added to an envelope in DocuSign, it is marked as co
## Responsibilities
### Manage g-ceo intake
### Process new requests from the #g-ceo kanban board
The Apprentice to the CEO is the DRI for the [#g-ceo kanban board](https://app.zenhub.com/workspaces/g-ceo-645b0eab68a4d40c0795ff61/board?sprints=none) and responsible for [managing all intake](https://fleetdm.com/handbook/company/communications#manage-intake) including issues and PRs.

View file

@ -19,11 +19,11 @@
moreInfoUrl: "https://fleetdm.com/handbook/company/ceo#process-the-ceos-email"
dri: "sampfluger88"
-
task: "Manage g-ceo intake"
task: "Process all /"New requests/" on the #g-ceo kanban board"
startedOn: "2023-07-29"
frequency: "Daily ⏰"
description: "Process the CEO's inbox"
moreInfoUrl: "https://fleetdm.com/handbook/company/communications#manage-intake"
description: "Process and prioritize all new issues and PRs"
moreInfoUrl: "https://fleetdm.com/handbook/company/ceo#process-new-requests-from-the-g-ceo-kanban-board"
dri: "sampfluger88"
-
task: "Process the CEO's calendar"

View file

@ -84,14 +84,14 @@ maintaining an expressive labeling system. For example, instead of a label calle
| `:` | Verb | `:dev`, `:research`, `:design`
| `~` | Adjective | `~blocked`, `~frontend`, `~backend`
### Manage intake
Team members [process their department's kanban boards](https://fleetdm.com/handbook/company/why-this-way#why-lean-software-development) daily, prioritizing all new intake within 24hrs from when it was submitted.
### Process new requests
Team members [process their department's kanban boards](https://fleetdm.com/handbook/company/why-this-way#why-lean-software-development) daily, prioritizing all new requests including issues and PRs within one business day.
To process intake team members will:
- Inspect each item in the "📨 New requests" column and understand the next steps needed to complete the task.
- Indicate to the requestor when they can expect the task to be completed by placing each item in the appropriate column (e.g. Not yet, Planned, In progress) and estimate if necessary.
- If the goal/user story is unclear, assign the issue to the requestor and at-mention them in an issue comment asking to clarify the intended action.
- If the task is to be backlogged (e.g. Not yet), place the issue in the "Not yet" column and at-mention the requestor in an issue comment. Explain why the task is unable to be prioritized and provide a tentative ETA on when the task will be completed.
- If the task is to be backlogged (i.e. "Not yet"), place the issue in the "Not yet" column and at-mention the requestor in an issue comment. Explain why the task is unable to be prioritized and provide a tentative ETA on when the task will be completed.
### Making a pull request