16 ms·
The age of cargo cult Agile must end
- mbesto 4y ago"Then build it, however long it takes." (from the referenced article) This is always my favorite fantasy. No one would have issues with "Agile" if you had unlimited time and money...but that's not how the world works. Hence why you break everything up into smaller chunks. It gives you clearly defined guardrails so that projects don't spiral out of control. EDIT: AND the people funding said projects know where there money is going. That's important.
- RangerScience 4y ago> unlimited time and money Yah. You run into a different issue even if you've got that. There's a lot of example of scifi/fant sagas where, as the author gains fame and (so it is assumed) gains more ability to say "no" to their editor(s), the series goes down in overall quality. AFAIK you can also see this is military R&D. (IMHO, you can see the flipside of that in a lot of web fiction with 1/wk+ release schedules) I'm pretty sure I'd never want to try touching a codebase built with unlimited time and money - I'd expect waaay too much code, mostly. IMHO, even if you have (functionally) unlimited time and money, spending unlimited time and money is still a bad idea. (Balance comes from opposing forces. If you don't have an opposing force, you can't be in balance. Budget and shipping can be treated as opposing forces.)
- JohnFen 4y agoA business mentor of mine used to say that the two primary ways startups die is 1) by not having enough money, and 2) having too much money.
- yamtaddle 4y agoThe best effects I've seen from agile practices have been getting everyone to frequently think about deadline/feature trade-offs, reducing the occurrence of surprise bad news. I'm sure this is possible without "agile", but it's a thing I've seen it aid with. The worst is probably standups-gone-wrong. There's little more demoralizing than a 20-person 3-team standup where you couldn't possibly care about what anyone says (because it's irrelevant to you) except three or four people, and you already know what they're going to say because you all, you know, talk, and then also having to turn yesterday's work into some epic (LOL) tale of adventure and adversity because your manager's in the meeting and that's the kind of dumb-shit tone they've set for it ("now—justify why I should continue paying you" with pointed, bordering-on-hostile follow-up questions to anyone without a sufficiently-convincing theatrical performance) and you'd like to keep your job. Starting every day with a half-hour of that shit. JFC. But, I'm pretty sure, overall, agile is one of those things where most places that it works, any halfway-reasonable system would have worked just as well, and places where it doesn't, no system was going to work.
- darreninthenet 4y agoThis is where a decent Scrum Master or Agile Coach makes such a massive difference... I've seen what you're describing so many times and it's a simple fix to get people to stop focusing on what they've done and to instead focus on what the team needs to do (ie focus on work not yet complete for the team and not what on the individual has done/will do)
- marcinzm 4y agoPeople care and should care about what they get rewarded for. If promotions/raises/bonuses are based on the manager's view of your personal work, as is the case at most companies, then that is exactly what a sane person should focus on. Removing the manager from the standup or adding another layer of a Scrum Master won't change that but merely change how they get that same information. Standup at least provides an equal opportunity for everyone to sell themselves in those cases.
- Pamar 4y agoSo people with better communication skills would get rewarded more than people contributing more on the actual delivery side?
- Scarblac 4y agoHe's not suggesting that's how it should work, he's saying that's how it does work at most places. It's my experience too.
- marcinzm 4y agoAs the other comment said I'm simply noting the unfortunately reality that what matters is rarely actual delivery. Trying to avoid that reality won't make things more tied to delivery but simply more opaque as to what they're tied to. There's exceptions but in my experience those teams don't bother with these types of deep discussions on process. The process is somewhat irrelevant since the expectations are fairly clear and what they will be measured on is also fairly clear.
- duxup 4y agoI can't comment too much on Agile but I can say that I don't trust my instincts as far as "however long it takes". First project I finished on my own I felt was FAR from finished, but it had to get out the door. It was missing so much.... Customers LOVED IT. They still love it ... crappy code, missing what I thought were essential features, and all.
- ericmcer 4y agoI am really struggling with this currently, I have agiled myself into a spiral of never being done. I am wishing I took a more waterfall approach so there was a fixed endpoint. For personal projects in the future I will adopt a more rigid design phase as you don't have designers and managers enforcing deadlines and sanity checking whatever tangents you go off on.
- wpietri 4y agoYou also have an agile option: release early and often! Use the feedback you get from users/customers to decide what to do next and when to stop. The problem with waterfall approaches to "fixed" endpoints is that at the beginning of a project you know the least. It can be comforting to imagine that you can fix an endpoint up front. But most projects worth doing result in a lot of learning along the way. I have heard of very few projects that did their 1.0 release and were so successful that they just stuck with that release forever.
- Waterluvian 4y agoIt’s hard to have this conversation given the countless definitions of “Agile” but I think the majority of what I’ve experienced does not help with the concerns you raise. Proper project management to enumerate concrete goals with well-defined timelines is what you need, which is obviously not a novel part of any Agile interpretation. Often the desire for Agile comes from not knowing how to manage a project and reaching for the popular thing that people think will magically solve their lack of expertise.
- ClumsyPilot 4y ago> Often the desire for Agile comes from not knowing how to manage a project Corporate Agile takes thr worst of Waterfall and Agile and combines them. It frees the management from budgeting for discovery and research, which are nessesary in waterfall. They can come unprepared. Then they demand all the things they expect from waterfall - hard deadlines, no surprises. Then thry change scope on the fly because 'its agile, right'. Agile does more to excuse poor managment than it does to enable developers.
- trentnix 4y agoI think this mostly nails how Agile is largely practiced. Being prepared with a clear, concise, well-communicated vision of what you want to build is essential to developing quality software, regardless of the adopted process. Agilists frequently argued investing time and energy into crafting requirements is an “anti-pattern”, so being unprepared became the Right Way To Work TM. This is 100% dead-ass wrong.
- and0 4y ago"Agile does more to excuse poor management than it does to enable developers." ding ding ding, maybe the most succinct description I've heard
- hinkley 4y ago> if you had unlimited time and money. If you had unlimited time and money, then you wouldn't need Agile. There's no intrinsic value in having 50% of the system working at 40% of the deadline.
- lmm 4y ago> There's no intrinsic value in having 50% of the system working at 40% of the deadline. In practice that's usually more valuable than having 100% of the system working at 100% of the deadline. Almost all deadlines are fake, and most requirements are too.
- deckard1 4y ago> break everything up into smaller chunks. It gives you clearly defined guardrails This is only true if management respects the estimates. In my experience, they do not understand why Fibonacci or t-shirt sizing, etc. are used. They mentally convert the points to some "X days" and then beat you in the head with it. They want to micromanage and they do not understand they are building software. You can't break certain tasks down further and you can't parallelize many tasks. You can bring up Fred Brooks but it's a hopeless cause. They will never get it. Then as you inch towards their arbitrary deadline (that they tell no one, by the way, because it's better the developers don't know about deadlines until the last fucking minute because "agile" and not "waterfall") they suddenly act shocked that 9 women really can't make a baby in one month. But I digress.
- wsc981 4y agoAt the end, those complexity number end up representing some time estimates anyway. Cause you will get the velocity graph, showing how much points have been completed this sprint and how it compares to previous sprints. The graph is expected to stay somewhat level or increase as the team efficiency increases. It will decrease when members are away on holiday. If your team capacity stays equal and last sprint your team completed 20 story points, it’s kinda expected the next sprint another ~20 story points are completed. So in that case 20 story points will represent about 2 weeks of work for the full team. I also think for many people complexity translates into time needed to finish work. A more complex task will naturally take more time to complete than a simple task. So from my point of view, it’s fair (if after a couple of sprints) a product owner might get an idea that 1 point is equal to -say- half a day of work. PS: I am not a product owner and not a big fan of ”Agile”. I think daily stand-ups might be overkill in many situations (in my current remote team it’s more like a weekly stand-up) and I generally hate retrospectives. I just want to get shit done (which is luckily the practice we have in my current team). We do have a task board, but we don’t do the whole assigning points stuff. And I am mostly free to pick-up any task I feel like working on. This is much more agile to me than “Agile”.
- Aeolun 4y agoThat’s generally true for that specific team in that configuration, but as soon as you start plucking people off, and adding other people to the team everything is up in the air again. It’s also a bad habit to rely on it.
- kerkeslager 4y agoOkay, but I could equally say, "No one would have issues with 'Agile' if developers could get infinite work done in a week... but that's not how the world works." The fact is, there's a limited amount of work that can be done in a limited amount of time with a limited amount of money. Developers want the time and money to be unlimited, while customers want the work to be unlimited. But none of that is how this works: all three of these things are finite. The point of "Customer collaboration over contract negotiation" is that the customer is involved enough in the process to see that you're producing close to optimally with the time and money they're giving you. Committing to an amount of work in a sprint doesn't work, because it always ends up with customers trying to get more work into the sprint--more production than ultimately is possible. And, it's worth noting, setting boundaries around that and guarding to prevent that, starts to just look like "contract negotiation" with a shorter contract. Sprints aren't agile, they're Agile: a marketable idea that doesn't work. Part of the problem is that customers see it as their job to get more work for less time and money, so they try to set aside what developers are telling them, the "work is limited" part of the trifecta. They see developers as their subordinates, so they think their desired outcome, where time and money are limited but ability to produce is unlimited, is reality. If developers and customers are seen as equals, both bringing needed value to the table, then this doesn't happen, because everyone agrees on the limitations of the situation. But as soon as you start treating customers as superiors, their view of the limitations becomes dominant, with predictable negative outcomes.
- alliao 4y agothis is the truth. quite frustrating in training materials it's all about empowering employees when it is totally not.
- bdangubic 4y agoYou can do this if you hire the right people. The only “process” that always works is “hire right people and the F out of the way.” The problem of course is that there are waaaaay too many software developers and roughly 93% are terrible at their job (this is just simple math, take anything and put millions of people to do it there will only be 5-7% that are actually good at it).
- Terretta 4y ago> spiral out of control Meanwhile, an '80s paper countering 'waterfall' with prototyping iterations called it the 'spiral method'. https://en.wikipedia.org/wiki/Spiral_model https://en.wikipedia.org/wiki/Spiral_model FWIW, the early '70s paper the DOD misunderstood as suggesting 'waterfall' had already said the right way was to build one to throw away -- but use the prototype to derive the usability, requirements, and design docs first.
- worthless-trash 4y agoThats not a rust command ;)
- rwaksmunski 4y agoIt's on nightly.
- deleted 4y ago[deleted]
- tacitusarc 4y agoI’ve recently found myself thinking a lot about the coercibility of ideologies as an intrinsic property of the ideology. Agile software development is certainly as much and ideology as it is a methodology, and it seems particularly susceptible to coercion. I know people who love it and who hate it, and they almost all have one thing in common: the all disagree about what it actually is. Personally, I think it’s clear and I am a huge fan of the espoused principles, but I feel like those same principles are constantly misinterpreted by people. Of course, maybe it’s me. Or maybe the Agile Manifesto is simply broad enough and vague enough that everyone interprets it the way they want
- Lerc 4y agoI'm not a fan of Agile for precisely the reason you give. If the principles are constantly misinterpreted, it exists as name without an anchor. I have encountered advocates of Agile who say that other people only say they use Agile but don't really use Agile. They are keen to point at successes an say "look They're using Agile" and failures as people who said they were using Agile but weren't really. You can't point to the foundational document because advocates will claim that Agile has evolved since then. It is unfalsifiable in the sense that no mater what critique you have, it can be avoided by using the shifting definition. The article here talks about Cargo Cult Agile, but the people doing that Agile don't believe it to be a Cargo Cult phenomenon. Who is the Author to claim that their view is the ground truth? Declaring that there are large groups using the name without the principles is the akin saying "My principles are less popular than you might think" It has gotten to the point that I don't believe the name is meaningful unless it as a Tribal identifier. To be frank I would like the name to go away completely. The principles should be able to stand on their own merit, people should be free to take the things that work for them. There is no need to Proper Nounify ideas other than to show you are talking about the same thing. For Agile, that ship has sailed.
- tacitusarc 4y agoI think that’s similar to what Dave Thomas talks about here https://youtu.be/a-BOSpxYJ9M https://youtu.be/a-BOSpxYJ9M
- davidthewatson 4y agoCovering the entire lean and agile history without touching on the work of Alistair Cockburn is missing some depth. He was on the list of Agile Manifesto signers and gave us Crystal and the Seven Properties. More than a thousand citations is evidence that Alistair's work was novel and established consensus: https://www.researchgate.net/profile/Alistair-Cockburn/publication/234820806_Crystal_clear_a_human-powered_methodology_for_small_teams/links/56d434b508ae2ea08cf8e07a/Crystal-clear-a-human-powered-methodology-for-small-teams.pdf https://www.researchgate.net/profile/Alistair-Cockburn/publi... See Chapter 2. Many of these methods were practiced by my team in Boston in the late 90's without the jargon. The results set the stage for how we'd work years later.
- WalterSear 4y agoAgreed. It's high time we moved on to cargo culting something else.
- fsckboy 4y agoat this point it feels like declaring something a cargo cult is a cargo cult
- WalterSear 4y agoNonsense! If there's one thing we know inside and out in this industry, it's cargo culting.
- prepend 4y agoThis is a long article that has some history in it, but I don’t think it makes a point. Who cares if Agile came out of Lean? It didn’t, but they are closely aligned. Agile is all over the place so it’s kind of hard to cargo cult agile. Maybe author is confusing it with scrum or whatever. And since agile is just a bunch of principles, there are also lots of dumbasses claiming to do agile when they are really just chaos.
- JohnFen 4y agoI really think that the problem with Agile isn't really Agile as such. It's that Agile, at least everywhere that I've seen it done, is used as a mechanism by management to squeeze developers harder rather than to be a better method of development. In other words, it exists to serve management, not product development. That's why it ends up as a means to treat programmers like machines. That's not really Agile's fault. As long as management has the last word about things, any methodology will end up the same way.
- galangalalgol 4y agoThe agile manifesto was a set of stated relative values that the authors felt lead to positive results when a development team bought in. It wasn't a description of any methodology or process. In fact I have never been able to tell how agile methodologies were related to the manifesto in any way. Software and manufacturing methodologies can be good as best practices or guidelines, but when they require documentation for following steps, and have a methodology for changing the methodology, they lose their value. If you have a well intentioned group of team players that understand the values and guidelines and buy in, then the formality is a waste of time, and if you don't have those people nothing can save you. Process gets used as a shield for accountability by those people not a tool to correct their performance. Accountability (not blaming) is simply a way to adjust the power given to well intentioned team players based on the results of their decisions and actions. It is not a punishment, even though it does hurt.
- Zigurd 4y agoOne thing I don't see very often in connection with Agile is the reasons pre-Agile project management approaches failed: Replanning a resource-leveled critical path analysis takes way too much time and effort for little benefit in the context of most kinds of software development projects. That, in turn, points toward incremental assignment of people to tasks as a key difference. There are of course many other differences, but exactly zero Scrum certification training courses even come close to mentioning stuff like this. "Cargo cult" is the inevitable outcome of not knowing anything about why one should do Agile for software development projects.
- BirAdam 4y agoSaying something failed is awkward as there are plenty of old software projects pre-agile that delivered amazing results, on time, within budget, at extremely high levels of quality.
- DubiousPusher 4y agoThere is nothing in agile stopping you from producing comprehensive designs or specs. Every project I take on these days has a pre-production phase. This phase is 1-3 sprints. It involves speccing sophisticated systems, designing UX and several spikes to evaluate technology. These all have outputs in the form of documents. Even the spikes should produce a short document outlining the technology recomendations and the reasons for the recommendation. Similarly, in a project with a more research orientation, we perform spikes which involve building various prototypes and documenting their feasibility. None of this conflicts with agile principals nor creates a situation in which engineers and designers are pressured to forsake, "building it right". In fact the only differences between this approach and "waterfall" is that there is frequent accountability and there is protection for the development team because they are still choosing what comes into a sprint. I generally find that whatever form the various criticisms of agile take over the years, there are generally two impulses really at work underneath them. Either management is trying to undermine the protections agile and scrum create for the dev team by violating the "only pigs talk" principal or it's developers trying to avoid regular accountability so they can build their castles in the air. To be 100% clear, I'm not even saying that approach never works. There are phenomenal developers who disappear for weeks and come back with magic. But often enough, developers who cannot deliver try to perform the same act and their incompetence sinks a project. The development team cannot collectively afford the risk to find out which kind of developer you might be and therefore you owe them accountability. We all owe each other accountability.
- deleted 4y ago[deleted]
- lumb63 4y agoYour last paragraph makes me wonder: are there two sets of people, one of people who perform better under Agile, and one of people who don’t? We acknowledge the above is true for, e.g., work from home, but have many ever taken the time to consider the same might be true for development process? I’ve worked with (and supervised) developers who I’m fine with sending off into their corner to do what they think is best for weeks at a time. I’m confident they’ll come back with something great, more often than not. I’ve also seen developers who I’m not comfortable with sending off on their own for even a day in between daily standups. I wonder if there’s a process that allows to reap the spoils of both types of developers. Naturally, I’d rather have a team of the first type and think hiring those is the best way, but inevitably, some of the second type make their way in.
- jjtheblunt 4y agogenuine question : did thomas edison's lab, or nikola tesla working alone, ever use a thought framework similar to "agile"?
- Jtsummers 4y agoReportedly it took 2774 attempts for Edison's people to figure out the lightbulb. So probably more like agile and less like Waterfall. Unless 2773 failed attempts were all part of the grand plan.
- Supermancho 4y agoIn Agile it's iteration. In waterfall, it's rework?
- Jtsummers 4y agoIn Waterfall it's a follow-on contract after delivering something that doesn't actually do what's needed.
- Hippocrates 4y agoI'm intrigued by the referenced article's rallying cry > It’s time to create a new operational standard. What does that look like? I do find agile to be tiresome and overbearing at times, but its operational model seems to make sense. At this point it has a an inescapable gravity. Can we think of a new operational model? I would love to try one out if I could just learn of ANYTHING else (please).
- wankle 4y ago"I do find agile to be tiresome and overbearing at times" Then you're doing Agile, not agile. "Can we think of a new operational model?" Yes, agile.
- Scubabear68 4y agoI can’t even comment on generic “Agile” because it is so vague as to be meaningless. Many teams I have worked with who have been successful work out their own process but slap “Kanban” on it as a label. It may or may not be Kanban, but by calling it Kanban, it is “acceptable” by TPTB as acceptably checking the agile box for management.
- civilized 4y agoThis is totally legit. Kanban is nothing more than tracking work by using tickets on a board organized by priority and status. It does not entail any Agile ceremony at all. I don't think it even requires that you track all the work on the board. It's a very lightweight system that most can benefit from.
- rjsw 4y agoI'm working on a project that is trying to apply "Agile" to document production. I feel that whatever teams merge shouldn't break the overall build but I'm not winning the argument.
- worik 4y agoI have learnt that it is not the methodology that matters most, but the people carrying it out. Second to the people carrying it out (the set of individuals) what matters next are the relationships between those people. Methodologies like "agile" are not completely stupid, but are mostly useless. It is the job of a team manager to manage their team effectively. A rule book has its uses, (not totally useless) but if a manager follows it slavishly, or in the face of resistance by their team, it is really bad. There is no rule book for good management. There is good and bad management, but the difference does not come down to a written set of rules. So, getting finally to my point, the age of "cargo cults" must die.
- daviddavidson 4y agohttps://archive.md/5rNqX https://archive.md/5rNqX
- MBCook 4y agoAgile is extremely popular for a reason. Whatever developers think it promises a way to wrangle complexity (breaking things down), adapt on the fly better than waterfall, and provide estimates so the business can plan better. Even if your company does it horribly wrong management is going to want those three things still. They won’t agree to take it away. You have to offer them something with the same (or more) benefits that works better. And “trust us we know what we’re doing” doesn’t tend to cut it. So I think we’re stuck with it for a long time, for better or worse.
- ryandvm 4y agoYou're right. Agile was never for the developers, it's for the business. Developers complaining about Agile is like kids complaining about their homework - it's to be expected. That said I've seen enough Agile projects flounder and fail to know that it's no silver bullet. Like homework, there is little indication that it actually fulfills its purpose. Whatever snake oil comes next is only going to gain adoption if it promises even more control for the business.
- MBCook 4y agoCompared to the previous process, often just waterfall plus total guesses, I actually see it as a real improvement. But people have to buy-in/trust it and do a half decent job. In my experience that’s not really what happens. Even half-assed agile (if that) at one place I’ve been was a real improvement, though not as much as it could have been. There was a clear difference in the teams that failed/refused to embrace it to those who tried.
- hgsgm 4y agoAgile was invented by developers for developers. For professionals, not people who want to be academics but get paid by a corpo.
- jstepka 4y agoMost software at the end of the day is the same as hammering nails. Anyone who builds anything needs a process and accountability.
- notShabu 4y agoSturgeon's Law rephrased "90% of all work processes are crap but labelled with whatever is popular" With "X is the problem", X is always a valid pointer to that 90% regardless of the actual merits or demerits of X itself. Changing fashions update the name, but the value is always the same...
- oscillonoscope 4y agoAs someone from the hardware world, I feel like very few of the agile evangelists have actually worked on a waterfall project. Everything they say about waterfall seems to come from hearing polemical takes on it. I have never been part of a waterfall project where the team didn't adapt partway through the project as requirements or understanding about the project shifted.
- anon23anon 4y agoI feel like when Agile first came out the local agile guru was basically an older programmer w/ a ton of years and wisdom under their belt who knew first hand why doing things a particular way was best. It's since becamse a 2 week course for anyone to enter the tech field. Feel the same way about the influx of cybersecurity experts. Those used to be really good devs who also knew a lot about security, now, don't even get me started.
- hgsgm 4y agoAgile was atarred5 by people doing small business consulting projects for clients, like "make me a website".
- ElfinTrousers 4y agoIt was started by people doing a giant business consulting project, for Chrysler. The Agile Manifesto came out of (some of? all of? I forget) the signatories' experiences working on the Chrysler Comprehensive Compensation System, using the Extreme Programming methodology. How well did that work out? From the Wikipedia article: "The one-year delivery target was nearly achieved..." "A few months after this first launch, the project's customer representative—a key role in the Extreme Programming methodology—quit due to burnout and stress, and couldn't be replaced." "The plan was to roll out the system to different payroll 'populations' in stages, but C3 never managed to make another release despite two more years' development." "Frank Gerhardt, a manager at the company, announced to the XP conference in 2000 that DaimlerChrysler had de facto banned XP after shutting down C3..."
- taeric 4y agoThere is something delicious about the main criticism of an article critical of agile being that it doesn't understand agile and was doing it wrong. I do think some of the points here are solid, but skip responding to the snark of the other post. That was literally the weakest part of it and generally not worth addressing.
- idiocrat 4y ago"The monkey has become weak in his eyes in old age; And she heard people That this evil is not yet so big of a hand: You just need to get glasses. She got half a dozen glasses for herself; Twirls his glasses this way and that: Now he will press them to the crown, then he will string them on the tail, Now he sniffs them, then he licks them; The glasses don't work at all. "Ugh abyss! - she says, - and that fool, Who listens to all human lies: Everything about Points was just lied to me; And there is no use for hair in them. The monkey is here with annoyance and sadness O stone so sufficed them, That only the spray sparkled." -- The fable "Monkey and glasses" https://freehotnews.ru/en/geometriya/istoriya-vozniknoveniya-basni-martyshka-i-ochki-basnya.html https://freehotnews.ru/en/geometriya/istoriya-vozniknoveniya...
- neilv 4y agoAll the Agile that I've seen is best suited to something like an outsourced Web/app agency that works for enterprise clients, and bills based on time. Just iterate, with uninterruptible chunks of billable time, and keep getting customer feedback on each concrete visual thing you can show them. If it's inefficient, and might miss big-picture needs/opportunities/coherence, but you're making revenue on that inefficiency, promptly and recurring. And the customer's many stakeholders are probably happier than if you'd tried to do project management. They don't have to think hard upfront, nor coordinate too much, nor commit to risky decisions. They just have a meeting every week or two, to approve/reject/bikeshed. Unfortunately, sometimes this methodology is applied to projects for which it's not suited as well, such as for a company that needs a solid product and business model. (Not VC-growth-oriented startup that hires a ton of people, for whom sprint tasks are a "proof of work" productivity, which is a relief from the organization's hard coordination problems.) And I get the impression that a lot of people in tech right now have never been on a team that exposed them to project management other than creating and doing individual sprint tasks.
- Fellshard 4y agoWhat's fun is that even though this is highly useful for that type of relationship, the firm I used to work for would tout these practices and claim that's how they believed clients would best be served; and then as soon as we set foot on the ground, they'd just capitulate to whatever worst practices were on the ground, out of 'pragmatics'.
- wpietri 4y agoHaving done entire startups with release-early, release often approaches, I disagree. Customer feedback, used well, increases efficiency because you can test customer and product hypotheses, allowing you to stop working on the things that aren't worth investing in. Is it true that you can be incoherent like this? Sure. But people doing waterfall approaches can also build incoherent projects divorced from actual needs. But it's perfectly possible to build a solid product and a good business model releasing early and often.
- gobengo 4y agohttps://www.asyncagile.org/method-stack https://www.asyncagile.org/method-stack
- ptkanchi 4y agoAgile is a form of babysitting
- CSMastermind 4y agoAgile as typically implemented is a set of processes developed by web consulting companies to deal with difficult clients. If you're a web consulting company dealing with a difficult client it's probably a great way to make sure the project actually gets delivered and you actually get paid. If you're doing something different then you might find the processes more or less useful depending on your domain.
- uglygoblin 4y agoInstead of just bitching and moaning somebody senior on the team needs to aggressively push back with productive feedback and compromise. You can't just say stop all of the process. You are invalidating the Scrum Master/TPM's existent and will just meet fierce resistance. Ask them to let you run the the standup the way you want to run it one day as an experiment. Ask them what metrics and reports are being shared so you understand why this is a hill they will die on. Ask them to participate as peers during the ceremonies so they understand where you're coming from. Ask why and explain why.
- CSMastermind 4y agoThe root problem in my estimation is that people want a boilerplate bureaucratic process which they can follow and achieve good enough™ results. A lot of the activities done in agile or scrum or whatever processes are potentially useful tools in specific situations. But people don't want to understand the history and reasoning behind the tools nor do they want to apply them judiciously as appropriate. They want a one size fits all process that produces results, if not optimally, at least consistently. And whatever Agile flavor of the month is popular is just that, it's good enough. And the benefit is that you get this fun mind trick to deflect blame ("I don't know what happened we followed the process. People don't fail processes do.") or ("I'll tell you what went wrong we didn't follow the xzy process. If we had just agiled a little harder this project would have shipped on time").
- lowbloodsugar 4y agoAnd the boiler plate process thinking is the literal opposite of agile.
- matchagaucho 4y agoMost companies will go through 1-2 agile boilerplates before defining, building and owning their own process. If a team moves onto a 3rd boilerplate, they've missed the premise of agile retrospectives.
- dilyevsky 4y ago+1 the problem is the management’s desire for modern day taylorism. Once that line of thinking sets in it really doesn’t matter which process you pick it’s still going to suck
- tharkun__ 4y agoAnd it works so well with metrics! S.M.A.R.T, right? Wrong! Goodhardt's law. Once you put any sort of pressure on the metric, it collapses. Deliver X story points per sprint? WTF? That is not the spirit of agile. That is Big Corp subverting what agile was trying to subvert from big Corp Man Days in the first place.
- athrowaway314 4y agoI think it's happening. Capital One got rid of the 'Agile' division. Capital One follows leads from FAANG type companies and in turn, there are some other banks that follow (and marvel) what Capital One does. https://medium.com/serious-scrum/agile-layoff-nightmare-at-capital-one-460b28612121 https://medium.com/serious-scrum/agile-layoff-nightmare-at-c... Edit: another URL in case you don't want the one above: https://www.theregister.com/2023/01/20/capital_one/ https://www.theregister.com/2023/01/20/capital_one/
- trentnix 4y agoThey will just glom on to some other cargo cult. It was Six Sigma and the Capability Maturity Model and PMPs as far as the eye could see before Agile, Inc. figured out how to package and sell itself via SAFe and certifications. Companies like Capital One will inevitably be seduced by the next great idea and will avoid hiring real leadership at the product and team level at all costs. Decision-makers got to their lofty corporate positions because of how well they play the game will do everything in their power to make sure the game continues.
- drdaeman 4y agoNot meant to defend (or bash) "agile" stuff, but isn't banking industry quite weird when it comes to modern software development? I'm simply not sure they can be a good example, given how generally awkward and legacy-ridden the whole industry is.
- wankle 4y agohttps://agilemanifesto.org/ https://agilemanifesto.org/ "Individuals and interactions over processes and tools" (a)gile wasn't about "ewww your software is old and stodgy so you can't play in our sandbox!"
- mr_00ff00 4y agoCapital One is still doing agile, they just fired the people that have that as their whole job. The managers and engineers now are in-charge of doing agile duties.
- 0xbadcafebee 4y agoThe agile manifesto makes no sense. 1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. What if the software requires a lot more work before it becomes valuable? What if continuous effort isn't sustainable or there aren't many features required? What if this just leads to software development for its own sake? 2. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. What if change is so constant that you never ship a single working feature? Or every time you change, it breaks the user experience? Or you simply can't keep pace with how much of the app is changing and are stuck in tech debt hell? 3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. What if the software is running in a car? A plane? A bank? A pacemaker? A power plant? On and on it goes. Stupid overgeneralizing proclamations that are trivially debunked, yet passed off as some kind of grand scheme to solve all that ails making software products. You know what software is? Materials. Materials are used in our everyday lives, from textiles to plastics, structural steel to paper. You build a machine to grow the cotton, then a machine to harvest the cotton, then a machine to spin it, then a machine to weave it, then a machine to dye it, then a machine to cut it into a pattern, then a machine to stitch a logo into it, then a machine to make the plastic bag it's packaged in, then a machine to ship it, and so on. All of those materials and machines are created by people, and then used by people. They break down, they need maintenance, they get replaced, and they get used. The significant difference is, most of them aren't made so only Gardening Machine A can be used with Weaving Machine B to go into Dying Machine C and be used on Cutting Machine D, etc. Software is written in a little box, and it's very fragile, like the works in a watch. It's not durable and universal. It's delicate and tiny and intricate, and made to fit. We spend all our time fretting and niggling and poking and prodding and teasing the software, and wonder why we can't ever estimate how long it takes to make something. But it's because we keep making new watch springs, each one slightly different than the last one. Of course there's no consistency; we're not making things consistent! The software industry is like an industry of teenage art school students trying to build hospitals. Quite expensive and complicated, but made worse by a whole bunch of "creatives" constantly changing things to fit some custom ad-hoc sculpture sitting on a platform of marbles. The people who are smart enough to make it won't do it in a way that's repeatable; the people who have the money refuse to contribute their work to some sort of general industry-wide commons of resources; and the people who organize them just want to get anything done, so who cares about rigor or process or efficiency or uniformity, just shove some shit out the door so I can collect a paycheck. At least cargo cults deliver a plane every so often.
- Consultant32452 4y agoIn my experience talent will succeed in any system and lack of talent will fail regardless of the system. Engineers will never design a system that accurately detects who is doing a good job vs not. It's not in their self interest to do so at scale.
- at_a_remove 4y agoCults gonna cult, and with special names like scrum master and rituals like standup, well ... cults have a way of fragmenting, as per the old Emo Phillips joke. Agile, in its flexibility, lacks what might best be called "orthodoxy." It lacks punishments in accord with the most common failings. "He hath spoken the forbidden word 'deadline,' and we must pelt him with marshmallows." I'm joking about that, but only sort of. Agile has entirely too many ways it can be taken advantage of by bad and/or incompetent actors to be all that forgiving. I've seen so many sins: the stakeholders who will never meet or communicate with you, the deadline given only to have seven months elapse before they look at the product, the demand to see the prototype in the first week with all of its features (leading me to ask questions like "How fast does ten percent of a Porsche go?" and "If the prototype is feature complete, how is it a prototype?") Standups with a lot of clucking from the chickens, standups where the wrong people were present. It isn't even a "process," it might better be defined as a failed attempt at a meta-process. It lacks the equivalent of unit tests and commandments graven on stone, so pretty much anything ends up going and Agile stops having its one original virtual: kicking the ball back to the stakeholders constantly so that the developers cannot be seen as the hold-up. Really, that was the original magic of Agile, just keep punting it back to them so it is that much harder to blame programmers. This failed pretty early on. As I grew more disenchanted with my latest cult exposure, for one project I finally built in a very specific "Did they even look at it?" framework, much to my boss' eventual dismay. I could tell who looked, when, how much of it, everything. He was very into Resume-Driven Development and blaming anyone else, so me batting it back on the absentee stakeholders didn't go over well ... but that was the original methodology of Agile. And the defense is always the same: you didn't pray hard enough, you didn't pray right.
- jalapenos 4y agoI'd say the problem is a bit simpler than this: ability. When you're part of a firm that's staffed by those with middling abilities, using concepts like Agile Development like a blunt instrument is typical. The reason isn't a complex one. Simply, that's the best they can do. In high performance firms, which are attracting the best and brightest talent, you have a lot less problems with this. They easily come up with taylored managerial solutions to managerial problems, perhaps inspired by ideas from various sources including Agile, rather than picking up a popular methodology they know of like a cudgel and beating everyone over the head with it. This is why discussions around this topic aren't that fruitful. The only fruitful course of action is to strive to get employment at more competent firms with smarter managers. I.e. work yourself up and out of it rather than bemoaning it.
- sesteel 4y agoI would have argued against this perspective a few years ago, but given my current situation, you are right. The ability to comprehend and manage complexity faster than others create it is key. The more help you have the better. Work with smart people who think about what they are doing.
- d--b 4y agoAnother “xxx sucks”, “but you’re doing it wrong” article . Be smart, keep what works, turn the page.
- justusw 4y agoYes, and who else is annoyed by random Japanese words being used to say the thing English but make it sound exotic and sophisticated? From the article: “Jidoka: the harmonization of people and machines” (jidoka/自動化 which literally means automation), or random TED talks about Muda, Ikigai, or Mottainai (sprinkle in Konmari for good measure). People here in JP think, what’s so special about these words? Kanban in the end just means signboard. I get that adding memorable words to things sometimes gets the point across extremely well, but all those other times, just say the thing you would like to say, heh.
- cratermoon 4y agoSometimes words have inflections, implicit, or multiple meanings in different contexts. The point of using a word from another language is to emphasize the meanings that it evokes beyond the literal, and always inadequate, translations. The simplest example I know of in Japanese is "hai", which literally translated means "yes", but はい doesn't necessarily signal agreement. Take the english word, "okay". Depending on the context and how it's said, it can mean simple acknowledgement or something closer to WTF. Of course people who think the literal translation is the meaning will miss the connotations.
- jotaen 4y ago> Of course people who think the literal translation is the meaning will miss the connotations. Isn’t that exactly the problem, though? In my mind, these loan words from other languages create the illusion that they were clear and unambiguous. In reality, however, people still often enough talk cross purposes, but as they now use exotic language, they often won’t even notice. (And when they do, they start a flamewar about who has the right definition, which rarely leads anywhere useful.) One other downside is that all that made-up wording makes it unnecessarily difficult for job starters to find their bearings. If you organise your team’s tasks with post-its on a whiteboard, why not just call that “task board”, plain and simple? That might not imply all the particularities of the process, but there are many examples from all areas of life where terms in themselves don’t convey perfectly comprehensive meaning, and yet, people manage to deal with that.
- teerak 4y agoIt will not end. If anything it'll get worse. It's become a tracking mechanism which management loves. There's also a gazillion agencies out there that will push for it as that daily meeting makes it look like there's constant progress, even if most people BS their way thru half the meetings.
- maerF0x0 4y agoExcellent rebuttal of those calling for the end of Agile whilst simultaneously not know what Agile even is. My addition-- If we're going to end cargo culting, we should also end all the cargo cults of Silicon valley style startups. 1. Stop the cult of "Grind". Working more hours is not more productive for most people 2. Stop the cult of "build faster with tech debt" -- internal quality matters and costs you velocity. Those 10x engineers are 0.1x when you consider their externalities 3. Stop the lie that you'll get rich off startup options. Statistically improbable and options which expire 90 days after your employment ends are not equity or property as most people understand it. They expire/evaporate unless you shell out the exercise price, and the tax money on the gains... -- RSUs or extended exercise windows are though. 4. "We can fix it later with an order of magnitude more VC money" -- Similar to the tech debt item, a company w/ a game plan of "more VC money" is outdated and missing the change in environment, instead be profitable from very early.. ideally from your first customer. 5. "We need bespoke software because our Product is so unique." -- Nope -- use all the tools you can until you have scale, then start to build whatever is least economical to buy. 6. Doing it like Google (or other respected company). You're not google. Oh and if you survey for "Best practices" -- it's not best, it's average. Average isn't going to cut it anymore. What'd I miss from the list?
- chinaman425 4y ago[flagged]
- maerF0x0 4y agonot sure if you're ironically mocking the exact kind of answer you'd get in an "I'm so excited!" style culture. Or if you're serious... I'm not angry I'm just tired of the doublespeak by people who, for example, say you gotta take a vaccine or you're "anti-science" but then turn around and denying much of the academic information we know about software engineering practice. It's self serving cherry picking.
- cratermoon 4y agoWhile we're at it, let's talk about what Technical Debt really means. A mess is not technical debt. Ward Cunningham explains Debt Metaphor https://www.youtube.com/watch?v=pqeJFYwnkjE https://www.youtube.com/watch?v=pqeJFYwnkjE transcript at http://wiki.c2.com/?WardExplainsDebtMetaphor http://wiki.c2.com/?WardExplainsDebtMetaphor
- ravenstine 4y agoAgile, and especially SCUM, are a scam. Well intentioned, yes, but mostly serve to create an industry around a problem that often doesn't exist at all. That's not even my main objection to Agile. The worst part of these methodologies is that there's no evidence that they work. It doesn't matter whether an individual team thinks it works. Does it work for many teams? What about most teams? What for what kinds of teams does it work best? What kinds of teams does it have no impact on or a negative impact for? Nobody actually knows, and seemingly nobody is interested in studying it. Even companies themselves aren't honest about whether Agile is working for them. Burndown charts and the overall number of tickets being closed is about as far as it gets, except management inevitably gets their hands on these things and uses them as a means to extract more work from their employees. What suffers? Quality. Agile doesn't care about quality.
- randomdata 4y ago> The worst part of these methodologies is that there's no evidence that they work. What methodology do you find in Agile? It doesn't really say much. In fact, here is the Agile Manifesto in full: -- * Individuals and interactions over processes and tools * Working software over comprehensive documentation * Customer collaboration over contract negotiation * 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. -- If anything, Agile promotes not getting hung up on methodology, to just use some common sense.
- chinaman425 4y ago[flagged]
- mobjack 4y agoI am a big fan of the Agile Manifesto, but Agile has evolved to be something completely different. It became a rigid process where people debate the definition of story points rather than getting shit done.
- dijit 4y agotbh, Agile as preached and Agile as practiced is not exactly similar. I think there is even a good video describing that, from 7 years ago[0]. agile does not at all mean backlogs, or sprints, or specific tooling or even CI. Agile boils down in essence to “deliver often, do the minimum needed, prioritise prototyping”. [0]: https://youtu.be/a-BOSpxYJ9M https://youtu.be/a-BOSpxYJ9M
- notachatgptbot 4y agoI’ve seen multiple posts on HN titled along the lines of “the age of x must end” in the last couple of days. Contents are always pretty bland with no new concepts or ideas. I’m not the only one assuming this is some sort of chatgpt or similar experiment am I?
- steele 4y agoWeird how emulating TPS never includes lifetime employment. Agile is a talent attraction / retention device more than anything else these days.
- geodel 4y agoI don't think that there is any other Agile with capital 'A' that is not cargo cult.
- _def 4y ago> Instead of keeping the assembly line running no matter what and then fixing things at the end (aka “always expected to be producing and delivering, incentivized to cut corners in order to get it done”), the expectation is instead to stop-the-line when problems are encountered so as not to leak quality issues to the next stage. What is this supposed to mean in practice? Working outside of sprints?
- holoduke 4y agoI would never go back into a agile/scrum organized environment where people talk about stoey points, the meaning and contents of a retro or an issue with the title of a ticket. If i only think about it i think its pure hell to work in it. Instead we work in self organized teams. Where we have defined our own rules. Our own way or working. Ten times more productive and enjoyable.
- qalmakka 4y agoNö amount of arguments can deny that the vast majority of Agile nowadays is just a blatant MLM scheme. Some people ripped off other people selling them BS "Scrum Master" certifications and then promptly proceeded into roping management into hiring them, so that more scrum matters and agile-related jobs are created. In practice, I'm still to find a single developer that likes agile or scrum, and doesn't have to battle against the constant nagging and interruptions. Agile is all about "letting developers choose what to work on" but in practice that's a delusional fantasy, everyone has people or customers above them that do not understand the slightest thing about how coding works and that want to prioritize some things over others. For most people scrum is associated with shady figures with nonsensical diplomas that try to sell snake oil to their managers, and that's a hard reality any fan of Agile has to confront with.
- Cwizard 4y agoI’m pretty sure most of the agile hate comes from developers who have never worked in a real agile company/project. As many comments here already mention the majority of companies are just cargo culting. I’ve worked on a few agile projects and it was great. It just doesn’t work in a factory like manner, that’s the problem, it can’t really be ‘defined’. You have to get people who know what they are doing and don’t require handholding (helping each other is fine of course) and you have to give them an environment where they can work with flexibility and trust.
- midoridensha 4y agoI agree; I've had one recent job that was agile, and it was done pretty well. Neither management nor customers were overbearing, if things didn't get done on time we'd talk about why the estimate was so wrong, if things took longer than expected we'd just push them to the next sprint, etc. Overall, the whole thing was just a useful way of keeping people on-track, and aware of what their coworkers were doing, and organizing and prioritizing work tasks in a flexible manner, and providing a process to keep things that way. The stuff with Fibonacci numbers was a bit silly but it was fine; it's just a rough way of estimating the difficulty of a task (which is different from the time needed, because this varies by developer skill). It was also good for making sure that new code got reviewed and tested properly before being merged. Of course, it doesn't work well if you use it in a cargo-cult manner. It needs to be applied intelligently to what your team is doing.
- LAC-Tech 4y agoI'm not even crazy about the original manifesto.
- oxfordmale 4y agoThe author is going of his way to explain what Agile is NOT. Instead, it would have been great if he could have defined his version of Agile. Beyond the Agile manifesto, Agile is nothing. Scrum and daily stands up are not Agile, they are interpretations of the Agile Manifesto.
- borplk 4y agoJust like communism, the cult members define any and all failures of the thing as not truly being the thing.
- siva7 4y agoThat's a really good article. It gets so boring to see every week another "Agile must end" cargo cult from software developers who lack both maturity and experience to see their own flawed argumentation and who couldn't be either bothered to get a really deep understanding about software development methodologies instead of looking only for pieces to reinforce their own believes.
- erfgh 4y agoWhat the hell is Agile? I started professional software development 13 years ago and ever since I have been hearing and listening about Agile but I never found out what it is. Can someone explain?
- indrora 4y agoAgile at its core is a reducto-ad-minimum of project management, with a focus on talking to your customer first, then implementing features. Originally, Agile was a manifesto: > We are uncovering better ways of developing > software by doing it and helping others do it. > Through this work we have come to value: > > Individuals and interactions over processes and tools > Working software over comprehensive documentation > Customer collaboration over contract negotiation > 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. The idea being that teams that talk to each other are better than teams focused purely on "doing the motions" of their process, software that works is better than well documented software that doesn't, knowing what your customer needs rather than nitpicking over the details of contracts is more effective, and accepting that things will change and working accordingly produces a better product than something developed exactly to plan. The core implementation of an Agile system is one where you have regular requirements meetings, build a product that can always be shipped (for some definition of "ship"), and value a stable product over glamorous feature creep. This manifests itself as two core loops: One where small, incremental changes are made in the smaller loop, and one where larger changes are discussed and planned over time, but subject to change. Today, Agile has morphed to consume a bunch of aspects from Scrum, Extreme Programming, Lean, and Kanban. It's to the point where most people don't know the core tenants of Agile, say they're doing Agile, and then pass on this mutated version of Agile along to others who adapt it.
- piokoch 4y agoEverything that is needed to develop working software in terms of project management is described in Frederick Brooks "The Mythical Man-Month". Design software. Do incremental development. Half of the code should be automatic tests (doesn't have to be unit tests, that are often waste of time, functional test is typically more useful). Unlike many, if not most, "Agile" proponents Brooks actually took part in creation of a really robust and badass piece of software, IBM's OS/360. In addition to corporate agiles like Scrum of SAF (SAF is a true abomination, all the most stupid ideas put into one bucket, but expensive SAF certificate expires after a year and has to be repurchased, so they make a lot of money) there are also anecdotal agiles, like Basecamp "Shape Up" that probably can work if you have a lot of time, mature fashionable product that sells itself anyway and you don't have to answer to annoying customers. All of this is mostly buzzword filled bullshit. Waste of time.
- NotPavlovsDog 4y agoAgile as a commercial enterprise underwent the unsurprising journey of consultants selling a revolution (if you can't integrate into existing structures, change the structure) to selling the manager's magic pill of convincing salaried individuals to dream about making someone else successful and rich. The core principles of Agile as an idea drew heavily from cybernetics - systems dependent on discovery and adaptation benefit from effective introspection. The modern consultant agile business is about making the stakeholders that pay the bills happy. SAFe is one such agile. So don't be surprised about what agile is today. It was always meant to be just that. The people that started it made money and the people selling it now keep making money. If you want a management system that actually works for an information dependent and/or producing system, nurture an information flow that enables rapid adaptation through introspection and exchange. Except this goes against the core interests of the salaried managerial class in any mature organization. Good news for founders - disruption is faster and easier in a start-up.
- forinti 4y agoMethodologies have to start saying something about what is being built. Games, phone apps, embedded systems, etc, are all very different and we should put the specifics of each one into the guidelines of the methodology used to build them.
- twawaaay 4y agoBit late to the party... but I don't think it even can be called cargo cult. Cargo culting means imitating motions without understanding what they are supposed to achieve or why. In case of Agile, even the motions are typically not being repeated. The basic tenets of Agile are moving responsibility for improving efficiency and quality to the teams and individual contributors with the goal of speeding up improvements. Why? Because in an infinite game whoever is improving faster is correlated with better chance to stay in the game for longer. If you looked at the "motions" of truly Agile teams you would see that the management allows the team an ability to define how they work and achieve their performance and the team owns the process and is spending a significant portion of their effort towards improving it. If "Agile" (to distinguish from actual Agile) is cargo culting, it is imitating other organisations which are imitating other organisations and so on, until both the motions and the reasons are completely lost in translation. In "Agile", you will see some kind of advisor to the manager or the manager instituting "Agile" process by prescribing how teams are supposed to work with typically unspecified goal of making the organisations better (but no measurements to confirm the improvement). As a next level of perversion, they can even introduce Scaled Agile Framework which when implemented typically gives absolutely no room for teams to tailor their process to their needs and requires the team to get management approval for a smallest deviations. I have many times fought and lost battles to introduce small changes to Jira configuration. I think managers are both uninformed about what Agile is but also even if they were informed, not mature enough to let go of their compulsion to determine how their organisation is supposed to run. I think this insecurity and immaturity is what is driving "Agile" deployments. In my work with underperforming teams I try to undo as much of the "Agile" damage and distill it to the basics: agreement with the stakeholders about what Agile is and what it is, reducing ceremony to the only thing that really matters which is retrospective and working with the team to instil sense of ownership for whatever they are doing.
- Gordonjcp 4y agoIt reminds me of what someone online said about ITIL (and if you haven't had the pleasure, consider yourself lucky): It's like sex in high school. Everyone says they know all about it, everyone says they're really good at it, and everyone says they're doing loads of it all the time. No-one knows much about it. No-one is any good at it. And absolutely no-one is doing any of it, at all.
- taurath 4y agoCan we also end cargo cult interviews
- pjmlp 4y agoGood luck with that, the whole enterprise space is full of companies whose business is to sell Agile development, with the whole package that belongs to it. This is what managers care about, regardless of what is being discussed on the engineering floor about what Agile is supposed to be like in practice.