Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


As a product manager, how often do you check JIRA board daily?

Mariam Matiashvili
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Nov 15, 2023

What triggers you to check it: a follow-up email, Slack messages, the general roadmap, or a deadline? What do you primarily observe to get a response to your question? In my experience, I do this almost daily. It has become almost the main source of truth for me. We use Epics as projects. What has been your experience with this?

1 answer

1 accepted

0 votes
Answer accepted
Bill Sheboy
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.
Nov 15, 2023

Hi @Mariam Matiashvili -- Welcome to the Atlassian Community!

IMHO, this depends on the team and product owner's (PO) working methods...and the different scales at which you are looking for information.  As a PO, please consider what do you want to know, why that information, how would you want to see it / use it, and when do you need to know it?

For example...

  • When a team uses mob programming, there is only one item in progress, and the product owner is actively working with the team at all times.  There are no "triggers" for when to check-in: everyone knows because they were "present", physically or remotely.
  • When teams use pairing / or small group development, the daily standup (or scrum) may be sufficient for syncs and the Jira board, reports, and dashboards could supply larger contexts.  And certainly if the team is blocked, they will ping others including the PO for help.
  • And then we have lone-wolf, silo-based methods.  These are the ones where progress may be unclear as a single person is less likely to update the Jira board as they work...perhaps only doing so immediately before (or during) a daily standup...if the team uses one.
  • And so on...

Some of these can be supplemented using Jira Product Discovery, roadmaps / timelines, dashboards, and the Jira reports.  Again, please consider your and the team methods to consider what is helping and where things can be improved...and then discuss that with the team to define experiments to improve.

Kind regard,

Suggest an answer

Log in or Sign up to answer