Відео

Europeans have a different approach to work than the American, for most of us our quality of life is more important than earning always more and more. On our side of the ocean, preserving a good private vs professional life balance is essential, more important than having a succesful career to many people. And we don't care about "keeping up with the Joneses" as much. In addition, in Europe we're under less pressure to save money to secure the essential necessities of life. We don't risk going bankrupt due to medical bills, or we don't have to pay hefty medical insurance fees to make up for them. Going to college does not cost tens of thousands. It's not so easy and so cheap to fire an employee. And we don't live on credit as much.

I'm only on my first programming job with SCRUM so far and something I noticed and I hate sm is how everything requires a meeting (physical or virtual). When something goes wrong with an app and I know what the solution can be, it demands a meeting to fix it, regardless. There may be sometimes the error can only be fixed by the tech leader and, yes, another pointless meeting, all for what? For the TL to not do what he could've done earlier bc "OH, HEY! ANOTHER MEETING, YOO".

One of the greatly explained videos I have seen

Thanks - as a Sr. software engineer, it's nice to hear the story from the other side

Absolutely, I fully agree with the main points covered in this video.

I think the idea of tying deployment to the end of the sprint is an outdated practice, and generally an immature outlook on scrum. Now, that's not me knocking or bashing, it just is what it is. I'm also not an apologist for scrum, I think you take whatever works for the team and implement that regardless of the framework. Agile is broken because it's been bastardized badly. Take it back to the core. Talk to each other, work in small iterations, and ship all the damn time.

Great video. Wish I would have seen this prior to becoming a manager :)

Drop the music bro don't really need it.

Steve Jobs:” the best managers are individual contributors who hate managing but do it because they *have* to”

Listening to someone rant about how Agile has failed software developers is about as interesting as hearing about how dieting has failed the obese.

Very nice tips, thanks for the video!

Because tech engineers in Europe are stupid and let managers who can't do anything walk all over them. In Europe you don't want to become an engineer, as everyone should become a manager, as they earn atleast twice as much and can do 10 times as less

your summary... and view on what should happen "instead" is exactly what agility should foster and is in its core...

Well what you said doesn't prove SCRUM or Agile is outdated or bad idea, it is just that it is terribly wrongly implemented and people doesn't understand its value so they bend the concept of agile and scrum into their management views which is control and reporting. The idea of agile is to get rid of unnecessary meetings and anything that goes against developers productivity and wellbeing. If people force the adoption of meetings that doesn't bring value unless checking what people are doing it's good old dumb management not agile. But i agree with that the consulting crap around SCRUM and agile certification doesn't help.

What’s your alternative to scrum that’s better?

Jira wasn't *created* as a project management tool, it was created as a bug tracker and a direct competitor to Bugzilla ("jira" coming from "gojira" aka godzilla). It *became* and agile project management tool after third party extensions like GreenHopper became popular and Atlassian bought them. Much of Jira's wierdness (when used for "agile") comes from these plugins being, well, plugins and not part of the core software. That's a minor quibble, though. The statement that "many people's careers depend on things staying the way they are" is so real.

What's the first line of the whole manifesto? We are uncovering better ways of developing software by doing it and helping others do it. This never gets quoted but it's the key. Develop software. Reflect. Learn as an organisation. Repeat.

"they check it before we deploy to production" scrum belongs in a world where you have to go to the integration machine and create an iso image. My orga is still shipping iso images, and i use the 2010 scrum guide to initiate teams.

i finish my first year as data engineering manager. seems like i wouldnt go back to code part. but im seeing less oportunities. the best advice is to refresh you technical skills)(just in case need to return) and develop managemetn skills and AI skill also

I asked some colleagues if they’ve ever read the agile manifest. One answered he didn’t have time for it. He was under the impression it was some kind of big manual. Great job on explaining what is wrong with agile.

If one starts with a faulty premise, the chain of logic takes us straight to the wrong conclusion Most people don't understand Scrum or Agility

i still find it baffling how a word as ugly as "scrum" managed to take hold as strongly as it has. Yuck

Could not agree more. IMHO the original agile manifesto was a sincere attempt to make the real-world practices of accomplished, mature, productive, professional developers transparent to customers who might be interested in actually becoming actively engaged in the development of their product, and engage in the ongoing "quality"/time/budget debate/compromise. It was all about flexibility, transparency, maturity - being real, and productive, in an agreed manner. In practice it seems to have become a formalised mechanism for the management of relatively young, inexperienced, over-confident, personally professionally and technically immature developers who haven't yet heard of Dunning-Kruger, never mind crashed through its trough. And an albatross around the necks of mature developers. And of course its toolkit/culture also provides the perfect mechanism for micromanagerial tyrrany. So much for the agile team being a closed safe space to learn, grow and contribute.

If you work in a big corporation, with a lot of processes, to the point it's impossible to get anything useful done, just give up and start coding stuff for fun, or take a second job and do that. Nobody will notice.

I feel you mate 😂 I have a stand up coming in 5mins 😂

What you describe isn't agile, or scrum.

Not to be overlooked is the fact that a lot of salaried jobs in Europe have very expensive insurance plans attached to them that protect workers against disability and labor exploitation, practically making it very difficult for employers to fire you. The cost of this tends to be about 35% of your explicit salary and is paid on the employer's side. You can bypass this by working as a freelancer on interim contracts, which boosts your income to about that of a run of the mill US state's average (easily over 100k euros per year). Still not as high as places like California and New York but those tend to have very high cost of living to offset that. There are also mid-lancer arrangements that offer an in between option where you get to keep 70% of your freelance hourly rate and have someone in an office finding contracts for you and probing your wishes and needs and a guarantee of about 2k month in worst case conditions. A good option for the highly risk averse. Ps. this is the situation in Netherlands, might vary between countries...

The content on this channel is pure gold!

Great insights! So true. Corporate culture of large companies is to blame. Waterfall is the same, the process is seen as the value rather than the thing being created via the project.

A major detail I think is left out in this discussion is the cost of living and the power of a given currency. In America, healthcare is super expensive, even with American companies being required to provide healthcare to full-time employees. But even then, they only subsidize it, which leaves the employees to pay pre-tax deducted premiums, copays, and so on. There are also deductibles we have to meet as well as other benchmarks. That's not even getting into the fact that employers may provide you with a dollar store, bottom-of-the-barrel coverage policy that you're stuck with unless you can find a better job, and even with good policies, they can still reject you for essential, life saving care. There's also the housing crisis we're currently facing here in America, where rent is stupid high and buying a house seems like a pipe dream left over from America's golden age. Food has also gotten terribly expensive, even though the supply chain has well recovered from the 2020 pandemic now. My point is that there is a lot to consider when immigrating between countries beyond just salaries. While that is important, the standard monthly expenses should also hold weight. This would help those who are considering making the leap across the Atlantic to make an informed decision.

A foldable phone works the best for me.

Daily scrum and standups are a giant waste of time and huge interruption to devs struggling to maintain or get into context... speaking as a manager & ceo.

This is why it is a bad idea: The most damning point to make against scrum(or most agile methods), is that, despite the fact that software engineering is an *applied science* , and we are all therefore supposed to use scientific principals when doing our job, despite this, **there isn't a SHRED of empirical evidence to support so much as a single claim made by scrum(or any agile) proponents** . This relegates scrum to the SAME category as aliens, bigfoot, Q conspiracy, flat earth, etc. That is, a category, for claims that are made, that are devoid of **empirical** evidence to support them. Belief in claims devoid of evidence, is by definition, **irrational** , and is borderline delusional. Being the opposite of rational, it is therefore the opposite of science, and therefore, NOT applied science. The most common excuse you get is, "agile is beyond the abilities of science to study" . Which is of course COMPLETE nonsense. The ONLY things that cannot be scientifically studied, are phenomenon that **do not manifest into reality** . They like to ignore that case studies, are considered the poorest form of evidence in science. They also like to ignore, that the handful of studies done into the matter, **show no advantage** to agile techniques. Fun fact, other things that are "beyond science" are aliens, astral projection, and bigfoot ROTFL. It is also important to note, that agile consulting, is a **multi-billion dollar industry, and it is ONLY growing** . So billions of dollars and hundreds of thousands of people stand to lose a lot if this little factoid about lacking evidence, is paid any attention. Quite the opponent. **One would think, that the biggest selling point to agile, to a bunch of scientifically minded engineers, would be empirical evidence of the claims.* "Here is undeniable proof it works" . "Sold" . Engineers use what works. **However, have you noticed, despite having billions, that industry refuses to provided any proof of the claims, by supporting the studies?? Now why do you think that is hmmmmm ROTFL????** My favorite argument "against" me, is "Well, that is just BAD agile" --> ROTFL ROTFL My favorite response: "For a system that is claimed to be superior, it is certainly inferior to ALL other methods, with respect to its ability to get it right. That is the opposite of superior, especially since none of your other claims about agile are supported by evidence."

You are awesome. I worked in software for 18 years. Earlier in my career, I was productive, innovative, and created good products. As time went on, more and more Afile, Scrum, Jira, Kanban took over, and I became less and less productive as well as less and less interested in programming. Then came the burnout…complete and done.

Agile = scam

The daily stand up done right is a way to handle obstacles as a team and make sure the team keeps direction and are organized the best way for the following day. It should take 5-10 minutes. It should never be about reporting. When I many years ago actually was a certified scrum master, the importance of the daily scrum should not be a status report was emphasised and that a status report meeting was an anti pattern.

I've made a lot of cash out of Agile... how? By correcting the problems it has caused... I'm a systems architect and engineer with about 30 years experience, and most of my work for the last 5 years has been recovering (fr-)Agile developed projects and reverting them to top-down requirements. That's not saying Agile in itself is bad, but I have never yet seen it succeed. Maybe the companies implementing it didn't understand, didn't do it right or whatever... but I'm grateful... correcting the problems it has caused has paid for my apartment and my car....

Scrum is like communism - nobody have tried it for real...

agile = middle management psyop to turn devs into buttslaves for mid management/other suits

I have seen and experienced issues with agile and have always been sceptical of some of the processes. However, it would be good if the video could provide quantity reasons or data highlighting the issues. At the beginning of the video, you say daily scrum is "COMPLETELY unnecessary." But then immediately follow up with "it works for some teams and not others", which is contradictory. Regarding sprint rews, not all product owners are going to be part of your scrums everyday. Jira is just a tool. You can design a building in Revit but it doesn't make you a good architect. It's just a tool. It'd be valuable el if you can give practical recommendations on how these tools can be used. If you work in a large organisation, reporting is just a reality. But management can put in place more actionable and streamline reporting processes. The chart.. well.. its just a bloated chart put together by a consultant to highlight the ethos and says very little about implementation. It's not even a process chart so has no real impact on day to day SW development. Time tracking is non valuable adding, but it's almost impossible to manage a large team without tracking peoples time. I'd love to see a follow up of this video with more practical and quantifiable recommendations.

Agile is shit

The only thing that is surprising to me is that it took this long for people to realize how ridiculous and non-Agile Scrum is. It was obvious to many of us from day 1.

For better or worse JQuery is still used ubiquitously! I still use it is a number of places. If it's the right tool for the job then use it.

Thanks! I thought I was going mad. But it’s nice to meet someone who knows what it’s actually like 😊

nowadays I only attend to dailies when I need something or at mondays. it's way better and I free more free

The problem with Agile methodologies are that they are derived from Extreme Programming which has a disdain for deadlines and fixed feature sets. Thus the methodologies are by design not functional in any environment where delivering specific features by a date is important. This would include delivering software to any Fortune 500 company or the federal government. If you're writing software for some bullshit free website you can do what you want; this is where agile shines. Managers start micromanaging agile teams because they need to deliver software and the agile teams can't tell them if they'll be done on time. That's where you get managers converting story points to wall-clock hours. They're desperate. The next iteration of Agile will include mechanisms for deadlines and commitments.

So basically story points are just ways to say how much more you should be paid I mean two coders who put out the same product and the exact same product one does it in a day and one does it in 100 days that guy who did it in a day should be paid more because he put in more effort therefore he put in more story points is that correct

Agile is like communism. It sucks because you're not doing it right. ( /s ) Or rather, not doing it at all, as I don't consider scrum to be agile, if anything it's the exact opposite. It's iterative and incremental which is better than waterfall, sure, but it's not agile. Agile is when the team gets to decide their own process, nothing more, nothing less, period. I worked in a place that was actually like that and it was glorious. We barely had any meetings, maybe like 2 hours a week in total plus whenever we needed help from each other obviously. We got so much fucking work done not being bogged down by process. And good work as well, as the objective wasn't to meet an arbitrary deadline at whatever cost, but to deliver quality. Granted sometimes things got a little bit chaotic, but it wasn't nearly as bad as scrum masters would have you believe. Something I don't think managers understand is that software development is very much a creative process. You need to be in the right mental space and your performance sort of ebbs and flows. And being unhappy is definitely one of the biggest productivity killers. It's actually insane how much more and better I code on days when I'm in a good mood. When everything just clicks and difficult problems are easy. Well I think I can count on one hand how many such days I've experienced in a corporate environment.

Scrum is also stripping away a layer of responsibility. Only way to 'grow' is as Scrum master or Product owner, roles a true dev does not want to achieve. No senior dev, opportunity, the pay is less and not your manager gets the blame but you, for the responsibility is shifted (without increase in salary), even if the estimates are completely off because complex tasks need thinking and sparring with competent co-devs, but they are occupied with other tasks in the sprint. The agile manisfesto is filled with commonalities that you think make sense but it is deceptive like the talk of the salesmen that sold encyclopediae, who did not need one? Many good comments on your rant.

If you read the Scrum Guide, you might see that all of the problems that people describe with it don't come from Scrum but from managers and Scrum Masters that are applying all the crap that has been added to Scrum courses for the Scrum courses to last more than an hour.