5 ms·
Agile has to work with actual human beings. Holding up the dogma and saying 'well perfect people would succeed' is more One True Scotsman. If nobody is a True S
by JoeAltmaier 8y ago
Agile has to work with actual human beings. Holding up the dogma and saying 'well perfect people would succeed' is more One True Scotsman. If nobody is a True Scotsman, what is the point of Agile?
- lmm 8y agoI'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.
- 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".
- jerf 8y agoLabels don't control reality. If I say to you, "If you remove your engine, open it up and clean it out, and put it back in, it'll fix your problem. I call this Cleaning the Engine." And then you come back and tell me that didn't fix your problem, and I ask, "Well, what did you do?" and you say "I Cleaned the Engine, just like you asked. First, I smashed the ignition. Then I rolled the windows up and down. Then I filled the gas tank with water. Now nothing works. Your Cleaning the Engine plan completely broke my car and it sucks!", I'm not going to be terribly impressed when I tell you that's not what I said to do, and you come back and argue "But I Cleaned the Engine just like you said! Oh, let's not get tied up in semantics and definitions, look, I Cleaned the Engine! I have a Cleaning the Engine consultant that says so." If Agile is to be damned, let it be damned for what it is. But complaining that "Agile" doesn't work when you take it, do everything pretty much the opposite of what it says, but insist on slapping the label "Agile" on it anyhow, isn't a very compelling argument. Before you have a problem with methodology, you have a problem with terminology. There is a sense in which Agile can't help but succeed, since it boils down to "Do the things that work, and keep checking that they work and check whether new things would work". The problem is, people don't want to do that. They don't want to have to do the checking work, or the thinking work, for any number of reasons (a few good, mostly bad). If you won't do things that work, check that they work, or sometimes try new things to see if they work, you can't expect the benefits of doing thing that work, checking to see if they work, and trying new things to see if they work, no matter whether you call it Agile or Scrum or Bumblekitty.
- Jtsummers 8y agoThis is why Lean and Agile are both failing in my place of employment. Lean (on the production side) because they failed to take into account one of the most important concepts of lean: employee empowerment. Rather than letting workers improve their own processes (or identify improvements to be approved by engineers if they made sense, some shortcuts don't need to be taken), they had management, engineers (sometimes), and manpower specialists walk through the area and come back to the workers with a statement like: Put X here, and Y there, that'll shave off 200 round trips a day and save you 2 hours for the work. They may not be wrong, but they've intruded on the worker's area without really consulting with them. They also gave the impression that the freed up time would be used to cut staffing (because now they can do more with less), rather than take on more workload. This scared the employees. Agile (on our software and services side) is failing for the same kind of reasons. "I heard we should have daily standups, so everyone have a daily standup!" Some teams have used it effectively, others haven't. Their leads don't know what to do with the time. Then we had people who insisted there's no planning in Agile (which is not true), and thought you could just throw things on the backlog and pull it off the queue and that'll be fine (they never go through the backlog and treat it correctly, prioritizing and grooming it). Which creates a bad result almost every time (surprise!). This leads to a bad impression amongst workers ("Agile doesn't work here.") and management ("Agile never works.") and customers ("We want you to lay out your 5-year detailed schedule because that 2-week at a time thing failed spectacularly."). The two extremes of Agile Adherents are both present here. Those who mistake Agile for Scrum or SAFe and believe there's a one-true-way with heavyweight (but not Waterfall!) processes. And those who believe it's an anarchic free-for-all with no processes and no plans. Both have missed the point of it, and both have made my job and efforts much harder.
- AnimalMuppet 8y agoAgile works fine with actual human beings. The problem is getting agile to work with actual managers, especially upper management. I mean, I've done agile with a team of maybe 30-40 people. It worked great... for a couple of years. When it fell apart, the problem was that upper management didn't know how to manage something that wasn't waterfall-ish.