Hierarchy

David Dsouza

Hi

I am working as Product manager for data modeling.

We have too many entities to ingest into data lake.

Each entities would go under data processes such as data discovery, data analysis and so on.

 

I am creating each process as Epic and entity ingestion would be user story under that epic.

 

But leadership is confused with this model in jira. they are only concerned about closing the epic(still coming from waterfall mentality but claim themselves scrum masters).

so I defended that initiatives can go longer and initiatives are tied to vision for data lake.

What other ways we can validate if this approach is right?

 

Vero Rivas

Hi @David Dsouza 

    I have used that hierarchy several times and it has worked very well for me, I think your drawback is the approach that people are giving to the qualification

    Instead of worrying about closing the epic, your focus should be on closing everything that is inside that epic, because once everything is closed it will close almost automatically, what's more, you can program an automatism that everything that is inside it, it goes to closed state the epic closes automatically, with which your people would not even have to worry about this

     I think your biggest drawback is a mentality problem rather than a tool problem, keep in mind that JIRA is very flexible and can be configured in the way you need, but the flow must be effective and as efficient as possible for the team and the organization

Cheers