4 ms·
Agile Cult
- bitwize 3y agoAgile was and is only ever adopted by organizations because of what it promises organizational management, to wit: fine grained observability and control of the software development process. That's it. Take that away and the advantages to Agile crumble, and your boss will be back to breathing down your neck asking for estimates that are really signed-in-blood commitments. Nobody making the decisions really gives a shit about what's on the manifesto.
- AnimalMuppet 3y agoFalse. It was adopted at an organization where I worked because of what it promised management, which was greater productivity. It died because management wanted greater observability (and, I presume, control). There was an impedance mismatch (so to speak) between the agile team and upper management - management wasn't getting their GANTT and PERT charts, and couldn't figure out how to manage the agile team. "Trust us, bro, we're delivering" didn't cut it, though the agile team had a track record of delivering. > Nobody making the decisions really gives a shit about what's on the manifesto. That's probably true. But if agile is any good, shouldn't it be good for the organization, not just the programmers? Shouldn't it deliver actual value faster than other approaches? (And in fact, we did. But management just had to have their charts to be sure we were going to...)
- psunavy03 3y agoAnd here we go with an entire thread of cynical comments where people assume that the jacked-up Agile implementations they've seen at their own organizations are the only way it ever can be implemented . . . Unfortunately, doing it well requires managers willing to give up power and developers willing to take the headphones off, go talk to other human beings, and be more proactive than just "I did what I was told." Some companies/teams struggle with these things.
- harimau777 3y agoIsn't that the entire problem though? Agile fails to take into account the realities of corporate politics and human (i.e. manager) psychology?
- psunavy03 3y agoAgile, or the "Agile Cult" the author mentions? Agile merely recommends biasing in four directions: - Individuals and interactions over processes and tools - Working software over comprehensive documentation - Customer collaboration over contract negotiation - Responding to change over following a plan And also to comply with 12 principles listed here in all their 2001 internet glory: https://agilemanifesto.org/principles.html https://agilemanifesto.org/principles.html There's nothing wrong with any of that, and a lot that's quite good. Failing to take into account the realities of corporate politics and human psychology when you implement it doesn't make the idea bad. There's no cause so noble that it won't have a few incompetents following it. What's more, there's a difference between expecting someone to change at a healthy pace as opposed to RIGHT NOW, and saying that they don't need to change at all. Implementing whatever flavor of Agile requires growing pains in the same way that getting physically fit or learning a new skill does. That's healthy. A lot healthier than just sitting on the metaphorical couch with a bowl of Cheetos. Just because a bad personal trainer pushes someone to the point of injury is not evidence that exercise itself is bad.
- OldGuyInTheClub 3y agoYour bullet points may (or may not) be fine for commercial software. If you're working on anything governed by the US Federal Acquisition Regulations (FAR), they are a minefield. - Process compliance is usually baked into the contract. If the contractor stipulates to complying with a process, especially a government process, then it had better be followed and documented - Documentation is not optional. People move on, get fired, and/or die. Because the s/w works today, it may not tomorrow when MS, Redhat, or whomever push patches - "Customer collaboration over contract negotiation": Once the contract is in place, it is in place. Customers will _always_ try to add scope and eventually try to direct the individual performers. If you're Firm Fixed Price, you are dead in the water. If you are Cost Plus Fixed Fee (CPFF), you will dilute your profit when you inevitably overrun. -- Aside: CPFF means the fee is fixed at contract start. If you overrun you may get your costs but the fee stays the same. And so on. An even bigger problem is when Lean/Agile gets glommed on to hardware efforts where you can't simply issue a patch every 30 minutes and where you can't have the customer in your day-to-day shorts.
- datadrivenangel 3y ago"And no, this is not a post where I will say “corporate” agile bad or “scrum-but” bad or any other truth worn thin. On the contrary, I’m talking about the “good” Agile that the cheerful but barely experienced in software development coaches will share with you in a two-day training session. I’m talking about one of the huge pillars of modern agile - Scrum itself. My biggest problem with Agile is that it has become a cult, full of fanatics, dogmas, sermons, its own mythology, and of course the holy inquisition that fiercely fights heretics. I’m a heretic now. In this post I will say a few anti-Agile things, so you may think I have completely embraced the Dark Side, where all the Evil Managers in their suits sit, and where the looming shade of the Great and Terrible Waterfall instills fear into the hearts of the bravest developers."
- nivenhuh 3y agoI think most stressful development environments happen because a manager either isn't familiar with how software development is done (resulting in unreasonable expectations), or the manager isn't communicating expectations upwards effectively. It's important to understand when the business needs a certain capability, and that should be communicated to the development team (so that the correct scope tradeoffs can be made). Bonus points if the business can communicate the challenge they're trying to solve as opposed to the desired output. (Sometimes, you can start with a simple shell script that relieves the pressures of the business while iterating towards a more feature-rich solution.) It's also important for the business to understand that the goal is a minimum functional implementation for the capability, and that there are development quality standards that must not be sacrificed to hit a date (bad code is a liability). Also, they have to understand that the date they are communicating to the development team is a "I would like it by this date", not a deadline / guarantee that they'll have that software capability on that date. (As a consumer, I do not set deadlines on a provider in many industries.) Finally, a manager needs to understand the project health on a regular interval and communicate progress and confidence levels as the project continues. This is usually where expectation management goes wrong -- because the conversation about the work becomes metrics driven (instead of talking about the true story of what is actually happening with the work). Everyone involved needs to understand the flexibility required to develop a useful, trustworthy product -- and that the time required will vary depending on a number of factors (some knowable / mostly unknowable). As long as there is trust and expectation management between all stakeholders, a program will usually go positively (and relatively stress free). (Lessons learned from shipping enterprise software applications & running a development consultancy.)
- mavelikara 3y agoWhat are the expectation from a developer in this world? I ask because you listed a bunch of expectations from management and business. But the “system” consists of a third element too - developers! What are your expectations of them, in this idealized set up?
- nivenhuh 3y agoGood question! - Transparency about the work. (Communicate progress without being prompted. Share screenshots & be excited about what you develop!) - Don't be a hero. (If something is difficult, collaborate with the team and don't go it alone.) - Be minimal. (Development is an additive process, and it's easy to "chrome plate" a development story. Be minimal and discuss above & beyond opportunities with the team before working on them [or just create a ticket for later discussion].) - Don't compromise quality. (It's easy to want to skip tests or refactor later, but that carries invisible costs & churn during PRs.) - Refactor as you go, but don't over do it. (Nobody likes a 1000 line PR. A major refactor means large code change [risk], large review, churn on correcting the PR, long time before feature is merged, ...) - Solicit feedback when you do want to cut corners. (Explain what the cost is in a quick implementation and why it's a good idea to implement minimally at this phase. Identify ways to mitigate risk / make refactor simple later.) - Don't overwork. (Developers tend to work harder in off hours and burn themselves out. What they don't realize is that their total contributions to the team go down significantly when they overwork.) - Be honest. (In a team development setting, some folks will communicate that they're further along on a story than they actually are, with the intention of making up the development effort. This causes overwork -- and the rest of the team can pick up on the dishonesty. I would rather have a member of my team say that they're having an issue with solving a problem [or there are external life factors] than feeling like they have to go it alone.) - Ask for what you need. (Organizations can easily pull developers into meetings and monopolize their time. Push back and ask for focus blocks.) - Be candid in retrospectives. (It's the one venue where management is literally asking you what could be better. So many times, people are waiting for someone else to speak before they voice their opinions. Have a conversation with a team member before retro to validate your opinions if you are self-conscious about them.) - Be candid in 1:1s with your management. (Typical management will lose the developer perspective and rely on feedback to be able to adjust team policies. If there's no feedback, then problems fester.) -- I get that this list leans on being extroverted -- and that some folks are introverted. It's totally a vulnerable position to put your hard work / opinions out in front of a team for review. It's even more intimidating (impostor syndrome) when you're working with really smart people. A good manager will mentor their staff on how to follow through on these expectations, and will also actively work to make the team environment a safe space for constructive conversation. There's a lot more micro nuance depending on the team and business environment, but generally, I believe this is a good starting point.
- nusl 3y agoI’ve worked at a lot of places that said they do Agile but they all really do waterfall with Kanban and call it Agile. Sometimes they do retros too. If you’re someone that studied Agile and knows how it really works I think you’re in the vast minority. Admittedly I am not one of those people and haven’t a clue of what “real” Agile looks like. I can’t say that I feel like I’m missing out either. Where did the word Spike come from? How does it mean “research” (kinda)? Dunno, I’ll google that now I guess. But the word itself feels out of place if you’re not in the Agile mindset. Seems like it’s from track running terminology for a short, quick sprint. Okay. Why not just call it what it is, just research and/or planning?
- psunavy03 3y agoBecause a spike was supposed to originally represent a short, quick, narrow trip through all levels of the stack from UI to DB to figure out how to approach a given gnarly problem. Narrow and deep . . . looks like a spike.
- jokethrowaway 3y agoThat's true. Almost nobody knows the principle behind agile. And almost nobody does full scrum either. https://agilemanifesto.org/ https://agilemanifesto.org/ Read this and you'll know agile in 5m. Forget all the buzzwords. You won't know scrum or any other monstrosity call agile today, but that's not agile.
- sureglymop 3y agoThe scrum guide is also like 16 pages, pretty simple and anyone could read and understand it in 20 minutes. What's surprising to me is, these processes are actually well defined. But my suspicion is that that's not what sells. No "aspiring manager" will take the "scrum class" if it's ideas are really pretty simple and not that revolutionary and hard to understand. I have come across so many managers who have had a vague idea seemingly from a few youtube videos (or perhaps a class they took) but they seemingly never had researched in the same way software engineers e.g. read API documentation. The same is true for the waterfall model too these days though. If you fully put in the time and actually research these things as am engineer, a lot of managers will feel threatened and stop that in its tracks.