@bhelmore1
After being a successful software developer/architect for 40 years, the adoption of "Agile" by my company completely destroyed my love for what i did. Delusional upper management saw it as a utopia. They used it as a cudgel to bludgeon engineers into being more "productive", believing that software engineering was analogous to manufacturing. The number of middle managers exploded. Tons of cheap (and untalented) offshore engineers were added. The worst developers "gamed" the process and projects became a nightmare of never ending meetings and fire fighting. All of our code (since the use of Agile mostly discourages the idea of code ownership) began to reflect the worst developers on our team rather than the best. I retired and have never looked back.
@braincraven
I hate Agile with a passion not because of the process but they way it's abused by leadership thinking it's a way of pushing development bypassing design. š
@jammintoast1
In my 35 years experience Iāve seen many SDLC methodologies, and not once did the method make or break the product. Success comes from skilled analysts that ensure product delivers value. Meanwhile everyone is arguing about whether something should be classified as a feature or a story, even though they donāt understand the business requirements that will add value.
@LiamODev
Project managers love to 'project manage' complex discovery tasks - which just doesn't make sense. Agile is becoming just another layer of 'reporting', rather than a methodology of 'delivery' :(
@mc4ndr3
Agile has lost all meaning. Every company labels themselves Agile, without adopting any bottom up improvements in process or allowing space for creativity or fostering healthier relations between people. This unfortunate state of affairs is the natural consequence of hype having replaced long term prosperity. Everyone builds pointless vaporware on a death march, so there's nowhere to go to vote with your feet toward sane practices.
@steveoc64
I donāt care what label you use to describe āthe next great improvementā to replace Agile If it involves having stupid meetings all the time ā¦ then itās just another gigantic waste of time The average developer doesnāt need another meeting every couple of hours to know what to do next. They are not like children lost in a shopping mall For most developers, their biggest problem is not knowing when they are ever going to find the time to work on the things that they already know have to be done by the end of the week Just let them do their job
@rtwas
With my first and last experience in Agile, I found it to be a mechanism that enables upper management to more closely micromanage developers. It was rather unpleasant experience in my case.
@threndor3743
Caveats: 1) This is coming from a QA perspective, 2) This is from my career/experience with numerous companies of a broad size range. 3) Most of my projects have been 'blue sky' projects (ie: not maintenance or version upgrade projects) I have yet to work on a successful Agile project. 1) Most seem to use 'Agile' as an excuse to not properly document (Example: One project was in UAT, and a day or two before we were supposed to be 'done' and still hadn't received the UI specs for some pages. My punchline was that project was going to have a -3 days of testing when you looked at the PM schedule vs Dev schedule.) 2) Sprints get bloated and kill the schedule (Example: project laid out the general outline of the 10-12 sprints, schedule fell apart by Sprint 2 or 3 [sorry, it has been a while since this project] due lack of delivery and what was delivered was excessively buggy. 3) PMs pushing schedule over stories and and having to fall back on waterfall to clean up the mess (especially when QA is showing them code quality/feature delivery)... I always tell PMs: QA reports the news, your code will tell you where you are at in the delivery cycle. 4) Leadership thinking 'Agile' is a magic bullet that will deliver products faster with little up-front planning. I could go on, but that is the general sentiment. The next 'proper' Agile project that I work on that stays Agile to completion will be the first one.
@arturhellmann9138
We were a good working, self managed Software Team. We took some advantages from scrum, had a board and such things... but we did it our own thing. we did not need a lot of meetings, dailies were optional. Everything worked perfectly. Then someone from upper levels (basically a company that bought us) meant to implement scrum... We got a scrum master and what not... calendars got full with dailies, plannings, retrospectives... And everything went down... Now that I am leading, I would never do scrum again. We are working agile, but with a bunch of common sense... I feel like Scrum is just a way of overcomplicating a process that should run smoothly on its own with common sense and a good team...
@StephanLuik1
When an adverb becomes a Noun (with capital N) you know that your concept has been hijacked by business bobos. I have seen it all: VSP, RAD, XP, RUP, LEAN, Agile, Six Sigma, SCRUM, SAFe. As soon as the trademark sign appears behind the name, you know you're in trouble. Just build stuff that works and have some fun in the meantime.
@TheEtherea
I was a PM following the general idea of Agile. I gave people autonomy, monitored progress and had further discussions when necessary. Never had to micromanage people until an actual ASAP situation had happened. Major b2b systems were implemented successfully. As I left, Scrum came in my place and employees wanted to hang themselves with dailies, one to ones and more meetings they had idea what to do with. 6 months later there was nobody left. Literally everyone left. People can't comprehend this level of micromanaging bs when you give them autonomy and freedom to complete tasks for years prior to that.
@ktreier
As a CTO, my sole experience with a Certified Scrum Master was a negative one. They were so bound by the constraints of the āprocessā they were willing to allow the Companyās reputation be harmed by an outage.
@kennethmark6868
Good to listen to one of the initiators of the Agile movement, their original idea and principles.
@sholinwright2229
In my shop, we introduced SAFe, which has turned out to be the bloated, overweight, top heavy version of agile. Itās also allowed for many non specialists to migrate into engineering management. If you donāt know anything about radar, you probably donāt make a very good radar engineering manager.
@grizfan93
Agile has been ruined beyond all recognition. It started out as a good approach, but as soon as the con artists and grifters moved in, the entire word has lost all meaning. I spent nearly 30 years working in the corporate world for a large tech company, and the last 10 years of that was largely ruined by Agile and the people pushing it. It took me far too long to recognize the fact that every single person pushing for some sort of agile approach was a no-talent hack who wasn't able to contribute any real value to our work, and instead was using agile as a way to collect a paycheck. All a bunch of parasites. I knew one scrum master who had actual skill and integrity, and she jumped to a different role the first chance she got.
@daithi007
I've yet to meet a scrum master that removed impediments. The roll attracts bluffers and people who are effectively secretaries juggling jira tickets. Scrum itself is compressed waterfall. Scrum is a death march for team members. That's my opinion, based upon nearly twenty years of dealing with this faeces.
@hallstewart
30 years ago, I had a standup row at a job interview: software is engineering, but coding is a craft. The interview went mental at the idea that programmers were craftsman.
@frederipochard8892
Probably one of the biggest tool the management has created to take over Agile is SAFe.
@jf3518
I remember what happened after our scrum master left the project. Nothing...
@calebghormley2322