I know a _lot_ about JIRA.
I know a _lot_ about JIRA. I worked at Atlassian for almost four years, in engineering management and product management roles. (Left in 2011, if you care). JIRA is a total nightmare to configure sensibly, and the UX is complex enough that there's a real learning curve to get your team using it effectively. The kicker is, that once the combination of JIRA, JIRA Agile, and Confluence are setup correctly, and your team is using them well, there's nothing else like it. It's spectacular for: - tying specs to issues to code - surfacing status to non-devs sensibly - allowing interested folk to keep abreast of projects without having to attend meetings - getting rid of huge messy email conversations - figuring out "why the hell did we do that?!" I'd recommend JIRA + JIRA Agile + Confluence to any team with more than 10 members, with the caveat that you need to find/hire an expert to configure the product and help your team use it effectively. ninja edit: JIRA will allow you to faithfully model+enforce your fucked-up development process. So, badly-configured JIRA can be one of the least fun experiences of your working life.
Posted by daveoflynn on Feb 3, 2015, 4:51 PM
Tags
Related issues
- C++ is the "just here to deliver" language.
- He is not weirdly political, he has just more normal views, I know that is something hard to grasp for some tech bro.
- Of course you don't have a right to murder anyone.
- Unify Control and Container nodes, allow children to pick the behavior
- I was talking about this the other day with someone - broadly I agree with this, they're absolutely fantastic for getting a prototype so ...
- In theory you could express most things as a flowchart but the complexity of doing that quickly escalates.
Raise real-world problems, find people facing the same issue, and discuss solutions.8,000 issues0 comments
ux (EdTech)
C++ is the "just here to deliver" language.
He is not weirdly political, he has just more normal views, I know that is something hard to grasp for some tech bro.
Of course you don't have a right to murder anyone.
Unify Control and Container nodes, allow children to pick the behavior
I was talking about this the other day with someone - broadly I agree with this, they're absolutely fantastic for getting a prototype so ...
In theory you could express most things as a flowchart but the complexity of doing that quickly escalates.
It's not really hard to onboard new engineers with Scala, Clojure or even Ruby backgrounds.
Very understanding (or even no) partners is probably a large percentage of it!
I know a _lot_ about JIRA.
I know a _lot_ about JIRA. I worked at Atlassian for almost four years, in engineering management and product management roles. (Left in 2011, if you care). JIRA is a total nightmare to configure sensibly, and the UX is complex enough that there's a real learning curve to get your team using it effectively. The kicker is, that once the combination of JIRA, JIRA Agile, and Confluence are setup correctly, and your team is using them well, there's nothing else like it. It's spectacular for: - tying specs to issues to code - surfacing status to non-devs sensibly - allowing interested folk to keep abreast of projects without having to attend meetings - getting rid of huge messy email conversations - figuring out "why the hell did we do that?!" I'd recommend JIRA + JIRA Agile + Confluence to any team with more than 10 members, with the caveat that you need to find/hire an expert to configure the product and help your team use it effectively. ninja edit: JIRA will allow you to faithfully model+enforce your fucked-up development process. So, badly-configured JIRA can be one of the least fun experiences of your working life.
Comments (0)
No comments yet. Start the discussion.