Hacker News Reader

Comment by jordanbeiber | Hacker News Reader

Again: describe a set of work principles explicitly that all agree on - it's a human communication and collaboration issue you were faced with.

A tool is not responsible for this breakdown. Lack of clarity around ownership and responsibilities is, by the look of it.

IM humble O.

View on HN

I'm willing to entertain that the teams using Jira are just making worse choices about the work principles they agree on than our teams using gitlab issues, and that it is coincidental and unrelated to the tool. Surely you agree though, that in general a tool can adversely affect user behavior? The agile manifesto said to value tools and process es less than individuals and interactions, not to discount their impact altogether. Developing software in a single paradigm language when your domain is better suited to a different paradigm is a horrific blunder I have witnessed twice in my career. Developing giant systems using vba macros in excel is a common mistake you hear about. I can however believe that the teams that selected jira over gitlab might have done so because they already bad this use pattern in mind, and not because the tool encouraged it.

I’ve worked in fantastic settings, truly following the agile principles, using jira as a tracker and board.

I’ve been places with many different tools and people.

Guess what, it’s ALWAYS about the people.

If a team is following principles derived from or resembling the manifesto, the tool will be shaped accordingly.

Jira, as an example, sure can be shaped, and I’ve done it myself several times - remove cruft, keep it simple, change if needed.

Reply on news.ycombinator.com