6 ms·
Is there an example of a company that has implemented the philosophy in the Agile Manifesto in a way that actually meets the needs of developers and managers?
by ryandrake 9y ago
Is there an example of a company that has implemented the philosophy in the Agile Manifesto in a way that actually meets the needs of developers and managers?
I read this all the time: The agile folks were right about software development, but Scrum/consultants/managers/process sucks! Everyone likes the Agile philosophy but then they all say it's never been implemented right. Reminds me of the "communism is the way--it's just that every time it's implemented it's done wrong!" argument.
My criticisms of Agile are: 1. It doesn't scale to team sizes beyond the point where "individuals and interactions" can drive progress; and 2. it addresses developer needs but does not sufficiently address the requirements of the rest of the organization, including management. Developers gotta develop, but the rest of the business needs things like measurements, reports, status, ETA, sometimes proposals, change requests, etc. A methodology that does not address these artifacts is going to have a hard time fitting in.
- zdragnar 9y agoThe agile manifesto was never intended to be a value proposition for the business per se, it was intended to be a promise of professional discipline. You don't ask the business if a refactor is okay, because the business doesn't know how to value or risk it. You refactor because that's what a disciplined professional does, in the course of their work. Think of another profession, if that helps. Teachers don't ask students or administrators if a test would be valuable after a given lesson. Builders don't ask if a hammer would be appropriate for a nail, or if they should use an air gun. There's a certain expectation that they should know and do these things. Scrum works if the scrum master functions as a mediator for the team to collaboratively prioritize work- ideally, this would be a role, not a job title. Scrum fails if the scrum master is just a project manager tasked with making sure the whole backlog entered by the product owner is done on time.
- sanderjd 9y agoI think I agree with you, but I find your analogies quite lacking, which makes me question our shared premise. Teachers absolutely do have the cadence of tests after lessons dictated to them by administrators. Builders absolutely do negotiate with their customers over whether their "implementation" is sufficient or whether it should be "refactored" (ie. partially or completely torn out and re-done to improve the quality). I'm not sure where this leaves things, but it seems to me that the differing incentives and negotiation between stakeholders is perhaps inevitable.
- zdragnar 9y agoI realized as I wrote it that the analogies were flawed, but I rushed myself a bit to finish writing. The teacher analogy depends entirely on the school district, and perhaps might apply more to a university setting than a grade school one. As for the builder, of course there's a discussion between the builder and the client... On the desired results. What a disciplined builder won't do is ask "can we" when they know that the current status is structurally unsound or flawed. There's some substantial differences in cost / financing and risk between the professions, so it's a bit of a stretch no matter what, I'll grant you that. If we can at least agree that there is a certain amount of discipline that embodies a profession, and that the agile manifesto emphasises priorities characteristic of that discipline (correctly or incorrectly) rather than a "business process" or "project management" scheme, then I think we're agreeing on the important points.
- chris11 9y ago> Is there an example of a company that has implemented the philosophy in the Agile Manifesto in a way that actually meets the needs of developers and managers? I'd guess most companies that call themselves Agile or decide to try Agile won't do that, but great companies can implement the Agile Manifesto in ways that make both developers and managers happy. It seems like a lot of agile consultants sell Agile by trying to convince management of it's benefits. That top-down approach conflicts with the Agile Manifesto's bottom up approach. I'd think developers would generally be happier with Agile implementations that were led by developers, not management. I'm not quite sure how that would meet specific business needs, but I think that a lot of developer complaints come from management decisions. I agree that a lot of problems can occur when trying to let "individuals and interactions" drive progress. Of course, a lot of these thoughts are because I've worked at places with really corporate versions of agile, like SAFe.
- dragonwriter 9y ago> Is there an example of a company that has implemented the philosophy in the Agile Manifesto in a way that actually meets the needs of developers and managers? As far as I can tell the best implementations lean heavily on the Lean rather than Agile tradition; Lean has very similar values, but much better early operationalization of those into high-level practices which helps resist cargo culting low-level processes.
- oceanghost 9y agoThe problem with agile is it is naive. It assumes everyone is acting in good faith and thus it can easily be turned against developers. What I've seen consistently is managers are willing to turn responsibility over to developers but not control, and yet that's the core tenant of agile, developers are in control. I have never seen a company that practiced agile that did not have deadlines. "Sprints" alone are toxic. To sprint is to exhaust all of one's resources, and rest. When was the last time you were allowed to rest as a developer? Most companies just say, "Sprints start every other Monday". "Respond to changing markets" becomes "managers don't have to plan." "Developers are in control" becomes "all jobs now belong to developers." And finally, the most toxic element of all is the misapplication of agile. Agile works for websites and mobile, THAT'S IT. You cannot plan infrastructure in 2-week increments (yes I've seen this attempted).
- jacques_chester 9y ago> Agile works for websites and mobile, THAT'S IT. From your experience. This is a kind of No True Scotsman. If agile is working on massive multi-team, multi-site, multi-timezone, multi-company projects, then apparently it ain't agile. My experience is different. I've seen it work and not work. Right now I'm seeing it work. It works well; the core of which is asking what's sucking and how we can fix it.
- maxxxxx 9y ago"the core of which is asking what's sucking and how we can fix it." This seems to be a taboo for a lot of managers. They'll do almost anything to avoid listening to their own people and fixing the problems they mention. Only outside consultants or management further up can be listened to but not the people they manage.
- jacques_chester 9y agoI think you're right.
- oceanghost 9y ago
- marcosdumay 9y ago> It doesn't scale to team sizes beyond the point where "individuals and interactions" can drive progress; Is there any methodology that scales that way beyond the fuzzy and personal "get somebody competent divide the work into small independent chunks"? Any methodology that treats developers as replaceable gears will have the same failure cases. It's not Agile that is the problem.
- kpil 9y agoSpot on. If the captain and the navigators are incompetent, and the shipping company send you to the wrong port, then no crew can save the company. The places were "Agile" goes bad, are the places where just about every management process goes bad. If too many don't know how how the sausage is made you get "list guys" running around with lists and metrics that don't make sense, reporting to committees filled with other "list guys", an ever increasing admin-per-developer ratio, and a productivity that slowly falls down to zero. Faking process and order is much, much easier than actually managing the semi-chaos that a large development process is.
- maxxxxx 9y ago" Is there an example of a company that has implemented the philosophy in the Agile Manifesto in a way that actually meets the needs of developers and managers?" I have worked at two startups and there I think we implemented the Agile Manifesto. We talked to each other and got things done. There were no pure management types whose only job it is to report further up the chain. But these were teams with a max of 20 people so I am not sure how well this will scale up.
- jacques_chester 9y ago> Is there an example of a company that has implemented the philosophy in the Agile Manifesto in a way that actually meets the needs of developers and managers? I work for Pivotal, so I'm going with "yes". > It doesn't scale to team sizes beyond the point where "individuals and interactions" can drive progress It says "over processes and tools", not "strictly instead of". If anything, good tooling lifts a lot of overhead out of the way so you can go back to individuals and interactions. Of course, scaling this stuff is hard hard hard. But that doesn't make agile irrelevant, it just means you need to keep thinking and rethinking what you're doing. > it addresses developer needs but does not sufficiently address the requirements of the rest of the organization, including management. Developers gotta develop, but the rest of the business needs things like measurements, reports, status, ETA, sometimes proposals, change requests, etc. Evolved XP+Lean is pretty much where Pivotal starts from. Engineers asking product and design questions is taken as status quo. Sure, it's hard, but it's not about "agile can't scale". We've scaled it and doing so is painful and difficult. But any organisation passing the Dunbar limit is hard to keep on track. The classic methods work, we're surrounded by their fruits. But we're also surrounded by their waste. It's always worth questioning yourself and why you do a thing.