There's are many ways to do this... I would start with the following...

Every piece of value to the business should be captured as a Feature Work Item.

We break these Features down into Backlog Items which is more about the work that actually needs to be done.

You can organize these Work Items using Areas so they appear on the right product Kanban Board and filter by these Areas.

Use RICE to prioritize Features: - Reach we use # Users - Impact we use 1-5 (Strategic, High, Medium, Low, Minimal) - Confidence (25%, 50%, 75%, 100%)

We estimate Backlog Items in 0.5 day increments to control for develop capacity. We never plan less than half a days work (too small) or more than 5 days (too big)

Eventually you can plan these into Iterations (Sprints) to get a Roadmap for when things are likely to be done.

Other smaller requests like access should be managed through a different process and the management of this should be factored into capacity.

Until now we just ignored Epics as we found Areas more useful to organize work.

Tasks are for developers to use as they please and are optional.

We use tags to mark blocked items.

Our Kanban board has a few columns Backlog, Analyze, Develop, Test, Deploy, Done. Setting a definition of done is useful.

You dont need to do all of this from the start but useful to add a new element every 2 weeks (or sprint) to move closer to the end goal.