You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi, How to create value vs complexity matrix in jira? Thanks
When you think of a "value vs complexity matrix" what does that look like to you, and how would your teams use that with Jira?
And, how are you representing value and complexity: with custom fields, etc.?
For example, are you thinking of a M rows x N columns table, showing the count of items for each value and complexity pairing? Perhaps with the ability to drill down and see each issue. If so, you could do that with your custom fields and the Two-Dimensional Filter Gadget on a Jira Dashboard. That would be a read-only view, based on the fields. Please look here to learn more about that gadget: https://support.atlassian.com/jira-cloud-administration/docs/use-dashboard-gadgets/
If you are looking for something more dynamic, where items could be drag-and-dropped to another "value" or "complexity", there is a matrix view in Jira Product Discovery which supports that for any created Ideas. Please look here to learn about that tool: https://www.atlassian.com/software/jira/product-discovery
Kind regard,
Bill
Hi Billy,
Many thanks for your response. I am thinking of the visual representation with 2 axis: x (horizontal) about complexity, y (vertical about value) and storie appearing in 1 of the 4 cadrants to classify them as large feature, quick-wins, etc...
Kindest
Aurelie
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What I described earlier offers a couple ways of doing that; perhaps try one.
And...You now mention sizing, which is different from complexity and value: for example, there can be small effort, high complexity requests and large effort, simple ones.
If you also need this third-dimension of sizing, neither of the approaches I described would help. Instead please investigate doing this with an Atlassian Marketplace addon or outside of Jira in another reporting tool.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.