Features dashboard in Zeda.io enables you to collect and track the progress, details, and priorities of all your features in a single place and also allows you to ship features faster.
Let's level up your Zeda.io game! Make sure you understand the Feature hierarchy before we proceed 🚀
In this article, we'll see -
You can create a feature via Feedback Dashboard, Feature Dashboard (+ create feature/import), Documents (highlight any text and create feature), or Roadmap (Click anywhere on the timeline view or click the "+" icon on the board view).
All these Features created will be shown collectively on the dashboard enabling you to track them all in one place.
Features have fields such as title, feature ID, description, attachments, linked feedback, modules, sub-features, progress/details, and prioritization tabs.
Features can be filtered, grouped by different fields, and organized into hierarchy levels for easy management.
A feature in Zeda.io will look like this -
Understanding Feature Fields
The following table can help you understand the feature fields -
Title of the feature, shown in different views upfront
Unique identifier for the feature in your workspace
Type of feature (Epic/Story/Improvement/Task/Bug)
A detailed description of the feature
Image/file attachments to define the feature better
Feedback aligned with the feature
Linked modules like documents, designs, and Analytics
Breakdown version of features into ISBTs
Marking and viewing of feature dependencies
Sub Features and Dependent Features
Organize your features with sub-features and dependent features in Zeda.io. This provides a clear view of how your features relate to one another and fits into your roadmap. A sub-feature is closely tied to a feature and cannot exist independently. Its fields are similar to those of a feature.
When building your products, you may need to leverage microservices or features maintained by other PODs in your organization. Track these dependencies in Zeda.io's Features dashboard to ensure timely delivery and prevent blocking. Use the blocking and blocker features to manage dependencies and avoid last-minute surprises.
Prioritizing features is crucial in planning and executing a product roadmap. It involves selecting the best framework to qualify features to work on. Zeda.io provides several popular frameworks.
RICE: Use Reach, Impact, Confidence, and Effort to calculate a score for each feature and prioritize accordingly
Value-Effort: Use Value and Effort to calculate a score for each feature and prioritize accordingly
Custom: Create a custom prioritization framework that suits the strategy by defining a name and score and creating a formula using custom fields
These frameworks are available in the Prioritization section under Workspace Settings > Modules > Features > Prioritization. After selecting the framework, you can use it in the prioritization tab of a feature to get a priority score, which helps sort features and decide which ones to work on first.
Linking Modules to Features
A feature is a compiled entity that consists of feedback, data, research, discussions, designs, and documents. Zeda.io makes it easy to create features and collaborate on them by attaching all relevant information to the feature directly.
Feedback Attached: Use this option to compile all the feedback related to a feature and keep the context intact.
Module Linking: Use this option to keep all relevant documents like PRDs and research analysis notes in the modules section and attach URLs for design and analytics files.
Custom Link: Use this option to attach links to external data like customer support ticket links or dashboard links.
Tracking feature execution with kanban board
The list of features can be overwhelming to consume on the features dashboard. To focus more on the important items, we have built the board view in the dashboard, which can be accessed to change the view from List to Board.
The board view classifies all the features with different statuses in the Kanban method and provides options to help further trace the feature using Filters and Group by options.
Group by option can help to further classify the data according to the Type, Importance, Product, and Assignee.
Multi Select or Bulk Actions
Features dashboard also caters to changing feature details like status, type, importance, assignee, and product for multiple features at once. Bulk actions also work on sending features to Jira, Creating a roadmap, archiving features, or deleting them.
In case you have got a specific query to ask, you know where to find us 👉