Product Mgt & Engineering Ops: Jira Product Discovery + Jira Software Premium + Advanced Roadmap
J P
Rising Star 
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Summary
I am curious about how you are integrating JPD into your overall Product & Engineering Ops stack with Jira Software AND Jira Premium.
I am SO excited about JPD! Jira Software has always felt like a solution built for developers that Product Managers had to endure. JPD get so many things right... and is just getting better and better through this beta process
Current State & Contact
- We have multiple product teams and engineering teams
- Engineering is currently using Jira Software for delivery (the Jira Software deployment was configured for and is owned / managed by Engineering)
- Our Product Team currently uses a collection of unintegrated solutions (e.g. scattered Confluence + Google Drive + other documents) with some Jira Software engagement for engineering spring and have inconsistent, non-Jira-integrated Roadmunk use
- From the top down, we are currently going through an intense process of defining and clarifying our processes and the systems / tools that support them.
The work Product Manage is full of lots of wonderfully messy middle...
The Questions / Discussions
- What system(s) are you replacing with JPD?
- What does your "hand off" from JPD to Jira Software look like?
- What are your artifact or other requirements / to transition to more structured "product planning" [that is NOT yet "Dev Ready"?
- Internally, how do you communicate the differences between the problems the JPD is solving vs. Jira Software [for Product planning that is NOT yet "Dev Ready"]?
- Who updates what... where... for which purposes? Double entry and updates between JPD & Jira Software (especially for higher level, hierarchical planning through Jira Advanced Roadmaps?)
Ok... what are all the right answers? hahaha 🤣
