Have you linked product management and product development boards ? Any guidance ?

[Lori Gipp]

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?

[Ste Wright]

Hi @Lori Gipp 

What is your definition of product management vs product development? Is it the difference between new features and improvements?

And what are you using the boards for? Is it for a team? To plan sprints?

Ste

[Ste Wright]

Hi @Lori Gipp 

I've seen teams do this in the past - it's setup like this...

• Kanban Board: Creation > Ready (including Sprint Ready) - the board is used for initial scoping, story writing, bug testing, etc.
• Scrum/Kanban Board: Ready > Done. Utilises a backlog, where items aren't added until they're "Ready"

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 can help limit the backlog to items you'll actually "do" - i.e they're scoped, accepted, and ready to be picked up, however...
• For some teams, everything should be in the backlog and prioritised, so it isn't missed, nor are they spending time scoping unnecessarily when an item might not even get built

---

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

[Lori Gipp]

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.