N/A
It is my honest belief that anything more complicated than Kanban isn't as agile as it pretends to be.
@chealej
"scrum is a really efficient way of making a mess really fast" yup. feel that.
@dr4t
If the managers are not changing priorities 5 times per sprint and then tell you "this is agile" if you complain, then what's the point of everything? That crippling anxiety won't come by itself!
@InconspicuousChap
And why do the engineers not do engineering practices in Scrum? 1. A product owner standing behind their backs and micromanaging their activities. "My KPI is more important than your technical debt because I'm going to move on next year, and you losers are going to put up with all this mess". 2. The influence that the product owner has over the developers, effectively becoming their manager, but not being competent enough. 3. The spoiled practice of everyone using everyone else as a disposable resource to reach their own short-term goals.
@aronrodrigues
24 years of experience and In just see one team doing scrum properly.
@reimusklinsman5876
The most efficient I've ever seen a company was when they just did kanban. I swear we moved at least 4 times faster than any other company I worked at with half the tech debt. At one company we had an engineer wide meeting because our story points weren't growing out whatever and I had to remind the PM that the team has been meeting it exciting every single deadline so if there is a problem it certainly wasn't with the engineers not doing work
@factorfitness3713
When everyone raced to "do agile" in the 2000s and 2010s, no one cared about any of this. They wanted the results without the practices. Turns out, that's not how it works.
@johnshaw6702
I laughed the first time I heard the term Extreme Programming. To me it was how I always programmed at the time. Although, I was the programming department at the time. Extreme to me was talking about what the program needs to do, start writing the details down, usually on paper, until it clicked in my head. Then I would start writing the code. I had a new manager, an electrical engineer, that wanted it fully designed up front. I told him if he wanted it done on schedule, then let me write it without all the paperwork and I'll write it up afterwards. For some reason, he wasn't interested in the design documents afterwards, and put me on the next project. Oh, I was also quality control, so it was rare that it left my desk until I deemed to ready for production. I miss those days.
@MarianneExJohnson
The "you're not doing it right" refrain from scrum/agile acolytes sounds an awful lot like medieval doctors prescribing more bloodletting after the first round of bloodletting has failed to cure the patient. Except in this case, the patient wasn't sick to begin with.
@garrettweaver3824
The point of the retrospective in scrum is for the team to develop these engineering processes. The problem with retrospectives are that it’s a threat to managers to let workers decide how to do their jobs. It’s the first scrum meeting to get cut in the pathway to 1-hour standup per day scrum.
@mepipe7705
"no, don't do refactoring now. first we need to only focus on releasing the MVP" (which is basically a big bang release, that already fits 95% of all business cases)
@MartinMaat
The one and most destructive thing is the collective ownership (it's in the graph on the screen, not being addressed). It means no one owns anything and thus takes care of anything or learns to understand anything properly, everyone is just collecting story points for the end of the week. And this is being rewarded while looking ahead and doing things that "have no business value" is punished. In politics it's called deregulation.
@mattschmidt2164
A lot of companies say they are agile when they really just mean they have points and standups. In reality their standup is a daily status meeting, and the points have been converted to hours so management can track time. I've been on high performing scrum teams but it takes a lot of discipline within the team as well as management allowing the team to be self empowered, which usually doesn't happen.
@prajapatij83
XP it is always and will always be.... I've been advocating that always... But the marketing takes over the minds of innocents... #JusticeIsDue😇
@georgehelyar
Just drop the "ceremonies" and "sprints" and be agile - focus on fast feedback cycles from users.
@TheMindverse
How about daily 45 minute long "Stand Up" meetings for a dev team of 8...
@michakowalski4147
I worked for few companies, and saw SCRUM done right in one case. It can be done.
@MasterSergius
Let's imagine that you build a skyscraper with several elevators. Within agile process, you might be told later that vip person wants to have elevator stop in his room. But everything is built. Next: another elevator should go left and right on certain floors. Finally, another one elevator should use AI to bring you to your room if you're too drunk to choose correct floor. And who knows, maybe later we should support elevator v2 in the same skyscraper
@dannyknowlton
Everybody using this as an opportunity to bag on Scrum, but Uncle Bob never said Scrum was bad. I think most people have never been on a team that actually practiced Scrum. Usually it's a team that has Scrummy sounding things they do, and then they think it sucks and doesn't work. Well, you weren't doing it! Also, if you neglect the engineering practices, only focus on project management, well of course you're going to produce really bad code. That would happen if you were following any project management framework, not just Scrum.
@JonathanRose24