Your Features board is where you organize and prioritize features. You can also use it to plan what will get built when, and monitor each feature's progress toward delivery.
For each core use case, you may want to arrange features in a different way. We'll discuss each of these options below.
Organize new feature ideas by hierarchy
Often when we first capture feature ideas, we arrange them by hierarchy.
Doing so allows us to see features arranged in a neat outline. Features are grouped beneath folders, called "components". Components can represent whatever you'd like, but we've found it best to use them to represent the user needs we're looking to address.
If you'd ever like to conceal components containing features that you aren't responsible for, you can use the Product filter. The filter works even when features aren't arranged by hierarchy.
Prioritize feature ideas by arranging as a sorted list
When you're ready to begin surfacing interesting ideas to work on, arrange features as a sorted list.
You'll see the same exact features, but they'll no longer be grouped by components (folders). They'll be displayed as a flat list that can be sorted or filtered in order to allow promising ideas to rise to the top.
For example, you could add a User impact score to your board to sort features by their score. You could even apply a filter to this column to show only those features that had been requested with critical importance sometime in the past 30 days.
This could help us realize that many of our most popular recent requests relate to certain types of integrations – ideas we might then investigate further.
You can also sort and filter features by a number of other column types, including the Prioritization score, which allows you to surface features that support your strategy.
Plan what to build when (and monitor progress) by release
If your team plans around set releases it will be helpful to arrange features by release.
By adding an effort column, you could see the total amount of effort/complexity that would currently be required to ship the release. If the effort exceeds your team's velocity, drag and drop features between releases to adjust your plans accordingly.
In order to decide which features to prioritize within a release, it might be helpful to show additional prioritization data, like User impact score, Prioritization score, or Drivers.
Note: Releases can be named however you'd like (e.g. sequentially: R18, R19, R20; or by dates: September release, October release, November release; or by broader buckets: Short term, Long term, etc.) Select a release's name to customize it in the details pane.
To mark a release complete, click on the Release Flag to change it's status. By default, the completed releases will now be removed from your view. Filter by only completed releases with the Status filter.
Plan what to build when (and monitor progress) by status
If your team follows Kanban, or continuous delivery, you may not plan what groups of features you'll be releasing together in advance.
Instead, you'll want to track features as they progress from stage to stage, from idea all the way through delivery.
Note: Even if you use set releases, arranging by status can still be valuable. For example, since prioritization can be such a complex decision, it's helpful to break it down into multiple smaller steps. You might arrange by Status while deciding which features to promote from New idea status to Candidate status. This could mean you'll invest more time and resources researching this feature idea before either advancing it to the next phase in prioritization, adding it straight to a release, or else deciding you won't build it for now.
Use saved views
It can take some time to arrange your boards in just the right way to accommodate each of several key use cases. Save time by capturing these arrangements as Saved views.
Saved views capture not just how features are arranged, but also which columns are showing, and how features are filtered/sorted.