From 83c5a7d8862c6d0fd4b4f8ca1070f401bcc4dd6a Mon Sep 17 00:00:00 2001 From: Mike McNeil Date: Thu, 1 Feb 2024 03:09:18 -0600 Subject: [PATCH] Update product-groups.md (#16527) # Checklist for submitter If some of the following don't apply, delete the relevant line. - [ ] Changes file added for user-visible changes in `changes/` or `orbit/changes/`. See [Changes files](https://fleetdm.com/docs/contributing/committing-changes#changes-files) for more information. - [ ] Documented any permissions changes (docs/Using Fleet/manage-access.md) - [ ] Input data is properly validated, `SELECT *` is avoided, SQL injection is prevented (using placeholders for values in statements) - [ ] Added support on fleet's osquery simulator `cmd/osquery-perf` for new osquery data ingestion features. - [ ] Added/updated tests - [ ] If database migrations are included, checked table schema to confirm autoupdate - For database migrations: - [ ] Checked schema for all modified table for columns that will auto-update timestamps during migration. - [ ] Confirmed that updating the timestamps is acceptable, and will not cause unwanted side effects. - [ ] Manual QA for all new/changed functionality - For Orbit and Fleet Desktop changes: - [ ] Manual QA must be performed in the three main OSs, macOS, Windows and Linux. - [ ] Auto-update manual QA, from released version of component to new version (see [tools/tuf/test](../tools/tuf/test/README.md)). --- handbook/company/product-groups.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/handbook/company/product-groups.md b/handbook/company/product-groups.md index a36544b04b..88b96d4a82 100644 --- a/handbook/company/product-groups.md +++ b/handbook/company/product-groups.md @@ -1,6 +1,14 @@ # 🛩️ Product groups +This page covers what all contributors (fleeties or not) need to know in order to contribute changes to [the core product](https://fleetdm.com/docs). + +## Background + When creating software, handoffs between teams or contributors are one of the most common sources of miscommunication and waste. Like [GitLab](https://docs.google.com/document/d/1RxqS2nR5K0vN6DbgaBw7SEgpPLi0Kr9jXNGzpORT-OY/edit#heading=h.7sfw1n9c1i2t), Fleet uses product groups to minimize handoffs and maximize iteration and efficiency in the way we build the product. +> Fleet's 🚀 Engineering and 🦢 Product Design departments also have [their own dedicated handbook pages](https://fleetdm.com/handbook/company#org-chart). +> - Use departmental pages for keeping track of specific, rote responsibilities and recurring rituals designed to be read and used only by people in those departments. +> - Use this "Product groups" page to write down philosophy, best practices, and everything else. + ## Product roadmap Fleet team members can read [Fleet's high-level product goals and planned releases for the current quarter and the next quarter](https://docs.google.com/document/d/11XEb__EJoGQJE9hXwaLrN45_5_k1NCi-zlJKH-OlKKk/edit#heading=h.33k3ii7z7ubc) (confidential Google Doc).