3.3 KiB
Product groups
Background
When creating software, handoffs between teams or contributors are one of the most common sources of miscommunication and waste. Like GitLab, Fleet uses product groups to minimize handoffs and maximize iteration and efficiency in the way we build the product.
Product groups were formerly known as "development groups" at Fleet. The term "product group" is more common across the industry, so in January 2023, Fleet switched to using it.
What are product groups?
Fleet organizes product development efforts into separate, cross-functional product groups that include members from Design, Engineering, Quality, and Product. These product groups are organized by business goal, and designed to operate in parallel.
Security, performance, stability, scalability, database migrations, release compatibility, usage documentation (such as REST API and configuration reference), contributor experience, and support escalation are the responsibility of every product group.
At Fleet, anyone can contribute, even across product groups.
Current product groups
| Product group | Goal (value for customers and/or community) |
|---|---|
| MDM | Reach maturity in the "MDM" product category. |
| Customer experience (CX) | Make customers happier and more successful. |
MDM group
The goal of the MDM group is to reach product maturity in the "MDM" product category, across macOS and Windows.
| Responsibility | Human(s) |
|---|---|
| Designer | Noah Talerman |
| Quality assurance | Reed Haynes |
| Product manager | Noah Talerman |
| Engineering manager | Luke Heath |
| Software engineers (developers) | Gabe Hernandez, Jacob Shandling, Martin Angers, Roberto Dip, Sarah Gillespie |
Customer experience group
The goal of the customer experience group is to make customers happier and more successful. This includes simpler deployments, more successful customer onboarding, features that drive more win-win meetings with Fleet's sales team (such as initiatives like out-of-the-box CIS compliance for customers), and "whole product solutions", including professional services, design partnerships, and training.
| Responsibility | Human(s) |
|---|---|
| Designer | Mike Thomas |
| Quality assurance | Reed Haynes |
| Product manager | Zay Hanlon |
| Engineering manager | Sharon Katz |
| Software engineers (developers) | Artemis Tosini, Eric Shaw, Juan Fernandez, Lucas Rodriguez, Marcos Oviedo, Rachel Perkins, Robert Fairburn, Zach Winnerman |