Well, I must admit I meant s/talking/any kind of direct communication/, but if colocating works for you... :) Just to offer the view from the other side, I'm c

Well, I must admit I meant s/talking/any kind of direct communication/, but if colocating works for you... :) Just to offer the view from the other side, I'm currently working with a group that's very embracing of remote work and fluid schedules, and still easily ranks as one of the most highly communicative and well-organized places I've had the fortune of experiencing. It's hard to look straight at a good situation and say "why" the magic is there with any certainty. That said, from this group I've noticed our PMs are very focused on asking developers questions to help keep the issue tracking to reflect their work, and very rarely make any changes until discussing them out-of-band. Doesn't matter if it's in person or over Slack or video Hangouts; it's the pattern of involvement that seems to cause the spark. It's a habit I definitely intend to try to take with me. I'm not sure user-oriented queues could be completely emulated with view filters. Maybe it's possible, but optional views seem to have limited impact on the overall flow of work unless everyone in the team agrees to use them. As an aside, the abundance of optional views and filters is one of my biggest beefs with the likes of JIRA. The first thing I do if contracting within a new group that uses JIRA is ask exactly which views and filters the PM uses to navigate the backlog, because otherwise I'm hopelessly lost as far as getting on their wavelength... and this makes customizable view features quite the irony to me! Tracker mostly seems to dodge this bullet since everyone lands looking at the same lanes in the same order by default, which is cool -- that kind of informational inertia in layout and navigation is huge. (That concept of inertia also jives well with per-user queues: someone can freely organize their own tasks in a personally meaningful way without wrecking the inertia another user's view.) The trick is keeping that inertia feature intact when huge amounts of info gets dumped into the system. And I'm totally on board with the countpoint "you just shouldn't have that many tasks, because you're fibbing yourself anyway", but at the same time, I really can't recommend a big enterprise starts just haemorrhaging security tickets from the record entirely if they can't keep their todo list short enough. Perhaps length-limited per-user queues combined with different mechanisms for "not on anyone's radar today" backlog grooming can find a new sweet spot?