Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Jira Initiative/s baseline example

Hey folks!  So, I'm interested in any article, opinion, or recommendation of what a properly defined Jira Initiative looks like.  Obviously one that ties the Upper Roadmap together with lower level Epics, but what are is the best construct with respect to granularity across: tie in to upper OKRs, how timebound, how might these tie in to both an infantile, or mature Product Release Strategy?

1 answer

1 accepted

0 votes
Answer accepted
Dave Atlassian Team Apr 25, 2021

Hi @Michael Gallagher,

I'm not sure that there is a single answer here and it also depends on whether you're using "Initiative" to mean "the hierarchy level above Epic" or how best to define a conceptual initiative (regardless of the level).

Our team typically uses initiatives to gather epics that are conceptually linked, but then we're using epic more like a feature (due to the current nomenclature restrictions in Jira).

I'm not sure if this helps or not (probably not!) but I thought a response might help get the discussion going.



Thanks Dave!  You're the first to return an answer.  In reference to 'Initiative', we're in a Hierarchy of: Subtask -> Story ->Epic -> Initiative (at the Neighborhood level) -> Roadmap (at the Town level).  Am interested in the Jira construct of an Initiative, and how we might define an Initiative (description) with respect to being descript enough to aggregate Epics but not so granular that we have dozens of them across say a 1/4 (Q1, Q2 etcc)  Really trying to get a baseline understanding of the best way to develop Jira Initiatives that are value-add in reporting up through an organization, and how best they can be constructed to dovetail over reporting-durations and congruent with a Product Methodology.  i.e. R1.0 - R1.1 - R1.2 -> R2.0 - R2.1 etc..

Like Dave likes this

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Marketplace Apps & Integrations

Staying organized with Jira: best practices for a better project management

Project managers know this problem: A “mountain of work” lays in front of you, and you don’t know how and where to tackle them. Different to-dos lie ahead, but just one task after the other can be ha...

151 views 2 1
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you