Product development structure

Fibery Process schema Screenshot 2022-03-09 at 10.48.27 AM.png

Use CaseA complete user scenario in a product. For example, Create context-rich features specification, or Create and maintain public product changelog. Use Case can include many Features from different Product Areas. Use Cases help to focus on user needs and not just add top features mechanically. Overall, it is better to release Use Cases than Features.Examples:

Create context-rich specifications Create context-rich specifications / PRD

Prioritize insights and features Prioritize insights and features

Screenshot 2024-10-18 at 11.45.19 AM.png

Product AreaSignificant area of a product. For example, Search, Whiteboard. May contain other Product Areas. For example, Integration → GitHub Sync.Product Area is a hub that collects everything related to an area of a product: Features, Bugs, Insights, general feedback.Product Area may not exist in a product yet, but it should be created to collect feedback. For example, Fibery has no mobile App, but we have Mobile Product Area to link relevant feedback.Every PA has PA Owner. PA Owner is responsible for this area and do the following: Create Features in this area, handle feedback, review Insights linked to his area, prioritize work inside his area.Examples:

Board View Board View

Permissions Permissions

Screenshot 2024-10-18 at 11.46.21 AM.png

FeatureFeature is a solution to a problem and a functional requirement for a Product Area. Features can be nested. NOTE: We used to have User Stories, but replaced them with nested Features for simplicity. It seems User Stories add nothing new, but why then have one more term? Examples:

Table View Block in Rich Text Table View Block in Pages

My Space My Space

Screenshot 2024-10-18 at 11.47.01 AM.png

Dev. TaskTechnical task that does not add new functionality to the system: refactoring, technical preparations for the feature implementation, writing tests, etc. Can be linked to some Feature.Examples:

Narrow account registry scope checking logic Narrow account registry scope checking logic

Screenshot 2024-10-18 at 11.47.38 AM.png

BugAn issue in a product. Can be linked to a Feature or to a Product Area. Examples:

Bad feedback for inline code Bad feedback for inline code

Screenshot 2024-10-18 at 11.48.10 AM.png

InsightUsually insight is a problem in the product. For example: People don't understand the difference between data and views. It can also be an observation or an opportunity.Examples:

Users are worried about end-to-end encryption Users are worried about end-to-end encryption

Dependency management is missing Dependency management is missing

Screenshot 2024-10-18 at 11.48.36 AM.png