[awaywopassd]

Unfortunately, this is a reality. I am part of a small team where we moved pretty fast.

We used to write our own stories in Jira and they were mostly one liners. They have now implemented so many required fields to fill out. Filing out one story might take 30 minutes.

And the management has implemented a mix of waterfall and agile methodology.

It is combination of worst of both worlds. We are asked to plan our next 10 or more sprints. Assign points to each story. And then we are asked to justify points to management. It is a big mess. In a week, we might spend 20+ hours on planning and planning to plan bullshit.

I fought this as much as I could. But in the end, I realized that this is losing battle. All we can do is work with them and help them justify their jobs and our jobs.

We have stories for planning stories. We have stories for reading documentation. We have stories for breaks. Oh I want to cry.

But good thing is if you work with system and make your team look super busy, you will get big bonuses and pay raises. Kind of like in real world, you can write the cleanest code but if you don't write features that customer want and brag about your product, you will not get paid for it.

[Carpetsmoker]

> I fought this as much as I could.

I think that "fighting" this in the first place is not the correct approach. It would be better to "work on improve" it.

Perhaps I'm being pedantic, but I think it's an important difference, and creates a different (more constructive) mindset.

But yeah ... I've been where you are and I feel your pain :-(

[matt_the_bass]

> We used to write our own stories in Jira and they were mostly one liners. They have now implemented so many required fields to fill out. Filing out one story might take 30 minutes.

Perhaps you should embrace this. Spending time at the story level means you spend early effort to clarify the issue and specify the (possible) solution. In other words: planning.

I know this may seem like it sucks and is not really worth it, but it is often really valuable, especially as you grow and scale. Your company has been bought by a larger one. Obviously one value of this is to use the larger company’s resources to scale faster.

Maybe some of the story requirements are extraneous, but perhaps you should work with central management to improve the jira story requirements not fight against them.