We have a lot of work on new modules to do in product management.
I'm considering keeping the boards separate because of the different level of detail, different labels etc.
I'm interested in people's experience with separate boards.
Pluses, Minuses, Considerations?
Hi @Lori Gipp
I've seen teams do this in the past - it's setup like this...
In effect, "Ready" is the last column on the first board, and the first column on the second, creating an automatic link between the two.
---
There's a fundamental pro/con to this approach:
---
This is assuming it's all team-level work - if it's portfolio vs team-level work that's a different discussion, and I do think initiatives (eg. months of work) should be on a separate board, with possibly a separate workflow, to stories (eg. days of work).
Ste
We are using it to facilitate the ideation, planning, prioritization and grooming phases prior to development.
Once we move it to PDevs board, they will break down further.
Recommended Learning For You
Level up your skills with Atlassian learning
Learning Path
Get the most out of Jira
Explore the interface and basic Jira terms, then discover how to effectively manage your work.
Learning Path
Atlassian tools and practices for developers
Focus on your development work by using Jira software features and functions efficiently.
Atlassian Certified Associate
Jira Software Essentials certification
Demonstrate proficiency in utilizing essential Jira features and working efficiently with Agile frameworks like Kanban and Scrum.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.