How Jira Program Managers use Jira Product Discovery for design allocation and capacity planning
Hi Community! This week as part of Jira Product Discovery June, we’ll be sharing examples of how different Atlassians use Jira Product Discovery. This is part 2 of 4. (Here's part 1 if you missed it!)
✨ Challenge ✨
We want to hear from you too! Leave a comment with any questions, tips, or how you use Jira Product Discovery within your team and get the Capacity Commander badge.
*This spotlight uses Jira Product Discovery Premium - learn more here.
Meet the Atlassians
-
Name: Rich Roberts & @Isobel Norton
-
Role: Program Managers
-
Where you’re from: Sydney, Australia
-
Fun Facts: Richard is a big fan of Dr. Manhattan (superhero) & Isobel did the highest bungee jump in the southern hemisphere (!!)
-
Advice for a Program Manager: Treat your internal stakeholders like customers - start with a PoC of your Jira Product Discovery projects and views then work alongside stakeholders to iterate on it
What team are you on at Atlassian and what is your team responsible for?
Rich Roberts - I am the Program Manager of Jira Horizon team, which is focused on unlocking use-case depth for new business teams in Jira.
@Isobel Norton - I do end-to-end Program Management, and am currently managing the Jira Issue terminology update and the Jira Work Management customer migration into Jira as part of the broader program to merge them into one Jira.
What challenges was the Jira team facing that prompted adopting Jira Product Discovery?
We have been working with the Jira design org to solve their capacity management challenges. In the Jira team, rather than being embedded in Product teams, designers align to a Pillar and are assigned to projects. Designers needed a way to see all the work that needed design support, how complex the work is, and when a designer would be required. This enables design managers to plan out upcoming work for their team, and makes sure that the right designer is assigned to the most applicable work.
What are the primary ways in which the Jira design team uses Jira Product Discovery?
The primary use case for using Jira Product Discovery is to have a source of truth for tracking and monitoring the product roadmap. We have recently been expanding this use case to other capabilities, like using Jira Product Discovery to track Designer allocation and capacity.
How has adopting Jira Product Discovery helped support the Jira design team’s way of working?
Jira Product Discovery has been such an easy to use tool!
- the bar to entry and management of our roadmap is very easy
- we've reduced the cost in admin to support and maintain roadmap documentation
- easy to use UI also makes it quick for our teams to routinely review their roadmap and make updates quickly in session on the fly, again reducing the cost to support and maintain our roadmap
Any pro tips or advice to share as a Jira Product Discovery power user?
If you're on Premium, use the Roadmaps feature + global fields to connect different Jira Product Discovery projects and see a cross-project view. Using the same global fields in each project allows an overarching cross-project roadmap to be created (and less admin for you).
Iterate! Start with a PoC to share with stakeholders, create a mock-up of how you see your project looking and share it with the key stakeholders who will be using it. This way, you can incorporate stakeholder feedback and get it right first time, and your key stakeholders have been taken along on the journey with and will be more likely to engage with the tooling.
Demo
In case you missed them, here the other articles in this series:
Was this helpful?
Thanks!
Kesha Thill
8 comments