16 ms·
Agile and the long crisis of software
- gamesetmath 5y agoIt was going so well until it turned into “old white men created Agile and they don’t understand POC’s and women”. The ‘weirdos’ in the first paragraphs were primarily nerdy men. The landscape has changed tremendously since then - Agile is terrible for many things, but it does not incite racism or bias. Perhaps the only bad thing it does not do. I was hoping for a better ending to this read.
- mr90210 5y agoI am African, and I cringe hard whenever somebody refers to a group of people by their skin feature, regardless of where they come from. I personally don’t think it’s ok to refer to a person like that, it’s a rather gross oversimplification of a human being. We ought to be more sophisticated than that.
- odshoifsdhfs 5y agoNo, you don't understand (/s), now he is in the 'in group' and gets brownie points, and because he used that logic, you can't criticise him or you are a racist/something other.
- discreteevent 5y ago"The mind is the standard of the man" - Martin Luther King. (Just in case: in those days 'man' meant 'human')
- bitwize 5y agoAlso Martin Luther King: "A society that has for 300 years done something special against the Negro must now do something special for the Negro."
- deleted 5y ago[deleted]
- np- 5y agoThis is completely out of context. He said that before civil rights were realized, and Black Americans were regularly structurally discriminated against. The special thing that needed to be done was to not let things remain the status quo but to allow Black people to become full members of society.
- planarhobbit 5y agoI love it when people who have no idea about our profession start doing this race baiting bullshit. I’m really hoping (too optimistic, I know) that HN will collectively one day start flagging articles written by clueless people who spend an awful lot of words to say less than nothing. Embarrassing.
- mr90210 5y agoTalking about agile, I subscribe the ideas from Allen Holub (holub.com), especially because he doesn’t talk about a one-size fit all formula, instead he focuses in collaboration between peers, and short feedback cycles aiming to solve business challenges.
- nonstickcoating 5y agoI do not think the article argues that Agile somehow incites racism and bias, it argues that it doesn't account for them while it should.
- asplake 5y agoAgile's crisis (which is real) is because despite the generativity of the manifesto, the frameworks it spawned largely ignore how change happens in a healthy and sustainable way. It is deeply ironic how much the Agile industry leans into 1990's models of change (solution-driven, imposed, etc). That explains an awful lot. When people think that it's enough that they're right, bad things happen. Agile doesn't actually need a theory of society to understand that, just a little humility.
- nradov 5y agoThe Scaled Agile Framework (SAFe) includes review and change cycles driven by teams at the grass roots level. Of course some organizations skip that part, but you can't blame agile frameworks for management choices.
- asplake 5y agoEvery framework has some kind of inspect-and-adapt thing going, nothing special about SAFe in that regard. The bigger question is how the organisation is supposed to get from zero (not using the framework) to the point where it is working at every scale, necessary if claims of business agility etc are to be realised. If the answer is a rollout project, then the dissonance there (not to mention the pain) should not be underestimated.
- nradov 5y agoOrganizations starting from zero typically hire experienced trainers and consultants to guide them through the initial implementation and then a few cycles. That's expensive, but cheaper than failing. Of course if senior leadership isn't truly committed then it still won't work, but that's not the fault of the framework.
- meerita 5y agoIt's the gender and race wars agenda. Everything has to have a gender/race problem.
- pif 5y agoNo, it's short-sighted people from US not realising that the internet is broader than the US. Please, if you are writing an US-centric article, state it in the title. Example: "Agile and the Long Crisis of Software in the USA".
- tjpnz 5y agoHaving spent the better part of a decade working with agile teams in Asia I too find such statements to be decidedly off. My Scrum masters have all been POC and mostly female.
- meerita 5y agoIndeed. But I remember the race/gender thing was inexistent, nobody cared if a programming language is race biased or gender biased. Those are first-world woke problems. Solving those problems will not solve the entire topic. People focus more on external issues with 0 correlation instead of the main topic. It's logic that we need to apply to solve problems, not feelings.
- piva00 5y agoAgile as per the Agile Manifesto isn't bad. At all. I saw the transition of the industry from a complete waterfall process to the overhyping of agile, the pushback and now the land where agile as per the manifesto is more-or-less a given. The old ways were so much worse... The bad sprouts from agile are the multitude of processes and bullshit methodologies that tried to ride the hype and create "The Agile Way". Scrum and others are a side-effect of this and I'm very glad to see Scrum being shunned for the past 4-6 years and instead engineers being attracted towards much more lightweight processes. The problem with agile is that it only works when people had experiences, bad and good, and a team can tailor how their agile process should look like given their constraints. Throwing a bunch of juniors under an agile methodology and telling them what's right or not only creates friction and useless rituals, you need experienced people (PMs, EMs and at least one engineer) to cut the bullshit and stick to the points that matter: collaboration, communication, re-assessment of priorities, etc.
- pydry 5y agoIt's vague as hell though. Everybody from the agile consultants to the CEO down to the lowliest engineer projected their desires and intrinsic meaning on to the agile manifesto. If you ask 10 people what agile "really" means you'll get 10 different answers, many quite incompatible with each other.
- cestith 5y agoAgile focuses on the continuous improvement of not just the software, but the process. They tried to be specifically not too verbose, as dedication to one size and shape of process that does not fit all is precisely what they were against. Agile can be thought of as a meta-process. It's an attitude and a process for improving your process. Think kaizen for your software development team. It's about the tight feedback loop about what's working, what's not working, and what can be improved. Beyond that, 10 people might find that the processes they've refined from Agile really do differ. That might be because of differing (and broken) application of Agile itself, which is a common claim. It might be, though, that continuous improvement of process has lead different teams in different directions that function well or well enough for those teams.
- wodenokoto 5y agoI felt like the justification for saying that agile was not good for underrepresented groups came very late, but it is there and it actually is not a bad argument. > We’ve long known that eliminating bureaucracy, hierarchy, and documentation feels great, until you’re the person who needs rules for protection. I think the article eventually makes good arguments for this, at least if you are willing to say that code review and pair programming are things that spring out of the spirit of the manifesto. Basically they author is claiming that the goal of the agile manifesto is to remove oversight from developers so that they can focus on "the project". The downside is that you are losing oversight of bad behaviour, which gives space for work-place bullying. (and the other downside argued is that developers, who are also stakeholders, do not have a voice in questioning the utility of the project overall).
- r_c_a_d 5y agoI never read it as "removing oversight", more like "removing excessive admin". And it explicitly says to value "individuals and interactions". Part of that means you need a facilitator in retrospectives who can detect conflicts between individuals which may not be being addressed in that forum - and ensure that they are addressed elsewhere.
- richliss 5y ago95% of articles on Agile are incorrect and this is no different. 1. Mike (Miguel) Beedle was latino. 2. "Al Tenhundfeld, one of the manifesto’s authors" - NOPE. I could go on but what's the point. If you want to learn about agile I recommend reading Alistair Cockburn, James Coplien and Craig Larman. They're old school and know the history of this stuff amazingly well.
- bitwize 5y agoWe are in an era of mythologizing that old white men are at the root of all problems, so thinkpieces like this have to mention old white men as a matter of course. That said, however, the article is correct to assert that Agile, as implemented in real organizations, addresses the corporation's needs and only those needs. Otherwise, it wouldn't have been adopted at all, but dismissed as the snivelings of whiny insubordinate programmers who forgot just who signs the checks.
- throwaway6532 5y ago>We are in an era of mythologizing that old white men are at the root of all problems, so thinkpieces like this have to mention old white men as a matter of course. That we've gotten to this point must also be old white men's fault.
- bitwize 5y agoWhen you boil it down, it probably is. I don't believe for a moment that the reason why Occupy was scuppered by social justice stuff has nothing to do with the fact that the sort of person who attends the WEF was very threatened by Occupy.
- deleted 5y ago[deleted]
- eesmith 5y agoOf the 9 previous times this was posted this month, here are the five with comments, and either a pull quote or my summary of the discussion. 1 comment at https://news.ycombinator.com/item?id=31299834 https://news.ycombinator.com/item?id=31299834 ("The way it is described in the article highlights a subtle problem - the ability to change requirements as you go", followed by a discussion of that tangent.) 1 comment at https://news.ycombinator.com/item?id=31145030 https://news.ycombinator.com/item?id=31145030 ("doesn't match my understanding of the history") 2 comments at https://news.ycombinator.com/item?id=30988096 https://news.ycombinator.com/item?id=30988096 (both concerning the high number of re-posts) 1 comment at https://news.ycombinator.com/item?id=30967432 https://news.ycombinator.com/item?id=30967432 ("Neat historical overview followed by bizzare conclusions") 1 comment at https://news.ycombinator.com/item?id=30963468 https://news.ycombinator.com/item?id=30963468 ("Sigh. Another article on "Agile" that makes it read like "SCRUM" == Agile (Sprint, Stand-Up are Scrum terms, not Agile).")
- drewcoo 5y agoSo you're saying we favor frequent submissions over in-depth conversations? Hey - that's not in the manifesto!
- ellen364 5y agoInteresting idea from the article: that Agile methods “compartmentalize features” and risk creating “an assembly line in which no one, at any point, takes full responsibility for what the team has created”. The author meant responsibility for the product’s impact on society, I think, but it could also apply to responsibility for technical decisions.
- Jensson 5y agoSounds like ouija board driven design.
- mnd999 5y agoI haven't read the article because TLDR; but agile, particularly in it's earlier incarnations like XP is the least bad methodology I've used for most of the problems I've worked on in non-tech firms and small tech firms. I never worked in a FAANG or a Microsoft so at that scale things may be different. The usual rules apply, there is no silver bullet, nothing is all bad. Pick the most sensible process for the job and adapt as necessary.
- black_13 5y ago
- mikewarot 5y agoTLDR Agile was a response to management practices that didn't respect the profession of software development. Management didn't get the joke when the Waterfall model was used to show exactly what was wrong with those management practices. Agile was a response to the increasing unrealistic expectations of management, and the widespread (and highly predictable) failure of the Waterfall model. Somewhere along the line, women were pushed out of the mainstream of programming, and became a minority. The men who started the Agile movement were a bit creepy, and those in charge now have acknowledged past sins, at least somewhat. Consultants and Trade shows have commodified the dissent that was Agile programming, slowly turning it insane by forcing it to be a Waterfall again. As always, people who make powerful tools share some responsibility of how they are used.
- Dave3of5 5y agoJust as a note to the author what you saw the engineers do was SCRUM not agile. Most argue that SCRUM is agile I'm not 100% sure of that. SCRUM was a framework that one of the original agile proponents built to make money off developers. It gained popularity not from engineers but from project managers and the like which meant suddenly every project started to use SCRUM. The main reason was that they sold a course which gave a certificate and if there something that a project manager like more than micromanaging it's certification.
- dgb23 5y agoWhy do you think that is?
- sirmarksalot 5y agoI think the Agile Manifesto is an exercise in subversively asking management for a very reasonable-sounding thing that is completely impossible: autonomy. Every line poses a threat to a well-known corporate best practice, and the natural reaction is to co-opt the message and bring the items in the left column back into the right column. In the case of Scrum, it's that "individuals and interactions over tools and processes" line. Scrum did start out as a popular Agile methodology among developers, but because it was the most prescriptive and process-oriented of the methodologies, it got adopted and twisted by management and turned into a tool to reassert authority. Now it reasserts that tools and processes are, in fact, more important than individuals and interactions, but this time with the "Agile" label. I'd love to try working on a Scrum project that doesn't rely on JIRA. Just notes on a corkboard with a quick "need anything?" conversation in the morning.
- azangru 5y ago> I'd love to try working on a Scrum project that doesn't rely on JIRA. Just notes on a corkboard with a quick "need anything?" conversation in the morning. Don't you find value in keeping the digital record of the work? For example, if you want to keep track of dependencies that a given task has; or want to get back to the description of a given piece of product that was captured in a ticket (a user story, links to designs, references to other documents, etc.) after some time has passed? Notes on a corkboard are transient; tickets in the Jira are permanent. Isn't there value in that? BTW, why do people dislike Jira so much? Apart from it being slow or not allowing assignment of tickets to more than one person?
- luciusdomitius 5y ago"long-haired weirdos who hung around university labs after hours" How is someone's appearance relevat to the management technique? I've never seen it as a criteria. https://www.linkedin.com/in/miriamposner/ https://www.linkedin.com/in/miriamposner/ - OK, now it is clear - the author has "immense" experience in both management and software engineering and that's why she tries to describe the situation using the knowledge she has available to herself. What a miserable failure though. The real question is why people with actual experience in both would read such an article...
- msh 5y agoThe whole quote makes your clip sound different: Some of the most advanced programming, as Clive Thompson notes in his 2019 book Coders, was pushed forward by long-haired weirdos who hung around university labs after hours, hackers who considered themselves as much artisans as logicians. And it was not said in relation to agile.
- luciusdomitius 5y agoWhat does Clive Thompson have to do with software engineering excellence? Could you send me his github. Judging people by their appearance is extremely superficial and guaranteed to bring you tons of problems in any more complex context.
- msh 5y agoDid you actually read the article? What was the judgement in the quote?
- kcplate 5y ago> Could you send me his github. Oh is this is the new measure of success? I better get one then. Used to be we just pointed to the successful products and companies we created, but I guess we are measuring folks now on mostly pointless pet projects that no one is using?
- jillesvangurp 5y agoThe best characterization of agile is that it's an adjective, not a noun. It's why it has become so completely meaningless. Because everybody wants to do things with at least some pretense of agility. And often it's the people proclaiming their agility the most that you need to scrutinize the hardest when it comes to their proclaimed agility. As soon as you start talking about agile as if it is a noun, you are effectively bullshitting. It's not a thing (literally). It never was. The software crisis, is the notion that software is hard to produce on a schedule. People indeed noticed that early on before there even were compilers. Hidden in that notion is a thing that is problematic with software. In order to even have a timeline for "it" to be delivered, you'd have to specify what "it" is. That's a notion that is quite hard. Often such specifications are a combination of wrong, incomplete, and not very useful. And it leads you to an engineering mentality where specifying the thing up front in excruciating detail becomes a mandatory thing. If there's one thing we can learn from the last seven decades of software engineering it is that that is indeed extremely hard and probably futile with the exception of a few domains where anything less is just not acceptable. The notion of waterfall, which was popular with people that did not read the original paper by Royce (he does not mention the word waterfall but is often blamed for inventing the methodology) in full. Waterfall is the notion of specifying requirements upfront, designing the software, and then implementing it. Royce actually called out in his paper that going through this process multiple times yields better results. So, the key paper on waterfall actually suggests we might want to "iterate". Still worth a read more than 50 years later. Among all the agile nonsense, this is actually a good paper. But you have to read it in context. You might think of writing software as the actual process of specifying what the software does. The best specification is the source code you produce. It's executable and complete. Whatever it specifies, it does. You might be unhappy with the level of detail but it is a specification. The contribution of the agile manifesto was acknowledging that reality and the notion that it is more productive to talk about modifying this specification than to come up with some meta specification. You have to build in some moments of reflection and adjustment. So most of the time you are actually specifying changes relative to the existing system rather than the entire system. The only moment that is not true is when you have not written any software yet. Specifying software changes is what an issue tracker is used for. Bugzilla was one of the first widely used ones and it launched a few years before the agile manifesto got penned down. The insight at the time was a that a good issue tracker (and maybe a wiki) were really all the tools you needed to orchestrate software development. All the rest (scrum, kanban, sprints, planning/estimation meetings, velocity, etc.) was just retrofitted around that notion. That's it. If you can wrap your head around iterating, you are agile, just like everybody else. The smallest possible iteration is: write an issue, write some code, create a pull request, wait for someone to merge it. Pull requests are great. Most modern software development features multiple pull requests being worked on independent from each other at the same time. Of course the notion of concurrent iterations that aren't coordinated centrally makes the heads of most scrum proponents explode. There's a lot of great software that gets produced by large organizations, or even distributed organizations (like open source projects), seemingly without a lot of ceremony (scrum or otherwise). Open source is basically software development stripped to its bare essentials. There are no estimation sessions. No sprint plannings. No sprints even. Work happens concurrently with very little central coordination. All there is is an issue tracker, a code repository and exclusive access for those allowed to merge pull requests. Some great software gets produced that way. And I don't think it's accidental either. Some projects seem very consistent with maintaining a predictable frequency of releasing, high quality standards, etc. In fact they put many corporate "agile" teams to shame. Mediocrity is the norm, not the exception in our industry. The software crisis still exists; but mostly in supposedly agile teams still insisting on disguising waterfall as agile. The louder they talk about being agile, the less they generally are.
- dgb23 5y ago> If a company sets a goal of boosting user engagement, Agile is designed to get developers working single-mindedly toward that goal—not arguing with managers about whether, for example, it’s a good idea to show people content that inflames their prejudices. Pretty sure the author mixes things up in an attempt to create a narrative.
- azangru 5y agoGood point. In the pre-agile world, developers would work just as single-mindedly toward a goal, prodded by a manager; only after lots of time has been spent on coming up with a plan for the product.
- langsoul-com 5y agoAgile, these days, seems more like waterfall every 2 weeks.
- dazzawazza 5y agoThe tears laughter, pain and despair in the retro are the waterfall.
- baud147258 5y agoseems like our situation. Though the head honchos have also imposed SAFE (scaled "agile" framework), so we get an even bigger waterfall with all teams together every 4 months, which takes each time two weeks (one week preparation + one week of meetings)
- Jtsummers 5y agoWaterfall (as a bad management practice, which sadly is still practiced) is bad when you're trying to run a large scale project and don't have feedback (because Waterfall does not include feedback). Waterfall-the-real-thing has no feedback loops built-in or severely delayed feedback (months of dev followed by months of testing, I'm watching my colleagues across the hall repeat this mistake right now, they "finished" dev last week but it won't be installed for the testers until the fall and they've started developing their next version of the system...morons). If you actually have biweekly feedback, you don't have Waterfall. Planning and then executing on that plan in short increments is reasonable. Planning and executing on that plan over months or years, stupidity and insanity.
- alkonaut 5y agoAgile (Scrum rather, but this article appears to be about implementing agile through scrum) trades one set of problems of software development, for another set of problems. That needs to be understood I think. Some times when agile is treated like dogma and religion this somehow gets lost. It's a tradeoff. It's popular because this new set of problems is deemed to be a better set of problems to have than almost all other sets of problems you'll end up with. Switch to waterfall, and you'll have problems with that. Try whatever process, and there will be a set of problems that comes from it. Scrum is a flawed process, but there are many flawed processes. A lot of scrum-haters (understandably) argue against scrum, but what I'm missing is the presentation of the alternatives. We are going to be miserable and stuck doing scrum for the coming century unless we can formulate and demonstrate good alternatives. And if we don't want the processes to be upper-management centric, we better formulate the alternative as developers. The places where I have seen scrum function well (teams delivering features without burnout, without losing grip of the big picture because of constant micro-development etc.) are in teams that are high performing and highly functioning. But of course those teams would have been well functioning and productive with any process. The allure of scrum (in my opinion) is that it makes teams that would likely have delivered nothing, deliver something, or at least not waste time building the wrong thing. It's a way for management to increase the transparency and lower the risk of software development with poor software developers and/or bad teams. And that, to be honest, isn't something to be scoffed at. Throwing a poor process onto a bad team means you'll get miserable developers and risk having nothing produced. Agile means miserable developers and hopefully some transparency too. Not great, not terrible.
- Juliate 5y ago> It's a way for management to increase the transparency and lower the risk of software development with poor software developers and/or bad teams. So, it's kind of an "observability tool for teams' production process management"? (to reframe it in a more contemporary fashion) Edit: I guess we're headed to having pulse, blood pressure, VOmax, weight, daily exercise and so... metrics also displayed along mood and burndown charts. :p
- alkonaut 5y ago
- ilaksh 5y agoThe manifesto quote was accurate I believe but ascribing all of the management BS and everything else to "agile" was ridiculous. The really successful software projects I have been involved with had very reasonable requirements. In that they was not a long list of them and the core problems had plenty of time allocated. That's the first key in my mind. Limit the scope. Overall. Another thing is to close feedback loops in terms of making sure that there are actually users using releases. The number one biggest thing that has helped me is to avoid having places for managers or users to add an infinite list of features they want. I usually only need one or two things to work on every 3-5 days. We discuss every thing directly in text (or sometimes voice) chat based on the users testing the working application as it progresses. I think this is also best for small teams, although recently I have done mainly solo projects. I know one of the ideas with feature/issue trackers is that there are too many things to keep tabs on without them. But it seems like for a lot of projects, having the tracker means people fail to communicate directly when necessary, create busywork, and do not focus on priorities enough. If there is so much stuff going on that it actually can't fit in the chat room then maybe that's too much stuff. Obviously things are going to be different for a large team handling something really extensive like Google Chrome, which is actually a full overlay operating system.
- rswail 5y agoOK, here's my take, based on 30 years of being a programmer and "manager" and "architect" and other position buzzwords. I hate the title software "engineer" because engineering is a set of practices and processes that software creation doesn't come close to complying with. The primary problem is the feature backlog. It's always been that, whether it was called the "Requirements" or the "Functional Requirements" or whatever. Working out what the product of the effort has to do is hard. It involves understanding the actual end users (not the managers of the process/product), the process/product itself, and the context and environment in which it will operate. The stakeholders are multiple and on multiple levels. There are managers and auditors that need visibility of the ongoing operations, there are users and consumers that need the actual input or output. I've never met a "Product Owner" that actually understands the product they are building or where and how it is expected to be deployed and operate. They rarely filter out unnecessary or dangerous "features", but just add them into the overall bucket without knowing where to draw the boundaries. The "solution" is multi-faceted, but it needs to be directed at this area. Domain Driven Design is one approach, actually engaging with the actual end users is vital. Sometimes, ignoring a manager's desire (particularly for "dashboards" and "reports") is very important to keeping the feature backlog manageable. Understanding the context/environment is also vital. Does this product deal with individual's personal information? How does SOC affect it? Is the process required to be auditable? If it is, what evidence is required for the auditors? None of this is "software" per se or even "programming", or, even worse, "engineering". It's process and product and understanding what is being built.
- spaetzleesser 5y agoI agree about product owners. I have never seen one that could really guide a project from start to finish. They either don’t understand the tech sufficiently, or they don’t understand the business case or they aren’t engaged enough.
- sophrocyne 5y agoUnderstanding the tech sufficiently and effectively rallying the team around the actual business/user justification for work are literally the job of a product manager who owns tech product development. While they may not be common, actual product managers do exist. There are a lot of incompetent ones, to be sure, but there are also a number of incompetent engineers.
- smitty1e 5y ago> The manifesto’s authors may have looked like textbook engineers, in button-downs with cell-phone holsters, but “a bigger group of organizational anarchists would be hard to find,” according to Jim Highsmith. The word "anarchists" fits in its purest sense of tossing the org chart. Yet its common meaning of "bomb thrower" hardly applies. I typically describe Agile as "A small, stable cadre of ninjas getting it done." Projects wind up with too much scope, a revolving-door staff, and a dearth of wizards to cut through the technical thicket. The discussion of "tech debt vs. 'green field' projects" minimizes the threat of legacy code/data to any agile effort. We need to talk about a "software archaeologist" specialty where one tries to plow through a mound of garbage left by the predecessors and seeks to figure out what prescriptions their therapists had written for them.
- throwaway6532 5y ago>We need to talk about a "software archaeologist" specialty where one tries to plow through a mound of garbage left by the predecessors and seeks to figure out what prescriptions their therapists had written for them Reminds me of one of my favorite quotes about software/computer systems - "we build our computer systems like we build our cities - over time, without a plan, on top of ruins."
- jk20 5y ago
- taylodl 5y agoI've been developing software for 40 years and here's my unsolicited observations: - Projects always take longer than anyone expects, even when accounting for projects taking longer than anyone expects (Hofstadter's Law) - The project architecture will reflect the organizational structure of the entity creating the software (Conway's Law) - The above two points are often presented as jokes but they are not, they're both actually true - You cannot force two people who do not like one another to pair program - Pair programming should never be forced on developers, let developers decide when to pair and whom to pair with - this is the autonomy developers seek - Code reviews are a waste of time and present a great opportunity to destroy team morale - Software development attracts a lot of assholes and prima donnas who all believe they are the fabled 10x developer - It is just as important to understand the why of a feature as it is to understand the what - developers need to understand why a feature is relevant and what problem it's solving for users to be able to best implement it - Invest in automated unit testing, application build, packaging, configuration and deployment. This is your best defense against Hofstadter's Law. - Some teams have a knack for failure regardless of the software development methodology being utilized. The same is true for application frameworks and development languages. - Some teams have a knack for success regardless of the software development methodology being utilized. They can also use the "bad" application frameworks and development languages and still be successful. - Mutual respect and everyone pulling their weight are the best predictors of a team's success - Just because someone isn't working out well on one team doesn't mean they won't excel on another team. Some people will excel regardless of the team they're placed on. There are also a few, very few, who can't seem to excel anywhere. - Some people aren't cut out for development and since 1960 we've been trying to figure out who those people are and dissuade them from entering the profession - all to no avail. This is a sink or swim profession and it's tragic to watch people sink - especially when you can't put into words why they're sinking and how to start swimming. - Outsiders believe developers are anti-social and don't realize modern development is a team sport. The best predictor of success is how well you were able to play team sports. If you always had lots of problems with your team mates then you'll probably have lots of problems with the members of your development team. Of course this isn't 100% accurate, but it's a good predictor. Those playing well in team sports, play in bands, or have been involved in dramatic productions tend to work well. Basically any activity having a group of people work together towards a common goal. Loners do not work well on development teams - they find success on skunk work projects. - Finally, management is key. If you fundamentally disagree with your management then it's time to move on. There's no need to trash the management when you leave, all you need to say is you don't feel you're aligned with their goals and priorities. Some people may like the management, others may not. Don't take it personally.
- TameAntelope 5y agoOkay, so what's the alternative? I read most of this article and scanned the rest, but could not find any proposal. Should we just stop developing software? Should we go back to Waterfall? I know every person reading this could write a dozen pages full of suggestions for how to run a software team, but I really wish the author herself had spent some time suggesting what software engineers should be doing instead of "agile", because that, to me, would be infinitely more interesting.
- lbriner 5y agoSimilar to you. There were several hints that the author didn't really understand software. The problem with waterfall wasn't that you had to do tasks in order, it was that you needed to know mostly everything in advance to get rid of issues at design time so they didn't bite you during coding. Also, the rumblings of agile don't really point to anything to do with agile fundamentally, just the fact that people don't quite understand it or that management doesn't wholeheartedly embrace the mess. "Agile meant that the team didn't really know what they were producing" - that is a Product Owner issue 100%. So yeah, nothing's perfect but it's probably the least worse of the options we have!
- chris11 5y ago> Should we go back to Waterfall? Waterfall seems like a strawman to me. Has the tech industry ever used it? The first reference I could find for it was back in the 70s as what not to do. I don't think waterfall should be used as a defense to scrum. As for alternatives, you can start with giving engineering teams autonomy and ownership of their work. Gergely Orosz has a good article on project management in tech. http://www-scf.usc.edu/~csci201/lectures/Lecture11/royce1970.pdf http://www-scf.usc.edu/~csci201/lectures/Lecture11/royce1970... https://newsletter.pragmaticengineer.com/p/project-management-in-tech https://newsletter.pragmaticengineer.com/p/project-managemen...
- TameAntelope 5y agoEvery time you have a "Gather Requirements/"Design"/"Develop"/"Test"/"Deploy" set of stages, you're using waterfall. Note the absence of "collect feedback from customers". Waterfall is in no way a "strawman", it's very real, and many shops who claim to be "agile" are still using it today, not to mention the near-ubiquity of its presence in software shops for years prior to agile taking over.
- Xophmeister 5y agoMoreover, daily standups, billed as lightweight, low key check-ins, have become, for some workers, exercises in surveillance. Particularly when work is decomposed into small parts, workers feel an obligation to enumerate every task they’ve accomplished. There’s also pressure for every worker to justify their worth; they are, after all, employees, who need to be perceived as earning their salaries. This is a great summary about how I feel about "agile": it's patronising and anxiety inducing. The degree to which is a function of the technical and social abilities of whoever's calling the shots -- the PM, SCRUM master, whatever -- but, of course, their steering is necessary, regardless. Leaders with strong technical chops and high emotional intelligence exist, but are rare, I think. Similarly, this is why I don't believe that a fully egalitarian group of engineers would work, either: All skill and no direction doth not a project make. Besides, true egalitarianism doesn't really exist. Some will be stronger than others; some will have weaknesses that are complemented by colleagues (hence the value of diversity); some will be brazen, while others shy. Inevitably, a de facto leader will emerge. In my experience, often the loudest, rather than the most effective. Building complex software is a social problem more than a technical one.
- andrei_says_ 5y agoIn his talk "Agile is Dead", Dave Thomas (one of the creators of the Agile Manifesto) speaks about how distorted and perverted the manifesto's intentions have been by the "Agile" industry. Striving to be agile, flexible, adaptable is a very valid and useful principle. "Agile" as a noun, the cult-ish process-training-industrial-complex is not at all agile. Link to the part where he recalls the creation of the Manifesto https://youtu.be/a-BOSpxYJ9M?t=384 https://youtu.be/a-BOSpxYJ9M?t=384 It is immediately followed by the difference between agile (adjective) and Agile (noun). Agile IMO has been perverted by business and middle management to facilitate bean-counting.
- throwaway_1928 5y agoStandups are the new timesheets: a humiliating exercise in micromanagement.
- pydry 5y agoThis quite accurately characterizes the marxist concept of alienation. I think it's essentially just the default state of working for a business. Any business.
- fnordpiglet 5y agoI grew up in the industry during the 90’s in the Bay Area. What we considered agile is nothing like agile of today. The process people wormed their way in and made it super dorky and prescriptive. As a leader now I only encourage agile in my most junior or dysfunctional team. In my high functioning teams I guide them towards the less prescriptive more “agile” method of my youth, which was very heavy in the emphasis of you almost certainly know what’s next so do it and call together a standup when you’re blocked. I’d note that more powerful than agile is the trend towards asynchronous work and planning. Keeping a chat as an asynchronous standup where you daily post your thoughts on work and respond to others is a huge boon and completely replaces “stand ups,” which only really work in fully collocated teams. Every company I’ve worked at had folks all over the world working together, and trying to do a traditional agile standup at a fixed time is brutal on at least someone.
- lamontcg 5y agoI think the problem isn't really what is being done to manage software devs, but that managers are trying to squeeze more productivity out of software teams which are insufficiently staffed and where higher level strategy is bad and the teams are setup to fail. And largely the "poorly performing" software dev teams are just a symptom of the problem and you can't rub any level of management onto the team in order to fix it. What I'd like to see is a methodology which produced an objective measure of how overloaded a software dev team was and which could be used to justify an increased headcount. I've never actually witnessed that come out of one of these processes.
- nradov 5y agoWhat does overloaded even mean? An agile program team has a certain velocity, and will work on backlog items in order of priority. The business always has the option to expand the team in order to increase velocity (perhaps with some diminishing returns). But if the business is short of capital, or the whole program isn't very valuable, then it is often preferable to just let the backlog grow.
- dasil003 5y agoYour first paragraph rings true, but I have to disagree that the second is the solution. I’ve seen engineering management play this game to justify headcount without acknowledging the strategic or product definition problems and it just leads to more chaos and pressure on the team. If engineering doesn’t have both a voice at the leadership level (for whatever scope is in question) and sufficient biz/product chops to find the right 80/20 path and team/ownership structure then headcount is just more grist for the failed project mill.
- cestith 5y agoOne of the problems people are having is that so much is said against Waterfall instead of just in favor of Agile or its spinoffs. People emphasize that everything to do with Waterfall is bad, and generalize from large, detailed, inflexible architecture with no feedback loops being bad. They often end up, repeated by people trained to be Scrum Masters or some other management or administrative role who are not developers themselves, hearing about all preplanning being bad and evoking waterfall. I've been told that gating one story behind another is waterfall. I've been told that having a design story is waterfall. I've been told that architecture documents that are eligible to be revised as the system is built but created before all the code is in place are waterfall. This sort of backlash taken to heart means that anything larger than a developer can do in two weeks is infeasible. This often happens when the team building the software is not considered among the stakeholders of the team's output. There's a sharp focus on shippable improvements. Well, to me a plugin system is a shippable improvement even if there's no plugins for it yet. A data flow diagram from this week people can use to determine which parts to build next week is an improvement. This isn't a multi-year pre-planned development schedule. This is just having some idea how to integrate the software.
- xkcd-sucks 5y agoI get the criticisms of "waterfall" style development, but lack of any careful thought or specification spanning a whole project leads to really terrible contracts and projects as some people (especially Enterprise) use "agile" == "nimble" == "license to rug-pull project scope" when there is significant inertia, and occasionally sunk cost, in these scope changes. Case in point, I'm working in an engineering capacity with a "Big Mean Secret" pharma company on a contract that is essentially "Client will work with Vendor in an agile manner to <do something vague which could encompass everything or nothing>". The company I work for is nominally a "product" company, not a "services" company, and the contract specifies fixed payment terms and timeframe. This morning, one of my teams finished implementing some stuff that was a good amount of effort, several moving parts, etc. It was explicitly called out as top priority, and its progress has been tracked by both parties over the past weeks in a shared Jira board. A few hours later in a biweekly update meeting with said client, we mentioned having finished the feature. The client's project manager responded that actually the person who cared about that feature left the company, so it is no longer in scope. Then they erased it from the project tracking record, and in the same breath complained that so little progress had been made against the other objectives. And a million other little papercuts like that. It seems that "agile" style process is best confined to small / internal teams re: the "how", but the high level "what" requires comprehensive elucidation from the beginning.
- michael1999 5y agoHow would an upfront contract have changed that outcome? Wouldn't that now-absent person have demanded the same work in the up-front plan? Or is your concern being able to bill for that work?
- xkcd-sucks 5y agoYes, broadly speaking the concern is about being able to bill for that work. I realize that this is more an issue of terribly worded contracts, but "agile" expectations seem to encourage these.
- michael1999 5y ago
- RayFrankenstein 5y ago“Agile In Their Own Words”. A collection of negative social media comments regarding Agile. https://github.com/rayfrankenstein/AITOW/blob/master/README.md https://github.com/rayfrankenstein/AITOW/blob/master/README....
- magic_hamster 5y agoIn the profession built on designing the right solution for a business problem, it surprises me sometimes that businesses or colleagues consider one methodology (like Agile) to be a one-size-fits-all for software development projects. There is a rule in the world: no single solution can be applied to all problems alike. One-size-fits-all is always, always a lie, no exceptions. A software project is a problem that needs to be solved according to its needs. The skills required, the communication, infrastructure and metrics always differ. A good manager will never fully subscribe to any methodology, but instead will be truly "agile", or actually flexible, drawing inspiration from different methodologies where it's needed, knowing their team very well, and recognizing what's needed for their team to get the job done in the best way possible.
- gadders 5y ago>> I began to explore the history of Agile. What I discovered was a long-running wrestling match between what managers want software development to be and what it really is For "managers", substitute "customers". It's the people paying that want to know the cost up front as much as possible and when things will be ready. The managers are just trying to hold everyone to that (as much as is possible).
- specialist 5y agoThe peanut gallery reacting to these agile rants always contrast it with "waterfall", as if those two forms of dysfunction are the only two possibilities. I must live in a sci-fi horror movie/simulation. Where I'm the only person who remembers actual mature proven repeatable project management methodologies. Like critical path, joint application development, and a dozen others. Whenever I mention this alternate reality, I'm dismissed as a lunatic. Hello? Does anyone see me? Does anyone else remember Peter Drucker, PMI, and shipping software?