Hi!
We have just started using JPD to take our ideas from conception to implementation. We are a small team (12 people) with a fractional designer.
One question that keeps coming up is: where should we track our UX research & design work? Should that live:
Curious to hear how teams typically track/organize their design/ux work.
I found this related post:
Hi,
I've seen the following setups in the past, among others.
1. The UX/Design work is done in a specific step in JPD. Screenshots are pasted in the idea description, linked to Confluence or Figma. A delivery ticket can only be created when e.g. a checkbox in JPD "UX/Design completed" is checked.
2. The UX/Design work is done in the development project. UX/Design have their own steps in the workflow which are shown as columns in a separate board within the same project so that the Devs don't see the UX/Design workflow columns in their board.
3. The UX/Design is seen as part of the development process and the columns (or just tags to indicate status) for UX/Design is a part of the development board.
4. Something close to what @Jeny Stoeva wrote where UX/Design have their own project and tickets are linked between projects.
@Daniel Eden , There are no strict rules here :) It all depends on what works best for your team and how you can be most efficient. The choice is yours to make.
Keeping the designs close to their related topics could be a good thing. Your decision also depends on when you crate those designs, whether you create a design for every idea or whether you start working on them later when an idea is already prioritised for development.
How I organise for example:
In an Idea, I link an Epic (in the Idea's Delivery tab). This Epic is in another Dev project. The Epic has many issues inside and one of those is related to the Design(s) for this Epic. This Design related issue may be also coming from another Jira Project (dedicated to design tickets) but it is still under the Epic. This way I can track which designs go with which Epic.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.