The product team is newly growing, and consists of all product managers and product designers on the team. We will consider splitting into separate teams only when size necessitates it.
- Christina Forney, VP Product
- Product management
- Product design
- Technical writing
See Roles for open positions and hiring targets.
- Onboarding to the product team
- The Sourcegraph workflow describes how our product fits into the developer workflow.
- Product documents (PDs)
- RFCs (requests for comment)
Release early, release often
Each project, no matter how long-running, needs to plan to ship something in each release. The “something” depends on the project. We strongly prefer for it to be a minimal viable feature that is enabled by default. The next best thing is to ship something that is feature-flagged off by default. When possible, larger features should be merged mid-cycle to solicit feedback from the team and customers before the release is cut.
The reason for this is to avoid going for too long without customer feedback (from customers trying it) or even technical/product feedback (from performing the diligent work of polishing it to be ready to release). Lacking these critical checks means we will end up building something that doesn’t solve people’s problems or that is over-built.
When we have relaxed this in the past, the results have been bad and the overwhelming feedback from retrospectives has been to release regularly.