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
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hey everyone! Just looking for some thoughts around how to use JPD with my current organization.
Short story: We aren't 100% embracing Product Driven org so we end up with hundreds or "ideas" or "requests" submitted to our Product Division. While we are working on changing this mentality, it will not be an easy change. Requests submitted could be from enterprise clients and they could be large initiatives but ideas submitted can also just be changing or adding a button here or there.
From a previous thread on this site, the recommendation is to use a Jira Service Management desk to allow those to still be submitted. I agree with this.
I am trying to figure out the best way to use JSM/JPD/Software to be as transparent as we need to.
Here are my thoughts and places where I have some questions, please feel free to chime or offer other suggestions:
Any other idea or thoughts, please feel free to offer any and all opinions! Thanks!
Thanks @Cam ... preaching to the choir on the change the whole org mentality. We are working on it for sure. It is getting everyone else in a historically client/sales driven org to make the change that is the struggle.
I appreciate the response and validating what seemed the most sensical to me.
So having gone through this same progression this is what we are settling on. We don't have a huge team but do have dedicated people in charge of delivery and discovery but to make things easy for our CS/BD staff we are still operating their INITIAL interactions with the delivery board (i.e. JIRA Software).
However, we have created a new issue type 'Suggestion' (and limited the others they can create). So effectively they only raise bugs & suggestions. Our weekly triage process will convert a Suggestion to a discovery idea if it's needed OR for the really small things, we hand to the PO to convert it to a User Story that outlines the small change as per SCRUM/Agile.
We will see how this goes, it's not perfect but a start.
@Colin Goudie Thank you! Yes, this seems like the best for now. I like the triage meeting concept as well.