Trello is the best to keep track of where things are going and what the road map is. It's just so intuitive to use. Also, Slack for communication and zipBoard , which is our own tool, for exchanging feedback and collaborating with designers and managers on issues and bugs.
Hmm there are tons of nice tools out there, but unfortunately you cannot use everything, only the most suitable. Here is what i use with some explanation comments:
If you have a bigger project, and long term also, you might like the Atlasssian tools. We use them with my team on our projects :
On my personal side, I like to use ImDone package in Atom which is convenient for managing some small TODOs, and also OmniFocus (but this one is more about everything in my life !).
I'm more a fan of the one between my ears -- I've been writing software for what is very quickly closing on four decades, and to be frank I've found that when most "management tools" actually accomplish anything, it's to make up for a project manager not doing their job!
If you need some "tool" to do something like project management, you're the one being a tool. Eventually you end up wasting so much time on the endless extra steps and tools, you don't get any actual work done. It just makes it take longer to create a finished product, usually with less expertise, less insight, less learning, less innovation, and less understanding of how even your own code works.
If you need a tool to have people communicate, people aren't communicating. If you need a tool to manage code updates, the project manager isn't assigning tasks/provinces or doing their job of handling lower-level interactions. If you need a tool for time tracking more advanced than a punch-clock, you probably have lazy slackers playing farmville working for you in which case you fire their asses.
I often end up with the same opinion of versioning software; it's a crutch for nubes, and an excuse for people who have no business managing a project to not do their job... at least until you get up into really big projects like kernels or programming languages -- and even then I find their use dubious as again you end up without clearly defined roles assigned to people working on it, waste more time configuring and creating accounts than you do having people work, and don't even get me STARTED about the headache of regressions they CAUSE when they're supposed to be preventing them.
... Though more than anything I am shocked at when these giant tools end up used on small projects, creating MORE work, taking MORE time, and generally resulting in MORE code that's bloated and inefficient, then people magically label the entire process as having been "easier". Sets off my bullshit alarm faster than viewing the source of a COBOL application from 1978 and seeing two comment lines for every line of code.
But again, on average in most web development environments, I use 1/10th the code everyone else seems to think they "need". Probably because I'm not dumb enough to use "frameworks" just like I'm not dumb enough to waste time dicking around in "management tools" on projects that shouldn't be complex enough to need them.
Sadly, it seems most people take simple projects then MAKE them complex; as if they want them to be as hard as possible and cannot even conceive that it could be done simpler, faster, and with greater expediency without the "tools".
As a team, we use:
Personally
With trackingtime.co, we are not actually interested in how much time the developer takes to finish a task. That tool is a personal thing for a developer to make more accurate time commitments in the future.
Work:
Personal:
Looking into https://www.upwave.io/ as a possible Trello replacement since I dont need / use full blown trello.
Note: Edited to expand on other tools
Rahul Radhakrishnan
Content Marketer
Developers in our team use: