Hacker News Reader

"Individuals and interactions over processes and tools"

It is precisely at this beginning point where most "Agile" teams fall flat on their faces. Instead, it is all about process, rather than said individuals/interactions. Scrum rituals are done because, well, everyone else does them, so that's considered "correct". Whether or not there is any value in the process is secondary.

View on HN

My company's leadership does not acknowledge or care about value delivered locally; it is all about cross-team collaboration. (If you get something done locally in 6 weeks, you wasted your time, while if you involve 4 other orgs so that it takes 30 weeks, everyone involved gets promoted).

It seems local variations in development processes as the #1 blocker to more cross-team collaboration, so it is enthusiastically steamrolling them.

It's also the motivation from management to build process. Rather than agile being a toolbox you pull from because it's helpful, it becomes a suite of metrics that managers and executives can track. Thus everyone must use the full toolbox because their benefit is overruled by management's benefit.

Reply on news.ycombinator.com