371–380 of 462 posts
Earlier quoted context omitted.
The way I’ve explained this before is “would you rather small issues that we can fix one by one until anyone really notices or would you rather we hit all those issues in one big go?” Your mileage may vary.
Intuitively, I think most managers think that tackling everything in one go is somehow easier or less risky.
Rich Hickey put it best. “What kind of runner can run as fast as they possibly can from the very start of a race? Only someone who runs very short distances. But we’re programmers, we’re smarter than runners. We know how to fix that problem, we just fire the starting pistol every hundred yards, and call it a new sprint!” https://youtu.be/liUiRfN9NzQ?si=CRkbMokVLXLIdF42
Earlier quoted context omitted.
> Communism's defining feature is that there is no longer a state. Seriously? Who takes all the resources and allocates them "according to each person's need" then? :) > But it remains that communism cannot exist without having achieved post-scarcity. How could it? All the scarce resources are being stolen^H^H^Hshared in common. Communism predates the idea of post scarcity by a hundred years or more AFAIK.
> Seriously? Yes. Communism's key attributes are that it is classless, stateless, and moneyless. > Who takes all the resources and allocates them "according to each person's need" then? We'd need to know more about how post-scarcity is achieved in order to answer that question. Star Trek says the replicator is responsible, although that seems unlikely outside of the imagined Star Trek universe. Based on what we can s…
Did communist utopians realize it doesn't work so now they're adding "post scarcity" to it to make it work?
Will they add "AI" next?
Edit: "Based on what we can see today, I'd guess robots." Oh yea, "AI" is next.
Scrum is useless. it's just another method of demanding results. Where there isn't anything to tell, you shouldn't be forced to do so. All this imbecility does is to create competition, and weed out the ones that don't comply. I've worked in teams where we were forced to have something to report even when nothing was to report. This made the team create "things" to match their daily scrums, because the truth might ge…
This ten million times. It's about control, and it's about showing you that the only way to be considered to be doing your job, is if you abandon all dignity, and allow yourself to be treated as a child.
The adults (POs and managerial folk) are making your planning, your regime, you constantly report to them them what you are busy with, you summarize what you learned last week and what you'd be doing today, and you present to them your paintings for evaluation. It's so degrading and humiliating, but that's by design!
The secret purpose of Scrum is to get rid of managers and empower the engineering team. Most "scrum" is simply taught wrong because it was sold to companies as a way to squeeze workers.
Then Scrum spectacularly fails in its secret purpose, because it adds managerial type to the engineering team and removes power from the engineers.
Earlier quoted context omitted.
> Daily stand-ups, the main benefit of which is that managers (EMs/PMs) get daily updates on status. The scrum guide fairly explicitly states that managers should not attend or be part of stand-ups unless they're actively involved in the work as part of the development team.
It may be explicitly stated, but I’ve never had a scrum meeting without all managers and project managers. They also tend to make the stand-ups one hour long.
2 years ago we had 1 hour long dailies because the team was too large. We split into 3 subteams, each has their own stand-up. Now it's down to 15 minutes max.
Earlier quoted context omitted.
It may be explicitly stated, but I’ve never had a scrum meeting without all managers and project managers. They also tend to make the stand-ups one hour long.
As someone who works in a hard-tech startup, where daily standups in production manufacturing teams are part of the daily culture. 1) Anything longer than 15 minutes is insane 2) What do you even talk about for an hour? 3) Why do you even do standups for design work? What "blockers" could you possibly have that require daily, 15 minute tagups with the entire crew?
We once had 1 hour long standups. The reasons were:
1) large team
2) many devs loved to go into detail about their work, and no one stopped them
3) the expectation was that a standup must be about describing what you did yesterday, in detail
What we did:
1) split the team into subteams where each team has their own standup (down to 5-15 min)
2) the standup's facilitator now stops devs from going into too much detail, "you guys can discuss it further after the standup"
3) now the expectation is that a standup should be about checking the project status and if there are any blockers, and that's it, you don't have to recount your whole yesterday in great detail
Earlier quoted context omitted.
It may be explicitly stated, but I’ve never had a scrum meeting without all managers and project managers. They also tend to make the stand-ups one hour long.
> It may be explicitly stated, but I’ve never had a scrum meeting without all managers and project managers. This, this, this and a thousand times this. It's always the same with Scrum. Every time you point out something clearly wrong, the response is always "well that's not really scrum, you're doing it wrong". It's like when discussing communism with some diehard fans - when you point out the flaws, the response is…
Nitpicking, but the Soviet Union, for example, never claimed they were already a communist state. They were the "Union of Soviet Socialist Republics", not "Communist Republics". Their idea was that, to have communism, you must have a transitional form of government first, "socialist government". The USSR even once had a motto, "we will build communism by 1980".
It's like if someone said they were following some other development process which would eventually lead them to Scrum. But no one does that and just calls it Scrum :)
I'm at a weird point in my career where every development process stresses me out, no matter what. Guess that's burnout.