#Problem My team consists of software developers and UX designers. Their workflow is different--UX has different steps than a pure development task has. What's the best way to manage this on one Kanban board?

bonus: what's the best way to manage this in Jira's Kanban?

Details

With our project, we have UX folks conducting stakeholder interviews, building wireframes, and getting approval. Their steps are something like:

1. Interview stakeholder
2. Design wireframes
3. Developer feedback
4. Stakeholder Approval
5. UI Design (colors, etc)

We also have developers with their own flow, like:

1. Ready for Work
2. In Progress
3. Code Review
4. QA
5. Product Owner Review
6. Deploy

Some of the stories the designers work on feed directly into developer stories, so it would make sense to have a board combining all team members' steps. However, sometimes there's design work that won't directly lead to a dev story--basically, design stories will skip steps in the flow.

Thanks for your help! 🙇‍♂️

Problem

My team consists of software developers and UX designers. Their workflow is different--UX has different steps than a pure development task has. What's the best way to manage this on one Kanban board?

bonus: what's the best way to manage this in Jira's Kanban?

Details

With our project, we have UX folks conducting stakeholder interviews, building wireframes, and getting approval. Their steps are something like:

1. Interview stakeholder
2. Design wireframes
3. Developer feedback
4. Stakeholder Approval
5. UI Design (colors, etc)

We also have developers with their own flow, like:

1. Ready for Work
2. In Progress
3. Code Review
4. QA
5. Product Owner Review
6. Deploy

Some of the stories the designers work on feed directly into developer stories, so it would make sense to have a board combining all team members' steps. However, sometimes there's design work that won't directly lead to a dev story--basically, design stories will skip steps in the flow.

Thanks for your help! 🙇‍♂️

#Problem My team consists of software developers and UX designers. Their workflow is different--UX has different steps than a pure development task has. What's the best way to manage this on one Kanban board?

bonus: what's the best way to manage this in Jira's Kanban?

Details

With our project, we have UX folks conducting stakeholder interviews, building wireframes, and getting approval. They're steps are something like:

1. Interview stakeholder
2. Design wireframes
3. Developer feedback
4. Stakeholder Approval
5. UI Design (colors, etc)

We also have developers with their own flow, like:

1. Ready for Work
2. In Progress
3. Code Review
4. QA
5. Product Owner Review
6. Deploy

Some of the stories the designers work on feed directly into developer stories, so it would make sense to have a board combining all team members' steps. However, sometimes there's design work that won't directly lead to a dev story--basically, design stories will skip steps in the flow.

Thanks for your help! 🙇‍♂️

#Problem My team consists of software developers and UX designers. Their workflow is different--UX has different steps than a pure development task has. What's the best way to manage this on one Kanban board?

bonus: what's the best way to manage this in Jira's Kanban?

Details

With our project, we have UX folks conducting stakeholder interviews, building wireframes, and getting approval. Their steps are something like:

1. Interview stakeholder
2. Design wireframes
3. Developer feedback
4. Stakeholder Approval
5. UI Design (colors, etc)

We also have developers with their own flow, like:

1. Ready for Work
2. In Progress
3. Code Review
4. QA
5. Product Owner Review
6. Deploy

Some of the stories the designers work on feed directly into developer stories, so it would make sense to have a board combining all team members' steps. However, sometimes there's design work that won't directly lead to a dev story--basically, design stories will skip steps in the flow.

Thanks for your help! 🙇‍♂️