3 ms·
I've seen it succeed, in a lot of places, and the difference between places where "Agile works" and places where "Agile doesn't work" seems to be that the place
by lmm 8y ago
I've seen it succeed, in a lot of places, and the difference between places where "Agile works" and places where "Agile doesn't work" seems to be that the places where "Agile works" are the places that actually put even a token amount of effort into actually doing it. Like, in one of these threads I saw someone saying that standups were a bad idea because in their standup the manager sat down and the meeting took for 30 minutes. That isn't a problem with doing a standups, that's a problem with not standups.
I mean there is clearly some kind of genuine problem here, agreed, but the problem I see is "why do these people think they're doing Agile when they're doing literally the opposite of everything in the definition". I'm genuinely baffled. Is it a cynical lie from managers, or the consultants they hired? Do they genuinely believe they're doing it, and if so, how did they come to think that? Did this happen with other methodologies - did you get companies that claimed to do e.g. RUP or Six Sigma but were actually doing the opposite of everything those methodologies prescribed?
- JoeAltmaier 8y agoWhat about online standups? Nobody is standing up and not likely to. What about managers that fall into injecting themselves into every standup? Hard to fix that, hard to eject your manager from a meeting, and its a likely state that becomes the inevitable end point (see Markov Chain). There's no mystery here. Lots of stories the illustrate how they went wrong. People being people. Maybe they need more work on the front end, to condition participants to not bring their conditioned responses into it because it requires a new attitude or something.
- lmm 8y ago> What about online standups? Nobody is standing up and not likely to. Then it's not a standup. Maybe you can find another way to achieve the same aim, or maybe Scrum isn't suited to remote workplaces (I don't have enough experience either way) - if someone had tried to follow agile practice in a remote environment and found it doesn't work there, that could be criticism I'd be interested in hearing. But I just never get the sense that someone has actually engaged with Agile and found it wanting[1]; it always seems to come down to something like them: "Agile sucks" me: "What's wrong with it?" them: "We have this mandatory Agile meeting that everyone involved in agrees is pointless", just some criticism of something that has nothing in common with Agile except for both being a process. > What about managers that fall into injecting themselves into every standup? Hard to fix that, hard to eject your manager from a meeting, and its a likely state that becomes the inevitable end point (see Markov Chain). I haven't experienced managers in standups being a problem, but taking it as given that it is for you: if you're saying that you can't fix that then aren't you essentially saying that any process that your organization adopts will inevitably fail (unless you adopt a process with no meetings at all, which has other problems)? Agile gives you every possible explicit opportunity to fix the broken things in your process, including a regular dedicated meeting that's devoted solely to doing that; if your organization is incapable of doing that then I'm not sure what could ever work. [1] Not actually true; there is a group of people who prefer more up-front planning and tend to give a quite different genre of critique. But they also tend to be more measured and don't frame it as a problem with agile as such.
- JoeAltmaier 8y agoHere's a process that works: leave me alone to get the job done, and I'll report progress to you regularly. Leave the manager out of my day to day activities. In fact keep everybody out of my way. Agile explicitly puts people in my way, regularly, and with demands that I report progress with imaginary metrics. That's how I'd fix it. In fact I became a contractor so I didn't have to do agile any more. Now I get tremendous amounts of work done, using my experience and talent to attack root causes and write the critical code to get the job done. I see its a whole different attitude from Agile, I get that. But I'm adamant that I don't want what Agile does.
- lmm 8y ago> Here's a process that works: leave me alone to get the job done, and I'll report progress to you regularly. Leave the manager out of my day to day activities. In fact keep everybody out of my way. Hah, I almost said that that's where this genre of agile criticism seems to come from: the coder who believes they can produce a good product by writing good code without interacting with a customer and so regards any process as an impediment, and isn't actually attacking agile so much as attacking the very concept of process. What you propose is a good way to produce elegant code that doesn't actually do what the customer wanted at all; even if you personally can magically understand the requirements every time, a customer (or a manager) is right to be skeptical, because most programmers can't.
- JoeAltmaier 8y agoMost of the friction in agile is not about the customer. Where did that come from? Not fair to switch the subject for a pretended win!
- lmm 8y agoCustomer collaboration is right there in the manifesto.
- BeetleB 8y ago
- virtualized 8y agoI think the argument is that if it's so hard for most people to see the difference between "Agile" and "not Agile", maybe Agile is unsuitable for most. In my experience barely anyone who claims to work Agile ever looks at the values or principles, or reflects about their own work in a systematic way. Scheduling Scrum meetings is easy. Applying Agile principles to your actual work is difficult, especially if you are already overwhelmed by Scrum. People like Scrum because it distracts from Agile and doesn't interfere with your work much. You can serve time in Scrum meetings, then return to your actual work. Scrum fills a void, but doesn't ask any hard questions. Don't think about what you are doing, just show up to the meeting and go through the motions. People like to follow pre-made structures like Scrum. They don't like to define or change them. You could potentially insult someone. "The Scrum Guide says so" is less personal than "it makes more sense to do X". Clinging to a fixed process like Scrum inhibits being actually Agile because Agile is all about changes. Change requires courage. Most employees don't feel like courage will be rewarded. In our culture, courage is reserved for big companies or top-level management. In short, that's why "Agile doesn't work".