Thread regarding Bank of America layoffs

Agile is another fad. It will be gone soon. Like jelly of the month club.

@1xbi+1r9lVeB6 You just proved how useless SM/RTE positions are.
"It also can make life easier for supervisors, as instructions only have to last a couple of hours until the next scrum." So what do SM/RTE do outside of scrum calls? This is why many installations are moving from Scrum to Kanban.

Let's be honest here, observation and supervision have been in place even before Agile was introduced. Now, dev teams are experiencing burn out from Agile overkill.

The Atlassian suite is a mess at best. I wonder how much commission someone got for selling that bottle of snake oil.

“Is it really the Agile process or all the MRA documentation that’s causing all the overhead?”

Actually, agile created the MRA mess. Development teams went wild west with agile. Documentation and requirements were thin. The result was a lot of implemented changes lacking requirement tracking, thorough testing, etc. It was comical and sad.

MRA became inevitable. Unfortunately, whomever came up with MRA’s solution didn’t do a great job. They forced a bad process into Jira. Honestly, do we have to submit a power point for designs? We couldn’t have leveraged confluence in some way? It’s a big fat mess and no one wants to implement any changes. And it’s becoming more and more expensive to do work.

GTO is in a death spiral. Less and less change with more and more overhead and exploding costs. Well done.

Software developers, like others, are of variable quality. In waterfall, they are supposed to figure out what to do from specs. Not all are up to it, so Agile adds an increased level of observation and supervision. It also can make life easier for supervisors, as instructions only have to last a couple of hours until the next scrum.

"Agile is about creating non-essential positions in IT with no productive benefit to the end state."
It is a way to whip the employees. Then the employees learn to manipulate the agile process to make themselves look good which does not necessarily translate into a quality product. It turns the company into a Burger King.

Is it really the Agile process or all the MRA documentation that’s causing all the overhead?

Several years in and still no product owner for our team. That sums it up.

The cooldown period is such a joke. We are forced to lower the points in the last sprint but it does change the load and hours in relaity. We are actually overworked because Agile became a project in itself (20% overhead). Agile is such a useless program. Too much pageantry. Too many ceremonies and ceremonial positions. Scrum Masters, RTE, simply asks ask for team progress. Unless they manage an AIT, the actual heavy lifting goes to the dev teams and PO. Such a waste,

Agile is about creating non-essential positions in IT with no productive benefit to the end state. Just ask yourself on every call who are the participants and who are the spectators. You know who are the spectators as they do not contribute to the process. Just dead weight pretending to be important. There are a few benefits of Agile that can be used in Waterfall for a hybrid approach. In either principle, I agree on the cool down period to evaluate and correct immediate production issues after each install.

Agile is all about turning people into machines