13 ms·
He's not wrong. Having been involved in the Agile movement since before the term Agile was coined, I think of Scrum as the least interesting of Agile processes,
by wpietri 7y ago
He's not wrong. Having been involved in the Agile movement since before the term Agile was coined, I think of Scrum as the least interesting of Agile processes, but also the most successful in terms of adoption.
I used to think that was a contradiction. Now I think it's almost inevitable. I wrote more about it elsewhere [1], but the basic deal is that most companies have other priorities than being effective, so the processes that dominate will reflect those priorities.
On average, the first priority of managers and execs is maintaining the power structures that make them a big deal. But true Agile processes are about empowering teams to self-organize around serving users. Ergo, Sturgeon's Law [2] applies here too: 90% of company software process is crap.
I think reason why Scrum in specific won out is that it combined a process framework unthreatening to executives with the multilevel marketing scheme of Scrum certification. Executives got to keep doing what they were doing, the workers got a "didn't stop breathing" certificate, and coaches got paid. Win, win, win!
[1] http://williampietri.com/writing/2011/agiles-second-chasm-and-how-we-fell-in/ http://williampietri.com/writing/2011/agiles-second-chasm-an...
[2] https://en.wikipedia.org/wiki/Sturgeon%27s_law https://en.wikipedia.org/wiki/Sturgeon%27s_law
- abraae 7y agoScrum won out IMO because it's an awesome word and conjures up subliminal images of brute force pushing obstacles out of the way, bringing success to the team. Execs can relate to it without even knowing what it is.
- patothon 7y agoI actually think scrum won because of its multiple rituals that allowed most of middle managers and project managers to keep their job by recycling it.
- mlthoughts2018 7y agoI think it won out because the number one thing any kind of project management framework has to provide is ambiguous blame-avoiding fungibility to management. If a framework does not offer that, managers will politically subvert the policy-making process to rule out that framework. It’s the same reason why demonstrably value-additive, cost-effective prediction markets are rejected by managers despite evidence in their favor: it removes their ability to create ambiguous Dutch books out of different project deliverables and resort to exploiting subjective psychological biases of superiors to win money & status increases. Anything that holds them accountable to the actual measured result status of a deliverable can’t be tolerated. Scrum is just the by-product of corporate status-seeking evolutionary war games against in-house scientific thinking.
- chungleong 7y agoScrum won out because it's basically feudalism. It's great for those in the upper echelon.
- tamrix 7y agoScrum won because in reality not everyone is a wizz bang developer like your guys so make yourself out to be.
- Melchizedek 7y agoScrum (and other methods that try in vain to make developers replaceable cogs) won because it enabled bad developers to hide among the good ones, and avoid personal responsibility.
- goatinaboat 7y agoWhen I hear the word scrum I am always reminded that my school stopped playing Rugby because a kid in the next town got his back broken, in a scrum. So from then on we played football (soccer) in Rugby kit, until eventually all the kids had grown out of it, or left. Similarly, if you sprint and sprint and sprint you will collapse from exhaustion. I often wonder if they picked these words because they knew nothing at all about sports, of if there is a coded warning in them...
- brightball 7y agoScrum won out because it was waterfall in disguise. Commitments and sprints become terribly destructive over time.
- colordrops 7y ago> Commitments and sprints become terribly destructive over time. Could you elaborate?
- anon1m0us 7y agoYou're asked to deliver a feature that would take 4 weeks to implement without tech debt in two weeks. This requires sacrifices like ensuring network connections remain alive, handling exceptions, optimizing queries, abstracting functions for re-use, handling all the data input scenarios, etc. This creates a confusing code-base with lots of IF statements, copy/pasted code, data modifications from several areas of the system, etc. You'll fix a problem with data getting into the database incorrectly and realize a couple sprints later, fixing that bug caused other bugs elsewhere. Automated testing doesn't catch it because automated testing only handled certain scenarios. It's a mess.
- drngdds 7y ago>You're asked to deliver a feature that would take 4 weeks to implement without tech debt in two weeks. Well there's your problem. How is that inherent to scrum?
- barrkel 7y agoBecause it's a sprint. You've got a finish line and you're racing towards it. Businesses don't function without prediction, and refactoring gets cut before roadmapped features. If feature development is a bottleneck in company growth, debt will grow, quickly.
- MartinCron 7y ago
- dominicl 7y agoAgreed, it feeds the existing power structures. And it did hit at the right time when over-communication is not only appreciated but everything else is seen as intransparent and potentially suspicious. "You don't even know what your team is doing?" - is the best way for middle-management to pick on each other. So in order to never get into that situation daily standups, slack, jira, basecamp all these "transparency tools" are welcome as they offer defense for this manager. Does anyone know if there is an anti-movement to that over-communication trend? Something along the lines: "The only way to go fast is to go well", * Plan * Honor the flow * Adjust
- sidlls 7y agoI don't find much constructive value in your comment. To me it seems like a politely worded screed about the incompetence of management and organizations. To drive the point home I could easily transform "[o]n average, the first priority of managers and execs is maintaining the power structures that make them a big deal" into a derogatory comment about engineers, fad chasing, and resume padding by a simple word substitution. It would be neither accurate nor fair to many (perhaps most) engineers: just as your comment isn't really accurate or fair to managers or organizations.
- wpietri 7y agoI have been both a manager and an executive. As well as a consultant in many companies both small and large. I'm not saying that those people are necessarily incompetent. I'm saying that, per POSIWID, the purpose of most software organizations is not effectiveness in making software (or in serving users via software). That's not constructive in the sense of providing ways to solve the problem. But that wasn't my goal. My goal was to support and confirm the article's thesis. I have also written plenty of constructive things on software development, but I think it's absurd to suggest that every HN comment must contain that kind of constructive feedback. (And if that were a reasonable standard, you aren't living up to it.)
- keithnz 7y agoyes, I too was involved with XP before it was under umbrella of Agile which got consumed by the Scrum borg. I feel we kind of lost something where creating code/designs using strong feedback loops was a "first class citizen with royal honors" of the software development process. Scrum kind of makes it a sideline issue, a peon of middle management
- wpietri 7y agoTotally. Although this has long been a problem. My dad started developing in the late 1960s. He did a lot of in-house software, mainly manufacturing and insurance systems. His approach was to go out and see something in use, talk to the people using it, go back to his office, write something, release it, and go talk to the people again. He'd do that loop in as little as a couple of days. Today we'd call that obviously agile. But both back then and now, higher-ups wanted more "control", by which they meant feelings and appearance of control. Which caused longer feedback loops. Which made things more out of control, which required more process and even longer feedback loops. I think we have the same struggle today, and I have no idea how to get out of it.
- tootie 7y agoScrum is badly misunderstood and maybe that's a failing in and of itself but it's really a victim of the developers who sold it as a magical process. Scrum simply can't be implemented as a purely developer process. The backlog exists as a rolling contract between dev and product owners and sponsors. The most common failure I see is when project leadership agrees to a fixed scope and timeline then tries to execute in an agile way. Agile is the contract. But it's also a tough sell. It requires a high degree of trust to say "we'll pay you $XM in exchange for X sprints of whatever we prioritize with no fixed end state" but that's what you need to be agile. If you layer sprints on top of a fixed timeline, you're just adding needless complexity since your end state is predetermined and how you get there is irrelevant.
- keypusher 7y agoHave you seen any methodology work consistently when dealing with fixed deadlines? The reality when dealing with large contracts, as you mention, is that there are almost always timetables with expectations. This poses an inherant problem due to the unreliability of estimates, so either quality or features must be sacrificed if the timeline is in jeopardy. My only experience in such an environment was using some hybrid waterfall/sprint methodology that mostly worked fine, but i suspect that was more to with the general culture and people involved than anything else.
- nine_k 7y agoI think no industry producing anything new ever found a working process to predict and keep the timeline. (If omniscience really existed, it would have more lucrative applications.) Developing new aircraft, building a new ship, building a custom-designed bridge (most of them are) are processes that often run out of time and / or budget. If you want predictability, you want repeatability. But in software all reliably repeatable parts become automated away.
- wpietri 7y agoAbsolutely. And I'd add that predictability is dependent upon not learning anything over the course of the project. To be predictable either you know everything that matters up front (which is only true for trivial projects with no competitors) or you refuse to learn anything along the way (with, e.g., a big-bang release at the end). But I think good projects release early and often precisely so that they can learn as they go. At which point predictability goes out the window.
- mcv 7y ago> On average, the first priority of managers and execs is maintaining the power structures that make them a big deal. But true Agile processes are about empowering teams to self-organize around serving users. But that doesn't explain the success of Scrum, because Scrum does away with the power structure of managers, and should empower the teams. "We're doing Scrum now" is the big stick I see scrum masters use to beat back Business managers to keep them from interfering with and micromanaging the team. At least, that's what they should be doing when management interferes too much. And then address this higher up with whoever decided that we're doing scrum now, and explain to them what that means, if necessary. There's no excuse to tolerate micromanaging managers in a Scrum process. They don't belong there. Kick them out.
- arendtio 7y agoAgile has a problem with introducing Processes and Tools (by definition, as the blog post describes). However, Scrum offers a solution to this problem by creating an Agile space or bubble within those organizations that are still stuck with the traditional methodologies (Waterfall, etc.). So Scrum is a nice way to introduce organizations to Agile concepts but it is certainly not the final goal. IMHO, the idea is that over time the organization will adopt new Agile practices and not depend on Scrum anymore. In practice, however, many organizations think they are Agile after they introduced Scrum, which is a simple fallacy. After all, becoming Agile is about a culture change and not about the introduction of a new process framework.