4 ms·
The problem with agile is it's not management friendly. And since they cut the checks, they get to dictate how things get done. All they care about is when is i
by sharemywin 11y ago
The problem with agile is it's not management friendly. And since they cut the checks, they get to dictate how things get done. All they care about is when is it going to be done and how much will it cost. Oh, and make sure all that shit management promised is in there.
- emodendroket 11y agoWell, it does seem like an odd thing to sell your customer on, doesn't it? If you wanted to do some home renovations and somebody told you they had no idea how much it would cost to do until they started working on it, you might be uncomfortable. There are scenarios where this isn't an issue but I wonder if it's as broadly applicable as we've made it out to be.
- hiou 11y agoIts almost as if service based economies are not that compatible with property rights based capital markets.
- emodendroket 11y agoOK... so what do you propose software developers do to usher in the post-capitalist age?
- mindcrime 11y agoIts almost as if service based economies are not that compatible with property rights based capital markets. I don't see it quite that way. Services business work in our economy, but if you're doing something on a services basis, you have to understand the implications of that and how to manage them. There are all sorts of services in our economy that work (mostly) fine today. To illustrate what I mean, let me use an example.. if you take your car in to a shop for repairs, you expect an estimate, and you aren't necessarily pissed if the final tally is off the estimate by a bit. But you will be royally pissed if it's off by an order of magnitude or more. So, do software projects sometimes cost (in time, money, both, etc.) an order of magnitude more than estimated? Yeah, I'd say so. But here's the rub... are car mechanics better at estimating than software developers? Not necessarily, but their customer doesn't typically come along when the project is half done, and yank the rug out from under them and ask for something that negates half the work they've already done. "Yeah, about replacing that spun bearing...I don't really want that, just replace the fuel injectors instead". Nope. Doesn't happen. But I'll argue that the equivalent does happen in our world. Of course the Agile Manifesto is all about the idea of embracing change, and accepting change even late in the process. So we have to accept that and deal with it. But the rub here is that we have do so in a way that doesn't come across to the customer as an order of magnitude failure. This is one place where I think we, as an industry, kinda fell on our swords. WE understand agile, but we didn't always educate the customer on what agile meant. And we didn't do a very good job of communicating to the customer what the impact of their change in requirements is. We accept changing requirements, yes... but we haven't always made it absolutely clear to the business customer that "making this change is the equivalent of asking the auto mechanic to replace the fuel injectors instead of fixing the bearing. This is throwing out all the work we've already done, and we need to re-estimate everything now." Is it because IT people lack the nerve to push back when business users make huge demands? Or something else? I don't know, but over the years I've become convinced this is a big part of the problem. We let the users change things (which they have the right to do), but we don't make damn sure they understand the implications of what they're asking for, and update the estimate/plan/etc. to reflect the new reality.
- sharemywin 11y agoThat's the problem with outsourcing. Most outsourcing companies will let you spin around in circles charging the whole time even if they know a better way.
- mindcrime 11y agoIf you wanted to do some home renovations and somebody told you they had no idea how much it would cost to do until they started working on it, you might be uncomfortable. Right and this why I say that so many people are (intentionally or not) misunderstanding what "agile" means, and selling something else using that label. Look at what the Agile Manifesto actually says about plans / planning and what not: Through this work we have come to value: ... Responding to change over following a plan ... That is, while there is value in the items on the right, we value the items on the left more So, all those people out there acting like "being agile" justifies operating with no plan at all, are NOT really in alignment with the core principles of agile. Agile does not prescribe "no planning" and never has. What this was all in reaction to, was the idea of BDUF (Big Design Up Front) and the concept of spending huge amounts of time building models and creating artifacts which, in and of themselves, delivered no value to the customer - and furthermore, were likely to be changed anyway. If "agile has failed" is really true, then here's the one place where it probably failed: It was never prescriptive enough. Which might seem paradoxical, but the problem is, the AM is subjective enough that people could find justification for whatever bullshit ideas they came up with, in the Manifesto. :-(
- vonmoltke 11y agoHaving dealt with US Federal Government customers and multi-year projects, I think the issue is that it gets really hard to provide an accurate cost and time estimate for the whole project without a BDUF, at least once a project gets beyond a certain size. This is especially true when the project is just a piece of a larger product and needs to coordinate with other subprojects. It may be that agile is just not appropriate for such projects, in which case I wish companies and customers would stop trying to force-fit them.
- TheCoelacanth 11y agoIt's really hard to provide an accurate cost and time estimate even with a BDUF.
- 11y ago
- stcredzero 11y agoAre you redefining "friendly" as, "makes promises that can't be kept and tells you what you want to hear?"
- bitwize 11y agoIt's an operational definition of "friendly", as implemented by middle managers across the globe.
- stcredzero 11y agoBy more than middle managers. I think some people also use this when seeking relationships.