[whalesalad]

> a service that aims to give enterprises plan their strategic projects and workstreams

???

Interesting software. My spidey sense tells me that your team will need at least 1 FTE just to massage whatever kind of workflow is required to get stuff in Jira to play nice with this. These tools that promise insight into what is actually happening within prod/eng teams are always really great on paper but in actuality I have never seen one work.

"Yeah so there is a dusty old EC2 instance running on so-and-so's old IAM role (who is now terminated, but we can't kill their IAM or things will break) running this .jar which tries to take our JIRA stuff from these 3 projects and merge it into a pseudo "fake" project named "KPI BOARD DO NOT EDIT" that gets sync'd with a lambda function every hour to AgileCraft via a Google sheet. If this box isn't running then the KPI reports don't get generated in metabase and the board is going to lose their shit. Make sure to check the disk with df next time you login because it fills up ocassionally."

[yuchi]

For the uninitiated in Enterprise-talk, FTE stands for Full Time Employee. flies away

[yaseenk]

FYI it’s Full Time _Equivalent_. E.g a new feature may require 1 FTE for 1 week. That doesn’t necessarily mean 1 person 1 week. It may be 2 people 2.5 days each, etc.

[Waterluvian]

Or 9 women to birth a baby in a month.

I don't like being reduced to a quantifiable amount. You end up with crappy managers who have secret multipliers for every employee to try to make their crappy estimates work.

Nothing makes your colleagues dislike you more than it accidentally slipping that your manager sees you as worth 2.5 of them.

[tomrod]

Truth. Even saving their bacon, time and again, doesn't help.

[quonn]

Not really, it‘s for high-level planning, e.g. for features that involve multiple teams and often multiple companies. Mostly helpful for large-scale organizations. Jira is used one level below that.

[whalesalad]

Reminds me of the dumpster fire that is 'Portfolio' - https://www.atlassian.com/software/jira/portfolio

[opportune]

IME there are only two kinds of Ops structures. Either you have an organized, byzantine, inflexible system with way too many developers actually working on ops full time, or you have this kind of system which is more flexible in the short term but becomes an operational nightmare as technical debt accrues and accrues. I'm not sure if there is a way to get something in the middle.

The second system is a result of Agile methodology where some dev makes the mistake of telling the PM/management "well, we could get it deployed today if we just do [terribly hacky unmaintainable thing]" and gets the ok because the project is two weeks behind and half the team is going on vacation next month. The first system is the result of the "everything must fit the spec" methodology where you have excessivley long and inflexible iteration cycles, usually because you are an older more enterprisey organization.

[chrisweekly]

Yikes! Not every place is like that, thankfully.