A Scrum board organizes work around a backlog and sprints. A Kanban board supports a continuing flow of work, often with a backlog for work not ready to enter the active columns. Choose the board type from the team's process rather than the job title of the person requesting it.
A board is a view over work. Creating another board doesn't create another copy of each issue. The filter defines the eligible population, and column mappings decide which statuses appear. The local model supports Scrum and Kanban definitions with working membership, sprint views and limits. Hosted card colors, swimlanes and layout customization remain checked planning decisions here. They can improve readability, but they don't repair the wrong population or status mapping.
Choose a board type from the team’s delivery process.