New to JIRA Software. Best practices in Project hierarchy for non-agile software teams!

Efrain Gutierrez_uqu3do

Hello! I'm Efraín!

I was born in México, so English is not my born language!! Please be patience with my written english!!

In my systems department we still don't adopt agile methodologies but we want JIRA SW to help us manage our company customer requirements.

So, there are different teams to work for system needs from different departments (HR, purchasing, bank operations, trustees, audit areas, legal areas, etc.), so we have hundreds of systems (little, medium and large size), and constantly we need to make improves to those systems as well to create new ones.

With that background, how can we structure or hierarchize Projects? The goal is that developers know what to do, what's next, our managers know what are doing each team and our top executive level have a landscape of general status of customer requirements!!

 

I appreciate your thoughts and references to learn about this matter.

Thanks!!

Dave Rosenlund (Trundl)

Hi, @Efrain Gutierrez. Welcome to the Atlassian Community. (IMO there is no need to apologize for your English!)

This is going to be an extremely gratuitous (self-serving) response -- sorry -- but your use case is exactly why my company built Structure for Jira. It's an Atlassian Marketplace app designed to do what you describe.

Why a Marketplace app?  Unfortunately (in your case), Jira Software is designed for Agile.  Structure (and other products like it) help teams like yours extend Jira Software to make it easier to do other things, too.

Now, in fairness, Structure is not the only product you may want to consider. 

These Atlassian Marketplace searches will reveal not only our product but others too:

https://marketplace.atlassian.com/search?hosting=cloud&product=jira&query=hierarchy

https://marketplace.atlassian.com/search?hosting=cloud&product=jira&query=cross-project

https://marketplace.atlassian.com/search?hosting=cloud&product=jira&query=portfolio 
(because what you are describing is a portfolio of projects)

Pay attention to the descriptions (of course), but also the number of installations and the also customer ratings.  They are a good filter.  But some of the newer products (fewer ratings, and fewer installs) may be good, too.  Only you can decide.

Narrow the list down to 2 or 3 you want to take a look at.

*IF* you decide to look at Structure, our support team will be only too happy to help you with any questions you may have. You can reach them at structure at almworks dot com.

Best of luck to you,

-dave [ALM Works]