Re:How Atlassian Built a $10B Growth Engine
by gregmac on Tuesday January 02, 2018 @02:09PM
(#16054450)
You can also build flexible, low-overhead workflows using JIRA. The key is to keep managers out of the admin section, make sure the dev team is in full control, and tend towards saying "no" whenever anyone asks for changes to the workflow.
[ Parent
| on HN ]
Re:How Atlassian Built a $10B Growth Engine
by ravitation on Tuesday January 02, 2018 @02:25PM
(#16054622)
I think anecdotally that may work, but I'm not convinced that dev teams are that much better than "managers" are at creating or managing process (nor are they often very interested in doing it)...
But I think this does get to the core issue with JIRA. Whether you "like" JIRA or not is more a reflection of your organization than it is a reflection of JIRA as a tool.
Re:How Atlassian Built a $10B Growth Engine
by sdoering on Tuesday January 02, 2018 @03:04PM
(#16055055)
Just anecdotally I can confirm that different development and product teams work good with JIRA and Confluence in conjunction.
The agency I work at uses these tools together with ovur clients, as well as internally on different levels.
We have an internal project were we are just using tasks, subtasks with 3 states in a team of 9 in three to four locations. And we have a client, being served with about 100 people in different teams working on multiple projects, spanning multiple locations. Here we use the same tool. In one case with just a basic setup. One a 'little bit' more elaborate and customized...
Re:How Atlassian Built a $10B Growth Engine
by blattimwind on Tuesday January 02, 2018 @02:22PM
(#16054592)
> The key is to keep managers out of the admin section
Works as a general rule, too.