Thanks Igor!

I guess there is no right or wrong on this, it really depends on how the team is setup and working. But from my point of view, there are a couple of things to consider:

If the team is working in SCRUM in delivery, I think it’s difficult to map the discovery tasks on the same board. It’s the nature of discovery work that you cannot really plan everything ahead and know how long some things will take - hence, these tasks can't really be put into a sprint framework. If the team is working in Kanban in delivery though, I have seen teams who have a combined discovery and delivery Kanban board in JIRA. Here the difficulty is that the different stages/columns of the delivery flow (if you have special columns like e.g. code review, QA etc.) might not always map well to the discovery flow which might make it a bit confusing.

If you have 2 different boards, the discovery work isn't as visible for everyone who spends more time on the delivery side (e.g. engineers). If you still want to make sure that everyone has access to both boards, make sure you at least use the same tool - e.g. both boards in JIRA or both boards in Trello etc.

In no corona times and when not working with a distributed team, a physical discovery board can also be a great idea. Everyone can easily keep an overview as the board is quite visible also to those who spend most of their time on delivery work.

Hope that's helpful:)