2 ms·
> When I ask this, I’ll often hear about benefits like tracking, accountability, visibility, estimation, managing dependencies, status checks, notifications, ex
by alkonaut 9y ago
> When I ask this, I’ll often hear about benefits like tracking, accountability, visibility, estimation, managing dependencies, status checks, notifications, executive roll-ups, and reporting. I hear very little about improved collaboration, better insights, improved quality, more effective retrospectives, and increased team motivation / sense of ownership / clarity of mission. I almost never hear about improved end-customer outcomes.
I agree with the author. Enterprisey tools for enterprisey use cases are probably detrimental to developer efficency, motivation, and probably also in some respect to end-user outcome.
But what the author doesn't address is that those enterprisey behaviors aren't there for fun. There are tons of levels of management that need to see those charts. You could argue "then fix that!" but then please tell me how to do that instead of telling me what tools I could use once that is done. I'm going to argue that for a lot of enterprise development this isn't possible.
I don't hear a lot about huge teams of mediocre developers developing large scale software with managers on all levels having the level of insight necessary to keep stakeholders happy - while doing all tracking in a simple trello board.
Now I'm not going to argue that TFS and Jira are nice and nimble. But the alternative to these aren't Trello, they are Trello + fifteen different secret steps you need to take to complete the now ad-hoc process.
"When you finish an issue you need to email the QA lead with the build number to test in, then email the required translators to fill in the necessary translations, then move a thing on a board somewhere, ...."
Unless all these things are magically not required, then I very much prefer digging a deeper Jira pit where all of this is at least encoded and enforced in the system rather than in a wiki or email somewhere.
It's not management that pushes these systems on developers. Management push the process (because you lose track of e.g. which translations were missing and you had an embarassing release somewhere). Developers then use the tool in response, because to developers, software is the answer.