Hacker News new | ask | show | jobs
by ketzu 57 days ago
In a team I worked, we had full control over how we wanted to use the board. But the senior people just refused to engage with it, as anything they did on the board would make them accountable.

My lesson: Boards can be awful and useless even without managers running them! :)

I've been using a simple, standalone kanban to manage my own tasks, though.

4 comments

This is such an important lesson. To me so many things from the "agile" toolkit appear to fail in ways where people tend to blame the tools, but instead are exposing people/process problems. The intent was that organizations use the pain points to improve process and solve problems. But in my experience a lot of organizations would rather remain dysfunctional than work effectively, and so will then shift to tools that don't expose the problems.
Not just boards. I’ll argue any deliverable.

Part of what makes corp life so inefficient is that lack of unified approach.

Working with a company where many of C-suite folks operate in normal corp world: Office 365. Slides, spreadsheets, the currency of business.

Meanwhile the product team operates in JIRA and in Confluence. They communicate with each other in their respective preferred formats.

But imagine if CEO said something like: any deliverable of A,B,C types has to be Confluence. No exceptions. 3 strikes until you get a penalty.

Would that help?

Let me philosophize a bit: Stability gives you the opportunity to take the next step, diversity gives you the opportunity to choose a new direction.
I love the statement not so specific to this conversation but in general. Completely agree.
Sure, all the people who kind jobs that don't force them to use Atlassian products would just resign.
That’s one thing I hate at my company . Many teams run Jira with backlogs, burndowns and whatever. In theory all the info is right there. But the big guys can’t be bothered to use Jira so somebody has to spend hours and hours prepping PowerPoint slides with the info that’s in Jira.
I just require PR's to have tickets attached or it fails CI and otherwise use LLM's to write analytics to track what people are doing these days. Asking devs to hold themselves accountable is an exercise in futility in my experience. In a world where you can do that, why even bother with tickets outside of planning the work done? Might as well just transcribe your standup and turn it into tickets that way too.