Guide
Getting started
Fibery is a dynamic no-code platform designed to offer unmatched flexibility. The Product Team template is a comprehensive guide, offering inspiration and support to help you craft a custom solution that meets your unique needs.
The Product Team template assists you in:
💬 Capturing customer feedback from various sources
🔗 Linking insights to the product backlog
🔝 Prioritizing backlog items
🗺️ Bridging the gap between the product roadmap and delivery
📢 Communicating the roadmap to stakeholders and the wider audience.
Feedback Collection and Integration
Feedback comes from multiple sources: user research calls, support tickets, notes from the sales team, emails, surveys, and more.
The Fibery integration ecosystem helps you to collect all the feedback in one place: Feedback feed.
Feedback is sorted by date by default and shows a small summary (AI can create that).
Once feedback is processed, you can mark it as Processed, remove it from the feed, and later locate it in the All Feedback view.
To connect more sources, follow the integration guides:
Specific Integration | Generic Integration |
| or |
User Research
This template serves User research in several ways.
Persona Management
Think of this as your secret weapon in the product development world. It's like having a crystal ball that lets you peek into your users' minds. You get to know them, understand what makes them tick, and then use that knowledge to make decisions that hit the bullseye. And the best part? You end up creating products that your users can't get enough of.
You can whip up different personas, like creating characters for a novel, and link them up with your real-life customers. It's like playing matchmaker but in a business sense.
FAQ
If you want to connect multiple contacts to a persona, use one-to-many Relations. More on that in the guide about Relations.
The Product Hierarchy
A product hierarchy can be understood as a structured representation of the various elements that make up a software product. This hierarchy can be broken down into the following levels:
Product is the highest hierarchy level and represents the software solution being developed. It encompasses all the components, features, and subfeatures of the software. This is only needed when you have more than one product in your portfolio.
Component is a distinct part of the product that performs a specific function. Components typically comprise multiple features and can operate independently of other components. For example, in project management software, components could include task management, team collaboration, and reporting.
Feature is a specific functionality within a component that provides value to the user. For example, within the task management component of a project management software, features could include task creation, task assignment, and task tracking.
Subfeature is a specific aspect of a feature that provides additional functionality or detail. For example, subfeatures could include setting due dates, adding task descriptions, and attaching files within the task creation feature.
This hierarchy helps organize the development process, making planning, tracking, and managing the work easier. It also aids in communicating the structure and functionality of the software to stakeholders, including developers, project managers, and end-users.
Similar to most features in Fibery, the Product Hierarchy is adaptable. You can modify the names, the number of levels, and many other things to fit your needs.
Opportunities are placeholders for potential areas of growth or improvement in product management. They allow ideas and observations to be documented and revisited later for refinement.
Once thoroughly evaluated, Opportunities can be linked to specific features for development, ensuring valuable insights are not lost. They provide a flexible and efficient way to manage ideas and feedback, bridging the gap between idea generation and feature definition.
Connect Feedback to Backlog items
You can use Entity mentions and bi-directional links highlight specific details from the Feedback and link them to a particular aspect of the product, such as a feature or component. This simplifies future prioritization by aligning feedback with the relevant part of your product.
If you're uncertain where to connect this feedback within the product structure, you can create an 'Opportunity.' These can subsequently be linked to existing Features or serve as inspiration for new ones.
All the Feedback for a Feature (or any item in the Product hierarchy) can be found on the Feature View.
Prioritization
Prioritizing the backlog is complex, with no universal solution that perfectly suits every product or development team.
The number of drivers used for product prioritization can vary widely and is often tailored to the specific needs and context of the product and team. Choosing a framework and set of drivers that align with your product strategy and customer needs is crucial.
In Fibery development, flexibility is paramount. That's why we offer various options in the Product Team template. While we recommend using one of these options, they can be freely modified, removed, or replaced with new ones to suit your specific needs.
Priority by Strategic Drivers
Product feature Drivers are inherited from OKRs (Objectives and Key Results) in product development by aligning the objectives and key results with the product features that will deliver the desired outcomes.
There is no fixed number, and it can be customized based on the product, team, and company's needs.
In the Product Team template, we set two Drivers. The Drivers can be set in the Priority by Drivers view
The Drivers' settings and effort determine the Value/Effort score. The default formula is this:
[Driver - Adaption].Value + ([Driver - Engagement].Value * 20) / Effort
You can change the formula to fit your needs.
AutoEffort is a nice function that helps to sum up Subfeature efforts to its Feature.
Using the AutoEffort option, the efforts of the SubFeatures belonging to the Feature are added together. This can be turned off, even per Feature, and is a good example of how small things can simplify things.
RICE prioritization
RICE prioritization is a framework used to evaluate and prioritize project ideas based on four factors: Reach, Impact, Confidence, and Effort.
RICE stands for:
Reach refers to the number of people each project will affect within a given period. For example, "how many customers will this project impact over a quarter?"
Impact measures the effect of the project on an individual user. The impact is usually scored on a scale, for instance, 12 for massive impact, 8 for high impact, 4 for medium impact, 2 for low impact, and 1 for minimal impact
Confidence helps control projects where the team has data to support one aspect of the score but relies more on intuition for another. Confidence is typically scored as a percentage, with 100% being high confidence, 80% medium confidence, and 50% low confidence
Effort is the estimated work required to complete the project, typically measured in "person-months."
MoSCoW prioritization
The MoSCoW method is a prioritization technique used in management, business analysis, project management, and software development to reach a common understanding with stakeholders on the importance they place on the delivery of each requirement.
The board view is highly beneficial as it facilitates swift prioritization through the ranking of cards.
The categories are typically understood as:
Must have are critical requirements that the project must meet for success.
Should have are important but not critical requirements. The project would still be a success even if some of these requirements were unmet.
Could have are desirable requirements that are not necessary for project success. They are typically included if time and resources permit.
Won't have are requirements that stakeholders have agreed will not be implemented in a given release of the product
Feedback-driven prioritization
Feedback-driven prioritization is used in product management and Agile methodologies to prioritize tasks, features, or improvements based on feedback from end-users or stakeholders.
In this table
Reference count refers to the total number of direct links from feedback to the Feature.
Opportunity count represents the total number of links to the Opportunity associated with the Feature.
Feedback count is the combined total of the Reference Count and the Opportunity Count.
Feedback-driven prioritization is not a one-time event but a continuous process. It requires constant iteration and improvement based on the results and feedback received. It's also crucial to monitor and evaluate the effectiveness and efficiency of the feedback methods and tools and make necessary adjustments or changes.
Feature Tracking
Feature Tracking is your go-to method for keeping an eye on how your features are progressing. It gives you a bird's-eye view of where each feature is at in its journey. Tracking fields come in handy for keeping tabs on the usual tasks that apply to a bunch of your features, like Product specs, Design, Development, Launch status, or any other stuff you need to follow up on. The assigned people in charge of these tasks set the statuses themselves based on the info they get from their teams.
You can customize the status values that can be assigned to each task and the colors associated with them.
Special task fields can be linked to a delivery planning tool such as Jira, Trello, GitHub, or GitLab issues. This integration can automatically keep you updated with information from remote systems.
Please check the following integration option:
Also, consider using Fibery for both product management and software delivery. The tool is flexible and feature-rich, allowing you to keep all the information and run all the processes in one tool. You won't need to switch contexts and will have instant access to reports, requests, etc.
Roadmap
After collecting essential insights, associating them with particular features, and ranking them using one or multiple methods, the subsequent step is to define the development sequence and set a timeline. This provides a clear vision of the future product deliverables. A roadmap serves as a vital tool for stakeholders and the broader audience.
Product roadmaps are diverse in their forms to serve various audiences. In this template, we've incorporated several innovative ideas for your inspiration. Please feel empowered to modify, reinvent, or eliminate elements per your requirements.
Kanban
A Kanban roadmap helps product managers leverage the Kanban methodology in strategic planning. The Kanban technique involves grouping initiatives into clearly marked buckets by the state of the features. The name and the number of buckets represent your process.
Timeline
This bar chart displays a detailed schedule of features related to a feature. It helps show cross-functional teams what work they must complete in what order before they can move on to the next stage of a project.
Kanban Style Organizing in Releases
This visualization organizing elements in releases involve grouping features to be released together. This approach allows for more flexible planning options, faster output, clearer focus, and transparency throughout the development cycle.
Kanban Style Organizing by Quarters
Using the financial quarter structure can effectively establish and track goals. It interests stakeholders and allows for timely adjustments and decision-making. This approach helps organizations stay focused and results-oriented.
Write stunning PRDs
Fibery provides a user-friendly interface to organize and document your product requirements easily. With the Rich Text editor, you can create PRDs that effectively communicate your vision and streamline development.
All information is in one place. You can find all the linked feedback and components on the Feature view. You can even write the Public Announcement, which will be handy when preparing the Release Notes for the Releases.
Releases
Users must be informed of what has happened when the completed Features are sorted into Releases and released. This is exactly what the Release Notes do.
Putting this together is not always an easy task. But it would be best to collect them since you can create a Public Announcement for Features as soon as the PRD is finalized.
With Fibery's Automation feature, they can be put together at the touch of a button.
Public Roadmap and Release Notes
Transparency helps to create a bridge between the product team and the customers we serve.
The Public Roadmap can be shared as an interactive platform with colleagues and customers. It serves as a tool for validating ideas and maintaining open communication combined with Discourse integration:
It allows for collecting feedback on ideas still under consideration. This helps to understand which ideas benefit our users most and why.
It provides a platform to share upcoming plans and recent launches, ensuring everyone is updated.
This information can be channeled to the Feedback source as well.
Release notes enhance the overall product experience by offering a valuable chance to connect with customers and the wider market. When executed effectively, they can foster engagement and boost customer loyalty. Release notes serve as a means to convey messages and communicate with customers and the broader market. Well-written release notes have the potential to enhance customer loyalty and promote engagement.
Once you have compiled all the views within the Public Roadmap space, it will be shared with the world. Please use the Publish Space to Web guide to set it up.