Any tips on creating a board to show hierarchy of requirements?

[Caitlin Bell]

Basically I need a way to show high level requirements and what is involved to complete requirement.

For example:

1. Quality Assurance Workflow (high level)
   1. workflow configuration
   2. user administration
   3. notifications
2. Dashboard Views (high level)
   1. end user dashboard
   2. admin dashboard

Should I create Kanban board for each high level requirement or is that not a good practice?

Open to ideas. Thanks!

[nina_schmidt]

HI @Caitlin Bell 

you have some options:

1) a Kanban Board for every requirement --> you need a marker for those Requirements e.g. component or epic

2) all on one Board --> requirement as Epic, tasks and sub-task for grouping and prioritizing 

We use both setups.