mirror of
https://github.com/fleetdm/fleet
synced 2026-05-23 08:58:41 +00:00
Editor pass - Handbook: Add rituals section to Product page (#5303)
Editor pass for: https://github.com/fleetdm/fleet/pull/5178
This commit is contained in:
parent
253baee657
commit
d25fbc08fb
1 changed files with 7 additions and 7 deletions
|
|
@ -404,17 +404,17 @@ Fleet's feature flag guidelines was borrowed from GitLab's ["When to use feature
|
|||
|
||||
We track competitors' capabilities and adjacent (or commonly integrated) products in this [Google Doc](https://docs.google.com/document/d/1Bqdui6oQthdv5XtD5l7EZVB-duNRcqVRg7NVA4lCXeI/edit) (private).
|
||||
|
||||
## Product rituals
|
||||
## Rituals
|
||||
|
||||
The following rituals are engaged in by the directly responsible individual (DRI) and at the frequency specified for the ritual.
|
||||
Directly Responsible Individuals (DRI) engage in the ritual(s) below at the frequency specified.
|
||||
|
||||
| Ritual | Frequency | Description | DRI |
|
||||
|:-----------------------------|:-----------------------------|:----------------------------------------------------|-------------------|
|
||||
| 🎙 Product huddle | Daily | "In progress" issues are discussed and any issues "ready for review" are placed on the list for the product design review call. On Mondays, issues are broken down into a week's work and added into "ready." Issues are moved out of "delivered" every Friday. | Noah Talerman |
|
||||
| 🗣 Product office hours | Weekly (Tuesdays) | Decision is made regarding which customer and community feature requests can be committed to in the next six weeks. Issues are created for any requests that don't already have one. | Noah Talerman |
|
||||
| 🎨 UI/UX huddle | Weekly (Wednesdays) | "In progress" issues are discussed and any issues "ready for review" are placed on the list for the product design review call. Separate time from 🎙 Product huddle so Mike Thomas can make it. | Noah Talerman |
|
||||
| ✨ Product design review | Weekly (Thursdays) | Product team discusses "ready for review" items and the decision is made on whether the UI changes are ready for engineering specification, and later, implementation. | Noah Talerman |
|
||||
| 👀 Product review | Every three weeks | Features and improvements in the upcoming release are presented. Bugs, fixes and changes that should be made prior to release are discussed. | Noah Talerman |
|
||||
| 🎙 Product huddle | Daily | We discuss "In progress" issues and place any issues that are "ready for review" on the list for the product design review call. On Mondays, issues are broken down into a week's work and added into "ready." We move issues out of "delivered" every Friday. | Noah Talerman |
|
||||
| 🗣 Product office hours | Weekly (Tuesdays) | We make decision regarding which customer and community feature requests can be committed to in the next six weeks. We create issues for any requests that don't already have one. | Noah Talerman |
|
||||
| 🎨 UI/UX huddle | Weekly (Wednesdays) | We discuss "In progress" issues and place any issues that are "ready for review" on the list for the product design review call. We hold separate time for 🎙 Product huddle so Mike Thomas can make it. | Noah Talerman |
|
||||
| ✨ Product design review | Weekly (Thursdays) | The Product team discusses "ready for review" items and makes the decision on whether the UI changes are ready for engineering specification and later implementation. | Noah Talerman |
|
||||
| 👀 Product review | Every three weeks | Fleeties present features and improvements in the upcoming release. A discussion is held about bugs, fixes and changes to be made prior to release. | Noah Talerman |
|
||||
|
||||
|
||||
## Slack channels
|
||||
|
|
|
|||
Loading…
Reference in a new issue