4 ms·
Atlassian research highlights major disconnect between developers and leaders
- abbadadda 2y agoThis friction is often invisible. This cost is not measurable. Hard work needs to go into measuring developer productivity, helping business people understand, and then make that number go up. The second part is perhaps the hardest as if you don’t do that you might not be employed long enough to do number 3.
- kayodelycaon 2y agoOne my team’s “goals” (which we did not pick) is to increase our velocity. My coworkers and I didn’t really discuss it but we’ve all started adding extra points to every ticket.
- pacifika 2y agoRecently things are on the right track but not too long ago it was the jira experience that was the single biggest benefactor from upgrading my fibre connection beyond my wifi speeds.
- difosfor 2y agoHas anything about Jira improved lately? I hadn't noticed. Still frustratingly slow, overly complex and unoptimized for developer experience. Heck I still can't refresh the sprint board without it changing from under me because it forgets about all the custom filters I had to select to see the things relevant to me.
- flappyeagle 2y agoThis is ironic. Do Atlassian know that they are the cause of the disconnect? No one ever got fired for buying Jira but all your engineers hate it.
- nofunsir 2y ago>No one ever got fired for buying Jira If I ever owned a company, I would make sure anyone who authorizes a single Atlassian license purchase would be fired.
- altairprime 2y agoTheir stance will be: “How can you manipulate your engineers into accepting Jira and AI without harming their productivity?” It’ll be phrased in HBR terms, but that’s the essential core of it. It’s not about how leadership can change their own beliefs and priorities. It’s about how they can modify others so they don’t have to change themselves.
- kgdiem 2y agoI think jira isn’t really the issue — it’s actually easier to use (IME) to express a body of work than notion, asana or trello. Like most things, I think it’s a people problem. Story points, velocity, burn down, etc are mostly nonsense. Tracking productivity can be largely subjective and unfair, probably better left to judgement of a decent manager. At the end of the day I think it’s systemic incompetence and lack of clear communication, from any combo of product engineering and business, that causes frustration more than creating epics, stories, subtasks and bugs.
- hedora 2y agoYeah; Jira lets you pick whatever workflow works for your company. I'd love to find a replacement that can do that. Most of the major issues I've seen with Jira come down to a disconnect between engineering and product, sales, etc, etc. Of course, there's a bunch of other stuff they should just fix. For instance, Atlassian should pick one markdown dialect, and then default all their tools to it at setup time. Also, bugs stored in their cloud offering often go unavailable for a few minutes, even with tiny bug databases. (When I say a bug goes unavailable, I mean I can't access issue XX-1234, but other pages load, often including other bugs.) Anyway, it's the least bad bug tracking tool I've encountered.
- nofunsir 2y ago
- wood_spirit 2y agoAtlassian are positioning themselves as the solution, as though leaders should invest in more atlassian-centric work tracking to improve developer experience. But my experience is that developer friction very much comes from using the atlassian stable of horrendous products. Jira? Jira align? This didn’t win out over fogbugz due to awesome developer experience and productivity!
- jameslk 2y ago> Most developers attribute their time loss to tech debt or insufficient documentation Ah the tech debt argument. Most likely it's true, but what developers really want to do is Rewrite The Whole Thing, often in something new. That's always a fun, career-advancing project. Being in the position of seeing others do this, and being the person who's wanted to do this before and has done this before, I can say it's not often a good outcome. Software development and UX are different skills and it's a rare developer that has both. This is otherwise known as Refucktoring. When the tech debt refactoring project is given to the wrong person, it's a good way to end up with even more tech debt and less willingness of leadership to try again.
- watwut 2y agoI think that is massive strawman. The push for complete rewrite from developers is super rare. Usually they want much smaller changes. When people talk about technical debt, it is usually in codebase with massive number of bugs and teams that are constantly under pressure.
- jameslk 2y agoSure, everyone's experience is subjective. A lot of the tech debt I've seen that ends up being true baggage for developer velocity is inherent to some core foundation of the codebase leading to large rewrites. Most teams I've worked in try to address the smaller tech debt while working on related features that otherwise would use the tech debt (i.e. "leave it better than you found it") but that I'm sure depends on the team and what pressures they face.
- deleted 2y ago[deleted]
- errorlog 2y agothis is like the stasi publishing a think piece on the importance of privacy
- hibernator149 2y ago"Leaders" have to stop pretending that they know better than the developers who are actually doing the work. Let the developers decide how their "Developer Experience" should look like instead of deciding it top down. Show some real humility. A good example from the article is AI. Leaders think it is the greatest thing, but two out of three developers don't see the benefit. This needs to be solved bottom up. Devs love new shiny tools that make them more productive or that make work more fun. That's why we invent a new framework or language every three days. If the two out of three developers can't find a way to make AI work for them, then their non-technical leaders surely won't help.
- nitwit005 2y ago> Atlassian, we’ve invested heavily in developer experience with the goal of putting developers at the center of the process. As a result, developer satisfaction has risen 25 percentage points over the past two years (from 49% to 74%). This is phrased as a brag, but it sounds like they belatedly realized they hadn't been investing in something key to their business.
- matrix87 2y agoIf this disconnect didn't exist, who would bother doing business with them? As a company they're essentially synonymous with shitty UX OSS alternatives could eat their lunch overnight if it weren't for "corporate hospitality" or however else they conspicuously manage to shove their dogshit down everyone's throats