|
|
|
|
|
by taude
1724 days ago
|
|
I think this is overly simplistic, and extremely naivive speaking as a manager. You sound like someone who's a year out of college (or suffering from some other immature personality characteristics) and/or working for a company with very few employees. I routinely orchestrate tech delivery between anywhere from 3 to 10 dev teams across our organization. I'm totally open for suggestions on better tooling that: a) don't require me to schedule a ton of meetings instead to get status on all the various teams dependencies, dragging everyone into meeting hell b) don't require me to use multiple tooling for different teams c) don't require me to make project plans in other legacy tools like Microsoft Project, or even the newer "spreadsheet" tools like Smartsheet or Airtable, etc... EDIT:
Some other features I use all the time (speaking mostly in JIRA land):
1) one click linking from the JIRA issue to the Github PR
2) Partitioned Kanban/Sprint boards for each team, as well as easy ability to rollup to master board for entire project
3) Ability to Search, advanced search, filtering, custom dashboarding, etc.
4) Array of plugins to work with other tools like Slack (I can one-click create JIRA tickts from slack conversations), and I can additionally run JIRA queries and bring in the results into my EMACS workflow.
5) I won't go into all the bigger company things like user management, integration with SSO providers, etc, since that doesn't impact me and my team(s)... In short-every one has their use cases. And orgs of various sizes will have their own. |
|