15% off membership for Easter! Learn more. Close

What would be your roadmap if you were the PM of JIRA?

Asked at Atlassian
1.7k views
Asked at
eye 1.7k views eye 1.7k views
Answers (2)
crownAccess expert answers by becoming a member

You'll get access to over 3,000 product manager interview questions and answers

badge Platinum PM

 

Current state of product:

Jira is a software development tool for agile teams to plan, track and release world-class software.

Jira can be used for the following purposes:

·         Requirements and test case management

·         In Agile Methodology

·         Project Management

·         Software Development

·         Product Management (product owner used it only for creating and tracking user stories and solving issues for developers)

·         Task Management

·         Bug Tracking

 Clarifying Questions:

Should I focus on web or mobile? your choice

Do you want to focus on a specific market or global strategy? Your choice

Do you have specific goal in mind? Your choice

Do you have a specific user I should focus on? Your choice

Is there a preference for expanding existing functionality vs. rolling out new features? your choice  

Product vision

 Increasing userbase in product management

Short-term Goal

1.       Develop various tools for product management phases such as product design, feedback capturing, workflow planning, road mapping etc.

2.       Improve engagement among stakeholders in various phases of product management

3.       Increase in customer acquisition rate for product manager using Jira.

Select metrics

# Of product management tools used

# Of people using Product management tool

# Of Corporate impacted with product management tool

Associated user group

Product manager using Jira for Remote Product management.

Prioritized feature set

1.       Create template to understand the pain points on high level with different stakeholders.

2.       Plan for Customer journey/Design thinking workshop to identify the problem statement.

3.       Negotiate with stakeholders on prioritized items and timeline.

4.       Collaborate with UX designer to come up with mock ups for the solution defined.

5.       Discuss and demo the developed product to customers/stakeholders and gather feedback from them.

6.       Prepare plan for promoting the developed product such as Marketing Campaign, Demos etc.

7.        Analysing the product data

Develop a product roadmap with time lime

Feature Set

Business Impact

Implementation Effort

Template for Pain points/user need

High

Medium

Design thinking for Problem Statement

High

Low

Prioritizing features /items

High

Low

Mock ups for the solution

Medium

Low

Customer Feedback feature on Product

High

Medium

Promotion/Marketing of Developed product

High

Medium

Product analytics feature

High

High

 

Timeline for implementing the features based on Implementation Effort

Timeline: 1-3 months

·         Design Thinking for problem statement

·         Prioritizing features/items

·         Mock ups for the solution

Timeline: 3-6 months

·         Template for pain points/user need

·         Customer Feedback feature on product

·         Promotion/Marketing of Developed product

Timeline: 6-9 months

·         Product analytics feature

 

 

Access expert answers by becoming a member
1 like   |  
1 Feedback

Hey Pavan, I think you did pretty well here in structuring the problem. One area that I would look to improve is the roadmap itself. Generally product roadmaps do not describe the steps required to complete an individual project (like you have listed here) but rather a number of different key outcomes/projects. In your brainstorming section, I would focus more on different solutions to help move your key metrics. What you have listed is more like a project timeline, not a product roadmap. I hope this is helpful!

0
Get unlimited access for $12/month
Get access to 2,346 pm interview questions and answers to give yourself a strong edge against other candidates that are interviewing for the same position
Get access to over 238 hours of video material containing an interview prep course, recorded mock interviews by expert PMs, group practice sessions, and QAs with expert PMs
Boost your confidence in PM interviews by attending peer to peer mock interview practices, group practices, and QA sessions with expert PMs

Clarify Jira:We will focus on Jira SaaS and on desktop version for this discussion.

Overveiw of Jira: Project planning, tracking, and reporting software specifically built of software development projects. Project mgmt tool for shipping software. 

Personas: Scrum masters, project managers. Developers. Product managers user stories. Leadership - track progress. 

Goals for jira: # of paying customers, spend/paying customer. 

Inputs goals: # of free customers, Conversion ratio from free to paid.

#of active projects/ paying customer, # of active users/customer. 

# of successful projects/ customer. 

 

Mission: Help unleash the potential for every team. Help unleash the potential for Sofwtare dev teams. 

 

Industry trends and competition here:

a/ Software is eating the world. Software projects are only going to increase.

b/ COmpetition -- there is a lot of competition -- asana. However, Jira is market leader. 

 

Customer segments -- where all is software created. 

1/ ISVs -- SMBs to large companies

2/ Medium - Large companies -- IT projects 

3/ IT Services firms. - SMBs to large companies 

 

Personas and customer journeys:

a/ Project manager/Scrum master

Easily create a project -- put down a skeletal project plan. Assign tasks, monitor progress. 

 

b/ Developers who code

View the high prioriuty tasks, see teh rqurieements, ask for clarifications, design the software, start coding - iterate with product owner, commit code, unit test, push code to deployment through regression testing.  

 

c/ Product owners who create user stories

Wite the user stories directly in the tool. 

See activity on the user stories -- developer have questions. Prmptped for actions. 

See progress of project

 

d/ Leadership who wants to see reports. 

See project progress. 

 

How to prirotize which persona to focus on?

 

# of people involved

# of touch points they have with the software - do they use it daily, multiple times in a day. 

 

Developers -- volume is high.

Dialy usage -- low. Probably once or twice in a week. 

 

Project managers -- 1 project manager to 10 devs. Volume is medium.

Daily usage - high. Jira is their primary tool for their job.

 

Product owners - VOlume is medium.

Daily usage - medium to low: Create stories, track progress, clarify questions.  

 

WE will focus on Project manager persona: How to make Jira the best tool for project managers. 

Easily create a project -- put down a skeletal project plan. Assign tasks, monitor progress. 

How to make project mgmt easy?

 

Pain point: They need to understand how agile works. Can we make this simple?


 

Customer journey

Pain points. How important is this?

Solution

How software project planning works?

 

Creating a project plan

Dont know about software project planning. Make it easy to learn

 

High. If we can make ti simple, then project mgrs from other domains can become scrum masters. 

 

People with out strong project mgmt background, then get ramped up easily

Templates for project planning. Agile, Waterfall, Explain dependencies 

Show a template - click on it - lays down skeletal plan. 

 

a/ How many developers

b/ How many projects

c/ How many product owners 

 

Create a template based on this. 

 

Include in-context videos on hwo to think about software projects. 

Assigning tasks to owners - developers, product owners

  

Figure out dependencies 

High. Since if dependencies are not clear, then project will slip. 

Project plan template - should list dependencies at every step. For e.g, if user story is created, then developer needs to review and sign off. 

 

User stories -- estimations need to finish by xx date. 

Track project progress

Burn down charts. 

Project status - are on track, red and so on. 

 

Risk management 

High

Highlight based on previous projects where risks are likely to happen. 

a/ Developers who have propensity to slip. 

b/ Estimates and capacity are very tight. 

c/ key dependencies are not yet cleared. 

Reporting and Status

Creating an executive report

THis is a lot fo work. Have to create powerpoints. Docs. 

Make it automatic. Create doc, ppt. 

With reasons. 


 

Will focus on creating the project template and simplified onboarding experience for project managers. 

Success metrics: 

 

Time to create a project plan should reduce.

# of projects getting created should increase 

 

# of project manager users should increase

 
Access expert answers by becoming a member
2 likes   |  
Get unlimited access for $12/month
Get access to 2,346 pm interview questions and answers to give yourself a strong edge against other candidates that are interviewing for the same position
Get access to over 238 hours of video material containing an interview prep course, recorded mock interviews by expert PMs, group practice sessions, and QAs with expert PMs
Boost your confidence in PM interviews by attending peer to peer mock interview practices, group practices, and QA sessions with expert PMs
Get unlimited access for $12/month
Get access to 2,346 pm interview questions and answers to give yourself a strong edge against other candidates that are interviewing for the same position
Get access to over 238 hours of video material containing an interview prep course, recorded mock interviews by expert PMs, group practice sessions, and QAs with expert PMs
Boost your confidence in PM interviews by attending peer to peer mock interview practices, group practices, and QA sessions with expert PMs