Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-05-23 08:58:41 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 111

Update product handbook (#3650)

Browse source 
- Add links to product boards (GitHub projects)
- Update links in README
This commit is contained in:
Noah Talerman 2022-01-12 09:52:39 -05:00 committed by GitHub
parent 312bd840a2
commit e4fd9c3da5
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 18 additions and 11 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
handbook/README.md
View file

@ -28,14 +28,18 @@ The Fleet handbook is the central guide for how we run the company. As part of o
### Product
[Feature flags](./product.md#feature-flags)
[Fleet docs](./product.md#fleet-docs)
[Product design process](./product.md#product-design-process)
[Product quality](./product.md#product-quality)
[Fleet docs](./product.md#fleet-docs)
[UI design](./product.md#ui-design)
[Release](./product.md#release)
[Feature flags](./product.md#feature-flags)
### Growth
[Promoting blog posts on social media](./growth.md#promoting-blog-posts-on-social-media)

19
handbook/product.md
View file

@ -1,5 +1,9 @@
# Product
🛸 Product team (weekly) board: https://github.com/orgs/fleetdm/projects/17
🧱📡 Fleet core roadmap board: https://github.com/orgs/fleetdm/projects/8
## Product design process
The product team is responsible for product design tasks. These include drafting
@ -8,15 +12,14 @@ these changes to the engineering team.
### Drafting
* Move an issue that is assigned to you from the "Ready" column of the ["Product team" GitHub
project](https://github.com/orgs/fleetdm/projects/17) to the "In progress" column.
* Move an issue that is assigned to you from the "Ready" column of the [🛸 Product team (weekly) board](https://github.com/orgs/fleetdm/projects/17) to the "In progress" column.
* Create a page in the [Fleet EE (scratchpad, dev-ready) Figma file](https://www.figma.com/file/hdALBDsrti77QuDNSzLdkx/%F0%9F%9A%A7-Fleet-EE-(dev-ready%2C-scratchpad)?node-id=3923%3A208793) and combine your issue's number and
* Create a page in the [Fleet EE (scratchpad, dev-ready) Figma file](https://www.figma.com/file/hdALBDsrti77QuDNSzLdkx/%F0%9F%9A%A7-Fleet-EE-dev-ready%2C-scratchpad?node-id=3923%3A208793) and combine your issue's number and
title to name the Figma page.
* Draft changes to the Fleet product that solve the problem specified in the issue. Constantly place
yourself in the shoes of a user while drafting changes. Place these drafts in the corresponding
Figma page in Fleet EE (scratchpad, dev-ready)
yourself in the shoes of a user while drafting changes. Place these drafts in the appropriate
Figma page in Fleet EE (scratchpad, dev-ready).
* While drafting, reach out to sales, customer success, and marketing for a new perspective.
@ -35,9 +38,9 @@ these changes to the engineering team.
a link to the correct page in the Fleet EE (scratchpad) Figma. This page is where the design
specifications live.
* Add the ":product" and ":architect" labels to the issue and remove all other labels. This will add the issue to the product
board on ZenHub. In the ZenHub board, move the issue into the "Architect" column in the product
board so an architect on the engineering team knows that this issue is ready for engineering specification and later,
* Add the ":product" and ":architect" labels to the issue and remove all other labels. This will add the issue to the [🛸 Product
board on ZenHub](https://app.zenhub.com/workspaces/--product-6192dd66ea2562000faea25c/board?repos=309820286). In the ZenHub board, move the issue into the "Architect" column in the product
board. This way, an architect on the engineering team knows that the issue is ready for engineering specification and later,
engineering estimation.
#### Priority drafting