Track your feature backlog, product execution, and priorities in a single place and collaborate with everyone to ship products.
In this article
- Hierarchy in Zeda.io
- Products & product groups
- Organizing your features in Zeda.io
- Prioritizing features
- Collaborating on features
- Linking modules to features
- Tracking feature execution with kanban board
- Creating custom views of the feature dashboard
- Feature Settings for workspace
- Access control
- Multi-select or Bulk actions
- Archiving feature(s)
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.
Hierarchy in Zeda.io
There are four essential elements in the Zeda.io hierarchy to know before setting up your feature backlog in Zeda.io
You can imagine product groups as PODs/product teams/product groups in your organization that manage multiple products or product components and usually is made up of multiple product managers.
You can imagine a product in Zeda.io as an entity that exists as an independent offering for your end-users, something that has an independent context, and a vision, and is usually managed by one or more than one product manager.
A feature in Zeda.io is a component or a part of a product that can be defined, tracked, shipped, and monitored by a product manager and also something which can independently drive value for your end-users.
A sub-feature in Zeda.io is a broken-down version of your feature which will enable product managers to plan and define features better from an execution point of view.
Products & product groups
A product group in Zeda.io will enable your product PODs, groups, or teams to organize their features, execution boards, and roadmaps more seamlessly and only look at these items while going through the backlog or monitoring their product progress.
For more information on products and product groups and how to leverage the product space for these, you can refer to these articles.
A feature is not tightly bound to a product and can exist independently. A feature in Zeda.io will look like this -
The following table lists some of the fields of a feature -
|Title||This is the title of the feature and is usually shown in different views upfront.|
|Feature_id||This is a unique identifier for every feature in your workspace and will be along the lines of ZEDA-1001 where ZEDA is a placeholder for a unique identifier for your workspace.|
|Description||This is a detailed description of the feature and can contain a more verbose feature spec/detailing.|
|Attachments||If you have any image/file attachments to define your feature better, you can add those as attachments.|
|Linked feedback||When you align feedback to features, this is visible under linked feedback on a feature card.|
|Linked modules||When you link modules like documents, designs, personas etc. to features they are visible under the linked modules section.|
|Sub-features||You can break down your features into sub-features which are visible under the sub-features section of the features card.|
|Dependencies||At times, some features might block the closure of other features or they might be blocked for closure by other features. Such dependencies can be marked and viewed within the dependencies section on the feature details card.|
|Progress tab||The progress tab on a features card lists the different fields and labels which will enable you to get an understanding of the progress of the feature in the feature lifecycle.|
|Details tab||The details tab on a features card lists the different fields which will help you know more about a feature. The custom fields defined on a feature are also listed here.|
|Customers||The total number of customers tagged on all of the linked feedback of a feature is visible here to give you an understanding of the demand for a feature.|
|Total MRR||This represents the total MRR (monthly recurring revenue) that is generated from all the tagged customers at a feature level to give you an estimate of the value that can be driven by shipping a feature.|
|Type||This represents the type of a feature like Epic/Story/Bug|
|Prioritization tab||This tab will list the prioritization framework properties like RICE and Value-effort.|
Sub-features in Zeda.io are available within the sub-feature section of a feature as shown below-
A sub-feature is tightly bound to a feature and cannot exist independently. The fields of a sub-feature are similar to the fields of a feature.
Organizing your features in Zeda.io
You can organize your features in Zeda.io by using the filters, Group by and Hierarchy levels to manage and consume the features list in a structured way that suits the requirement.
Filters help in decluttering and searching the list of features present.
Group by helps to classify the features in the list as per the required field like type, importance, assignee and product.
Hierarchy levels have two options:
1. All Levels: on Feature + Sub-feature level
2. Only Features: on Features level
At times when you are building your own products, there are cases when you leverage another microservice or features maintained by other PODs within your organization or vice versa.
In such cases, it becomes really important to call out such dependencies and track them as well to ensure timely delivery of your features and also to ensure that you are not blocking others without communication.
The dependencies in the Zeda.io features dashboard, enable you to just do this - manage blocking and blocker features to ensure there are no last-minute surprises.
With Zeda.io, you can navigate to feature details > dependent features and start marking features as either blocking type or blocked by type.
Planning always involves picking the best framework to qualify features to work on. These frameworks can be really dependable on the strategy. Some popular frameworks in feature planning are RICE (Reach Impact Confidence Effort), Value-Effort etc.
In your workspace also you can have access to these frameworks directly and also create a Custom Framework that suits the strategy.
You can access it from Settings > More Settings > Modules > Features > Prioritization
- RICE - Provide numeric values to the Reach Impact Confidence and Effort of a feature to obtain a score derived using R*I*C/E
- Value-Effort - Provide numeric values to the Value and Effort to obtain a score against a feature derived using Value/Effort
- + Custom - Click on New Custom Prioritization to set up a custom framework. Then you have to define a name for the framework and the score. After that, you can create a custom formula using custom fields (of list type with enums or of number type). Enums can be defined across a custom field (of list type) while creating a new field in the custom field option.
The selected framework will be applied across all the features present in the workspace.
After selecting the framework, this prioritization method is available in the prioritization tab of a feature where the fields will be mentioned and they can be entered to get the priority score. The features can be sorted according to the score from the dashboard.
Collaborating on features
Collaboration is about the ability to keep the information flow constant across all stakeholders for a feature and keep a track of the feature development to support any kind of requirement needed.
In the workspace, it is solved by providing separate tabs for tracking and for information.
For tracking, the Progress tab in feature details:
- Duration to define the feature planned start and end dates for release
- Assign the feature from your workspace members to have a clear owner for the feature
- Status to understand different stages the feature is in like planned, design, dev, UAT etc
- Align to Product will help to link this feature with a product in the product space. It is not necessary to align a feature to a product. Features can exist independently
- Align to OKR provides information as to what Goal or Initiative is the feature contributing to which can help in better alignment for planning
For information across stakeholders, the Details tab in feature details:
- Customer shows the customer name and the fields associated with the customer like Total MRR. But this is visible only when the feature is mapped with customer-tagged feedback.
- Tags help to mark different entities like features, feedback or documents with groups across the platform
- Type is the kind of feature (classification between features) created like bug, feature, story, task, or epic.
- Importance denotes the importance of features in terms of low, medium and high which helps when the features are being planned for the roadmap
- Custom Fields created for the features will be available and can be edited directly here
Linking modules to features
A feature is a compiled entity that consists of feedback received, data, research, discussions, designs, and documents.
In the workspace for features, there are easy options to create features and collaborate on them easily by attaching all relevant information to the feature directly instead of maintaining separate sheets or pages with links.
- Feedback Attached compiles all the feedback which was aligned to this feature, which helps to keep the feedback context intact for everyone and attaches more information for the feature created
- Module Linking helps to keep all relevant documents like PRDs and research analysis notes together in the modules section. You can attach URLs for design files and analytics files.
- Custom Link is helpful in case to attach links to external data like customer support ticket links or dashboard links etc.
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 further help 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.
Creating custom views of the feature dashboard
Features dashboard can be consumed in specific lists like a list of features from a few people, a list of all the high-importance features or list of features from a specific product, etc.
Features dashboard can have a different view by the use of filters and Group By to create a specific list. This list can be saved as a view from the filters bar. This list can be saved as a Private (only the view creator can access it) or Workspace (everyone in the team can access it).
And this view is accessible from the dropdown in the title All Features. The view can be edited or deleted also using the 3-dot option near the name of the list.
Import-Send-Snyc your features (Jira)
For keeping seamless collaboration with the tech team, the workspace is integrated with Jira. Integration with Jira can be leveraged in 3 ways:
- Import features via Jira - All the features in a project in Jira can be imported to the workspace after authentication with an API key, connecting with the selected project in Jira and mapping the type, importance and status. This will populate all the features present in the project in Jira into the Zeda workspace immediately. More features from different projects in Jira can be added to the workspace similarly one by one.
- Send features to Jira - Any new feature created in the zeda.io workspace can be sent to the Jira by the action of Send to Jira (with mapping on status, type and importance). This action is available in the bulk actions. Check the gif attached for a clear explanation.
- Hourly auto sync - Workspace runs an hourly two-way sync with Jira to update any field value for the features which are mapped between Jira and Zeda.io. It also imports any feature created in Jira from the mapped project to the workspace.
Apart from just the integration with Jira, there are various places where this information is leveraged in the workspace. Some of them are:
- Once the Jira ticket is mapped with a feature in Zeda, Jira Id will be available in the features list view across the feature.
- Zeda.io fetches the epic and fix version along with the manual import and hourly sync, which can be used for fields for any feature on Zeda.io as well. These fields are available in the Details tab of a feature.
- Tags defined in Jira are also imported and synced with the workspace feature created
Feature Settings for workspace
Settings > All Settings > Modules > Features > _____
Workspace is highly customizable for the features where the teams can set the platform according to their framework and process. We have two types of fields present:
- Default fields (which are pre-defined on the workspace)
- Status - Each workspace has 3 defined states (Not Started, Work In Progress, Done). Each state comes with a default status (To do <> Not Started, In progress <> Work In Progress, Completed <> Done). New status can be added in each state as per the product development process. Every feature state will have to have at least one status and these states help in the feature analytics and automation.
- Type - It consists of default values (Epic, Story, Feature, Task, Improvement, Bug) but the team can add more types of type as per the team's process.
- Importance - It consists of default values (Low, Medium, High) but the team can add more types of importance as per the team's process.
- Custom Fields (which can be created for more details on features)
- These fields can be of type Text, Number or List.
- Number type can be used for custom prioritization also.
- For the list type, enums can be defined for each value and are used for custom prioritization.
Admin and creators have the same access. Collaborators have limited access. Refer to the table below for detailed functions and access to features
|Add a comment||Yes||Yes|
|Link to product||Yes||No|
|Be assigned to features||Yes||No|
Add zeda module links
|Hide from roadmap||Yes||No|
|Use filter / group by / sorting / save views||Yes||Yes|
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, archiving features or deleting them.
Archiving is essential to clear up the workspace but also maintain the data of features. It can be used to store the Completed features in the workspace. This can be done on a single feature or multiple features using a bulk action.