And I completely agree with the article. It is EXTREMELY difficult to balance product development to have a good enough feature set and bearable complexity.
Here are two very typical feedback we receive from end users:
NEGATIVE. Compare to Jira Target process is way behind. No ticket has the testing phase. This is very poor by design and it is very difficult to learn, because so many things on the ticket at a time and cant locate important things like Sprint or who is assigned and in which state it is? Very badly designed system.
POSITIVE. It was easy to use, and since I've been forced to use Jira instead now, I miss so many of the features Target Process had... Sigh. Perhaps some day we can convince the company go to back to TP.
To be honest, there are more critical references than positive.
I have concluded several rules to myself from my experience:
1. Developers hate project management tools (rightfully so, in general). Anything more complex than Trello will be ridiculed and hated.
2. Teams should be allowed to choose own tools, but then we have a lack of high-level management overview. In this situation management almost always win (sadly).
3. Any serious PM tool should be a Platform with Apps in fact. JIRA is closest to this, but it is old and legacy have its price, so it is more complex then required. I expect to see completely new tools that will beat JIRA in a couple of years (Slack of PM tools :)