If you are building command and control software for an energy power plant, or medical software, you probably have a lot of regulatory requirements to meet so it may require a more intensive PM tool for tracking of work, sign-offs, etc.
If you are building time tracking software for managing a staff of retail employees, precision and regulations are very different than a power plant.
My suggestion is the most minimalist set of features to help the team stay organized and get things done. All the extra features packed in claiming to make things easier never really do. There is no silver bullet to make projects go better than a team that gels together well and a PM tool, or any software, isn't going to be the key thing that makes that happen.
The left window shows a good estimation of my current workload and progress, and the right one shows my velocity (beside other things).
My only problem is that it doesn't really scale for bigger teams:(
A room set aside for the purpose, with lots of marker boards. Add sticky notes. It doesn't get any simpler or smoother than that.
For digital, I've found gitlab and redmine to have far simpler and smoother tooling than anything from Atlassian (jira, confluence, ...), but initial setup and ensuring everything is smooth is key.
For digital, be lazy about data entry. Instead of making a ticket for every little thing, try to capture clumps of things on a wiki page, jumbo ticket, or something, deferring ticket creation until you have to. The more tickets you have, the more time you'll spend managing them. A wiki page with a bulletized list is way easier to manage than a ticket for each bullet on that list.
Personaly, I am sick of the term "workflow" since it has been overused by literally every SasS platform. But this Meegle thing seems to truly link all the tasks in a mind-map like diagram looking intuitive. No one has ever done that.
Just wondering if this approach could be a real change for cross-function collaboration. Any thoughts?
The task manament system was great and that it was integrated with everything. I could also just be that it was that everyone was forced to used the same system so there wasn't the bs of each department having their own system.
Microsoft Project sucks, but it useful as an "industry standard" file interchange format.
For medium size projects, my team used Airtable to good effect, customizing it to suit our needs while still maintaining ease of use.
Not being sarcastic.