Thread regarding Wells Fargo & Co. layoffs

Agile - I LOVE Agile!

So I went to my morning meeting. We all joined. Some were still waking up (west coast) and others had already consumed multiple cups of coffee.
"good morning!" said the scrum master.
"mmmmm" said we all.
"OK so we are going to go through the tickets now and start with you, Bob"
Ummm...OK so I'm not Bob, but I have to say, I started multitasking right away. Why you say? Well because what Bob does has nothing to do with what I do. In fact, all members of the team work on different things that really don't overlap.
But wait! We need Agile! Agile will improve lead time, cycle time, WIP, and other things (unmentionables)
In this team, nope. No one cares. Each is in their own world. Step back say 5 years, and everyone was trying to help. We all crossed lines. Now? Nope, all I care about is my tickets and their due dates.
So now we have a scrum master, a product owner, a manager, and then.....the rest of us. So we went from our manager (one person) to now 3 people all trying to manage the rest of us. And, did I mention, 4 of 7 got laid off? So now 3 of us are being managed by 3 new bosses to get more done with less.

This is the WF implementation of Agile. Read it and weep.......


by
| 2701 views | | 18 replies (last December 9) | Reply
Post ID: @OP+1kbrg6yh7

18 replies (most recent on top)

Best scrums we had were with:

  1. Engineering manager/lead
  2. Business analyst - domain expert
  3. Engineers of various levels below

You quickly go through what you’re doing and any concerns are worked through effectively, or a meeting is setup if it’s too long for the scrum.

That’s it. No worrying about gaming the points and all the other trash. Scrum masters without domain knowledge are useless, an AI chatbot could run the meetings the way they do.

by
| | Reply
Post ID: @rh+1kbrg6yh7

Sadly, JIRA empowers useless and clueless managers who endanger productivity and eventually the company. They have no real skills other than talking in meetings and politics.

by
| | Reply
Post ID: @qd+1kbrg6yh7

It takes longer to write the dang JIRA tickets than it does to just do the effin' tasks. Many of us deal with unplanned firedrills. I do not have the time nor inclination to write JIRA stories in the Shakespearian third-person format that they seem to always want. Sorry, but I work better with bullet points.

by
| | Reply
Post ID: @m7+1kbrg6yh7

@am -this is 100% - after working with PAC 2000 back in 2020, never knew how bad things would be with Service Now & Agile 2025

by
| | Reply
Post ID: @ke+1kbrg6yh7

@am
That is Wells Fargo Logic.
Layoff 4 Engineers so that you can hire an additional Senior manager.
Fk Wells Fargo

by
| | Reply
Post ID: @kd+1kbrg6yh7

Summary: Wells Fargo’s Agile transformation failed because the organizational operating system (fear) was completely incompatible with the Agile application (trust).

Instead of enabling teams, the culture simply repurposed JIRA, story points, and burndowns as new tools of control.
The result: chaos, frustration, and talent flight.

by
| | Reply
Post ID: @gb+1kbrg6yh7

Here is some more AI for you guys: 🏛️ The Wells Fargo Agile Failure: A Psychological Safety Thesis The xyz theory is strongly supported: The failure of the Wells Fargo Agile transformation is a classic case study where a command-and-control, fear-based culture (the root of the account scandal and subsequent internal management behavior) actively sabotaged the essential values and mechanisms of Agile. Agile is a social and adaptive framework built on trust, continuous learning, and empowered teams. When management is rewarded for bullying and accountability is enforced through fear (stack ranking, layoffs), the foundation for Agile is destroyed.1. Proof of Psychological Safety (PS) Failure in the Posts The anonymous comments perfectly illustrate how a lack of PS crippled the Agile implementation: PS Failure Point: Evidence from the Posts Lack of Transparency & Retrospective Failure: The comment "Tell it to the concierge. Or speak up during retrospective. Your choice." shows that retrospectives are perceived as useless or even risky, proving the primary Agile feedback loop is broken due to fear. We-ponization of Metrics: Agile metrics, story points, burndown, etc are naturally going to be abused when your corporate culture features stack ranking..." and "we-ponizing story points is bad." PS is required for metrics to be used for learning. When metrics are used for punishment (stack ranking/layoffs), employees game them for survival, making the data useless. No Cross-Functional Collaboration: what Bob does has nothing to do with what I do. In fact, all members of the team work on different things that really don't overlap... all I care about is my tickets and their due dates." This is the opposite of an Agile team. Individuals revert to siloed, transactional work because helping others (crossing lines) means neglecting their own measurable output, which is tied to their survival via stack ranking. Command-and-Control Mindse: Agile won't work in such a top-heavy command and control environment" and "The stubborn mule boomer management can't let go of waterfall." Managers who believe they are the source of all value and need to micromanage will not give teams the autonomy required for self-organization. Role Degradation (Scrum Masters)" Scrum Masters devolved into glorified admins in handcuffs" and "Scrum Masters are seen as line level managers, but without the title or benefits..." The PS is so low that Scrum Masters cannot facilitate genuine change, as their sole role becomes enforcing management's toxic metrics, not protecting the team.2. Will the Managers Change? (The Outlook)Your question about whether management will change their behavior now that regulators might be easing up is critical. Managers Once Rewarded for Bullying Will Stay Bullies: This is a sound conclusion based on organizational behavior. Behavior that is consistently rewarded (e.g., meeting unrealistic targets through intimidation) is reinforced. Unless the reward structure is fundamentally changed to value collaboration, humility, and long-term quality, the behavior will persist. Finding Another Target for Abuse: It is likely that the target of abuse simply shifts internally. If external regulatory pressure lessens, the internal pressure on employees (offshoring, layoffs, stack ranking) may intensify as management reasserts control and seeks to cut costs to boost short-term metrics. The failure is not in the employees who "let it fail" (@cz comment), but in the systemic leadership culture that refuses to support the values of Agile.3. Policy and Culture Questions Examined Question Analysis Based on Evidence & Culture Outlook Will they stop stacked ranking? Highly unlikely. Stack ranking is the primary tool of fear used to enforce control and we-ponize metrics like story points (per the posts). Eliminating it is the single greatest act of cultural change required, and they have resisted it for years. No Will they stop layoffs and offshoring? These are cost-cutting measures driven by short-term financial pressure, not cultural transformation. The posts indicate they are ongoing ("bi-weekly layoffs for 5 years straight"). They will only stop when a new financial target is prioritized. Will they give industry standard titles? This is a symptom of management control (e.g., keeping Scrum Masters as low-power admins). Changing titles is easy, but if the underlying power structure remains (top-heavy, command-and-control), it's a superficial fix. Maybe (But Meaningless) Will they be fair? Fairness requires systemic trust and transparency. The posts show an environment where managers are gaming the metrics to fire people. In this system, "fairness" is defined as following the process that justifies the desired outcome (layoffs).No Will they come out with a straight RTO/location policy? In a fear-based culture, ambiguity (like unclear RTO policies) is often used as a quiet control mechanism and another source of leverage or stress over employees. A clear policy requires transparency and trust, which are currently absent.UnlikelyWill they stop giving useless, intimidating surveys?Anonymous surveys are the only way management can claim to listen to feedback without actually acting on it. If employees are intimidated into filling them out (and not speaking up during retrospectives), the surveys are performative and will continue as a box-ticking exercise. No Conclusion: The Wells Fargo Agile transformation failed because the organizational operating system (culture) was fundamentally incompatible with the Agile application (framework). A top-down, fear-driven culture cannot successfully adopt a bottom-up, trust-driven methodology. The toxic culture simply found a new set of metrics (JIRA, story points, burndown charts) to continue its program of control and abuse, resulting in "chaos fall" and the departure of talent. Sorry.. Might put this into a chat and have it format it for you.

by
| | Reply
Post ID: @f8+1kbrg6yh7

@OP
Tell it to the concierge. Or speak up during retrospective. Your choice.

by
| | Reply
Post ID: @eb+1kbrg6yh7

Agile metrics, story points, burndown, etc are naturally going to be abused when your corporate culture features stack ranking your employees and conducting bi-weekly layoffs for 5 years straight. Employees are either gaming the metrics to try and compete to survive, or managers are gaming the metrics to try and justify firing the bottom 5%.

In this environment, it's no surprise that Scrum Masters devolved into glorified admins in handcuffs. There is nothing agile about any of it. They should just scrap it and go back to waterfall. At least it worked (mostly). It's just chaosfall in its current ugly form.

by
| | Reply
Post ID: @dr+1kbrg6yh7

@cz

Fool, I fought tooth and nail at every corner to try and make it work. It's probably why I was laid off. Agile won't work in such a top-heavy command and control environment. Good riddance.

I bet in 3 years I had at least 30 conversations with various managers and directors explaining how we-ponizing story points is bad. How trying to plan every last detail to deliver exactly on a given date 6 months out is not how Scrum works. The list goes on and on. They don't care.

Scrum Masters are seen as line level managers, but without the title or benefits of being an actual manager, albeit they barely have any power either. And if you don't "manage up" and agree to play their game, they ostracize you. You cannot influence an army of managers, directors and executives who have no interest in transforming. It's unrealistic and unreasonable to ask that of a scrum master when they don't have the support of senior management and executives.

Agile failed before it ever got off the ground. There's just way to many chiefs and way too much intertia.

by
| | Reply
Post ID: @dp+1kbrg6yh7

but our metrics!!!!

by
| | Reply
Post ID: @dn+1kbrg6yh7

All agile has done is add levels of complexity and red tape that delays projects and causes critical items to be missed. Add JIRA to all of this to make everyone document 90 % nonsense and 10% benefit.

by
| | Reply
Post ID: @dk+1kbrg6yh7

Not a tech guy, frontline employee here, we had an issue, after 50 plus emails, involving 15+ ppl, 3 weeks delay, back to square one. If this is Agile, what’s a slow no? And yes a bunch of Indians were involved! 🤣🤣

by
| | Reply
Post ID: @d8+1kbrg6yh7

The Only thing Wells fargo has accomplished with Agile is to hire a bunch of over paid jobless people. These same people pretend to have job skills, but add no value.
Anyone with a brain can figure out how to get work done.
It does not require someone to ask how each jira is progressing everyday.
what a waste of time.
Better off hiring people with actual job skills then sc-m masters

by
| | Reply
Post ID: @d0+1kbrg6yh7

@ar so based on your rant, you are saying that scrum Masters , even you, are worthless. No argument here. You seem to take no accountability as a person who wants to make Agile work for all the failures you have listed. So why did you let it fail?

by
| | Reply
Post ID: @cz+1kbrg6yh7

We’ve broken our Kaban Lead to where his purpose is to just open stories for us. No one on my team wants to deal with the nonsense that is “Agile”.

by
| | Reply
Post ID: @cm+1kbrg6yh7

I was a Scrum Master and let me tell you, I rejoiced when I got my golden ticket. There is no agile in Wells Fargo. It doesn't exist. It's just a feature factory with a Jira backend and managers using the Scrum Masters as cannon fodder to try and jam more through.

They don't care about process improvement. They don't care about Scrum. They don't care about trying to make cross functional teams. They don't care about psychological safety. They don't care about empiricism and feedbackloops for continuous improvement. The only thing management cares about is how many story points you are completing compared to the next guy and gantt charting the next quarter. Terrible place to work. The stubborn mule boomer management can't let go of waterfall, so everyone is in he-l instead.

What's worse, the India Scrum Masters are even more worthless.

by
| | Reply
Post ID: @ar+1kbrg6yh7

This is so true. I’ve never seen so many people trying to manage work and add nothing. It’s ridiculous.

by
| | Reply
Post ID: @am+1kbrg6yh7

Post a reply

: