We've standardized on Github Issues as the PM core, Waffle to prioritize, and Slack to communicate. The tools largely stay out of the way, unlike many of the on

We've standardized on Github Issues as the PM core, Waffle to prioritize, and Slack to communicate. The tools largely stay out of the way, unlike many of the ones I've used in the past. Give the bureaucrats access to the appropriate rooms on Slack and keep 'em out of everything else. I've found the right tool is so incredibly team/company specific that third party advice on these matters is often useless, but I'll share a few additional data points in case they help. 1) I recently helped a 40 person dev team rethink their dev tools and they chose to adopt Trello, roughly using this post as a guide: https://community.uservoice.com/blog/trello-google-docs-product-management/ https://community.uservoice.com/blog/trello-google-docs-prod... The team was using Pivotal and will continue to do so, but adding the Trello layer on top allows the "bureaucratic overlords" the info they need to a) stay informed, and b) make better decisions on resource allocation. 2) If giving the business folks a window into dev progress is important, also check out Sprintly. They do a great job at that. Good luck!