5 ms·
>"Just like the cargo cult Agile pandemic peaked a few years ago, I suspect we're reaching peak open floor plans right now." Wait, that peaked? That hasn't bee
by bogomipz 9y ago
>"Just like the cargo cult Agile pandemic peaked a few years ago, I suspect we're reaching peak open floor plans right now."
Wait, that peaked? That hasn't been my perception. I'm curious where you are seeing that.
- varelse 9y agoI'm not seeing anywhere near the $h!+storm of pointless standups I used to see every morning. I'm also seeing the return of the weekly status meeting. Give it time. Then again, I'm someone who's threatened to enact the 6 mph standup meeting wherein the second anyone drops below 6 mph on foot, the meeting's over because how can we practice Agile if we aren't agile? That wasn't received well.
- brogrammernot 9y agoVery rarely do I actually lol but I just chuckled so hard in a meeting. Yeah, you guessed it. An agile meeting.
- robertlagrant 9y agoPretty sure you both mean Scrum.
- noarchy 9y agoI haven't been seeing it, either. In fact, I dare say it is nearly impossible to find a software shop in my area that isn't knee-deep in some iteration of "Agile" management - usually some form of Scrum.
- abritinthebay 9y agoThat's because it works. There's a reason it's popular. That said: a lot of places don't do it correctly and really do deserve being called cargo cults. Still, some process is better than no process.
- noarchy 9y ago>That's because it works. There's a reason it's popular. Versus: >That said: a lot of places don't do it correctly and really do deserve being called cargo cults. That's how it always goes, right? Company after company implements some kind of Scrum process, and when it doesn't work the problem is never Scrum itself. I'd contend that the reason things like Scrum are popular is that it gives non-technical managers things to play with: things like burndown charts, that gives them metrics to measure and show to their own managers. Devs aren't measured by lines of code generated per day anymore. Now it is all about "velocity" and burndown. Old wine in new bottles.
- varelse 9y agoTo be fair (and probably downvoted), _The Agile Manifesto_ is a great read IMO. None of its 12 principles mandate open floor plans, scrum or daily standups. https://www.smartsheet.com/comprehensive-guide-values-principles-agile-manifesto https://www.smartsheet.com/comprehensive-guide-values-princi... Combine these with Joel Spolsky's 12 steps to better code and I'd call that a winning culture. https://www.joelonsoftware.com/2000/08/09/the-joel-test-12-steps-to-better-code/ https://www.joelonsoftware.com/2000/08/09/the-joel-test-12-s... But that's never how it turns out so "you're doing it wrong" is (and I hate to admit this) a valid objection. Sigh...
- noarchy 9y agoI actually agree that the Agile Manifesto is a good read. That's why I tend to use air quotes when discussing "Agile" at any shop, because I think it rarely resembles anything in the Manifesto. But I'm not sure one can sell certification courses as easily based on the elegant-yet-simple principles outlined in the Manifesto.
- thwarted 9y agoThere's being "agile" as in flexible and outlined in the Agile Manifesto, and there's being "Agile" as in Scrum. I've found myself, and others, referring to the later verbally as "capital-A Agile" to distinguish the two.
- kps 9y agoScrum is collectivized micromanagement.
- postfacto 9y agoAgile protects the C-level from being fired for poor planning by blame-shifting to developers who get fired for not reacting to poor planning from above fast enough. Agile is Executive Armor.
- mlindner 9y agoHonestly, what's the alternative to Agile? Waterfall? Hell no.
- varelse 9y agoAn infinite ala carte menu of subsets of the parts you like about Agile, Waterfall, or any other methodology as long as you ship working code roughly on schedule. When I hear the above argument, I'm reminded of the Protestants versus Catholics scene in Monty Python's The Meaning of Life.
- EliRivers 9y agoI worked somewhere that did waterfall, hardcore. For everything, requirements came first (sometimes, since moving on, I've even found myself suggesting in meetings that if we don't know what we're meant to be making, the odds of getting it right are pretty slim - obvious yet somehow it needs stating out loud more than it should be). Sometimes literal months were spent on getting them right. Then the design. Full on designs, full on design reviews, the whole lot. It wasn't impossible to come back afterwards and change things, but it was pretty rare. By the time coding came around, it wasn't much more than implementing the design (coded up in literal programming style, too, such that what was written turned into two separate sets, being beautiful latex-based documents interspersing the design and commentary of that design with the code implementing each piece of design, and the code for the compiler to eat); all the actual programming thinking had been done during the design. Then levels of testing, starting small and unit, moving up through the layers until the original requirements were being tested against. It's the only place I've ever worked in which the customer never registered a single bug. They even asked us if we could take over from a different supplier since they'd never managed to deliver anything that worked. When the tests were signed off (and they literally were; the tester signed their name against each test, data records were archived, the paper test steps and signatures were sealed in envelopes for customer inspection on demand) that software did its job from delivery day one. Waterfall is really demanding and really hard to do well (and it also requires a high quality of customer; if your customers don't know what they want and simply cannot be guided into telling you, I suspect it's impossible), but it sure can deliver. I've never worked anywhere else that managed such high quality.