Thread regarding Wells Fargo & Co. layoffs

Unintended consequences of Agile

We hopefully can agree that Agile methodologies originally served to allow software code for products and features (net-new, patching, etc) to deliver to market more expediently.

Now that Agile has fully matured and evolved into all facets of technology, we can't escape the byproduct of the method when it doesn't fit the above type of work:

  • Compartmentalization of actions w/o understanding the big picture increases risk
  • Cannot meet in traditional manner to meet and discuss design/strategy (We are always putting out one fire after another. The fire itself is considered the product feature. Ha!)
  • Productivity is measured in JIRA/SN output that does not consider quality or complexity of work
  • Interpretation of the methodology encourages sloppiness/speed over actually understanding the method. Agile is a legitimate skill and takes time to learn and review how the method is or is not working.
  • Promotes zero time to build and maintain professional relationships. We are mere chess pieces on the board. Someone above is moving us or the board around. What purpose do I serve each day at work?
  • Agile destroys any ability to accurately place value on any given worker. We are all not robots on an assembly line. The number of tickets assigned/closed/etc is not a metric that matters. At all.

We have concerns that need to be addressed, we have ideas to share, we want to participate in the company's future and improve ourselves along the way.

Agile is forced upon us poorly and without any regard for whether it makes sense. It does not consider our individual professional skillset, it does not value a real person's contribution today or tomorrow.

Each one of us should expect to be treated as professionals in the workplace. Agile promotes the opposite, it is a dirty factory floor with no mop in sight.

by
| 1943 views | | 20 replies (last October 28, 2023) | Reply
Post ID: @OP+1ph7bd9E

20 replies (most recent on top)

@geu+1ph7bd9E

Are you a program manager? Then I have more reasons not to trust you guys. Don't come to my LOB.

by
| | Reply
Post ID: @2tfa+1ph7bd9E

I agree with the one who said they are trying to force agile to be used in areas where it is not needed. We had a simple system that was efficient before, but they forced us to start using agile, and now I end up doing the exact same work but with a more pointless meetings. Of course, the reality is that during these agile meetings, I just listen in, but get actual work done while they are talking about stories.

by
| | Reply
Post ID: @1imw+1ph7bd9E

Just accept we aren't actually doing Agile, just using JIRA for extreme documentation, and all the problems go away???

by
| | Reply
Post ID: @1abj+1ph7bd9E

WF is trying to force every area into Agile when Agile wasn't meant for every process. The leaders don't understand that at all and it is a giant dumpster fire for so many teams.
Forcing people to use tools that don't do anything but bottleneck the process is the antithesis of Agile. This company is on a downward spiral big time, but I can't help but think that is part of the plan. Add in outsourcing thousands and thousands of jobs to India where they don't care one iota about the work or the company...massive failure throughout "the firm."

by
| | Reply
Post ID: @1tas+1ph7bd9E

I think the major problem with Agile are the people. You need to have a vision and strategy BEFORE you start sprinting. If you are taking a roadtrip, do you know your destination? When you know that you start iterating and delivering value.

by
| | Reply
Post ID: @1cfp+1ph7bd9E

We are spending too much time for documentation than focusing on actual work due to auditing requirements ifor Jira stories. Product conversion is not working well in our LOB.

by
| | Reply
Post ID: @1eag+1ph7bd9E

@1zqb+1ph7bd9E

Added problem is that many of those id--tic program managers are now trying to manage scrum masters and product owners, giving them waterfall instructions. Agile teams need to be managed by agile product managers, not by waterfall program managers.

by
| | Reply
Post ID: @1vcd+1ph7bd9E

@1jqa+1ph7bd9E

I agree, program managers are some of the worst offenders in change management. They are ignorant and arrogant at the same time. They don't understand what LOBs need and how the SDLC process works. One program manager (he is an SVP by the way) freely admitted that he has not done project management for years and can't remember how to manage projects anymore. I can see why project managers struggle under those id--tic program mangers because they are giving project managers wrong instructions and creating more chaos. Wells Fargo needs to get rid of those overpaid program managers.

by
| | Reply
Post ID: @1zqb+1ph7bd9E

@geu+1ph7bd9E

I have observed that most of so-called "program managers" are most incompetent and useless. You guys have no clue of what you are doing. I think Wells Fargo can save a lot of money by getting rid of these useless and incompetent program managers.

by
| | Reply
Post ID: @1jqa+1ph7bd9E

Agile is a joke here. Change Management is an utter failure

by
| | Reply
Post ID: @1mkg+1ph7bd9E

@geu+1ph7bd9E

I thought we are transitioning from program management to product management. LOL. You should stop the old thinking, that's why LOB has difficulty trusting you. LOL. Stop blaming business partners for your incompetence. LOL.

by
| | Reply
Post ID: @1qbo+1ph7bd9E

In tech engineering we are in no way shape or form ‘agile’. That concept is a complete failure and waste of time. Thank goodness wf wants to push a 20 year old square philosophy int a round whole for everyone. A huge mistake for some groups

by
| | Reply
Post ID: @yir+1ph7bd9E

Program Management is impossible at WF. There are too many Insecure business partners who are not willing to delegate work and allow a PM to manage a matrixed team. They have all but gutted the PMO for change management under the guise of Agile.

by
| | Reply
Post ID: @geu+1ph7bd9E

It's not Agile itself that is the problem. Agile works well in a pure technology environment, but not suitable for the highly regulated banking industry. Agile also does not work well when the incompetent leadership forces to override the process.

by
| | Reply
Post ID: @jyj+1ph7bd9E

Wf waste so much money on this garbage

by
| | Reply
Post ID: @tze+1ph7bd9E

Agile might work at a small company that produces inconsequential products. If there's a bug in your goofy new app, so what? It does not work in a highly regulated industry (like banking) and with large, complex projects.

The example you hear from Agile Coaches sums it up: "Say, you want to change the color of a button..." We're NOT changing the color of a button! We're replacing a mission-critical legacy application that interfaces with 20+ other systems.

by
| | Reply
Post ID: @khq+1ph7bd9E

You are describing Scrum and not Agile.

by
| | Reply
Post ID: @umr+1ph7bd9E

There’s nothing wrong with Agile. Exec management forcing it down our throats while subverting its principals is a dumpster fire. Blaming Agile is like blaming Dell because your computer doesn’t work when you hit it with a hammer

by
| | Reply
Post ID: @hjb+1ph7bd9E

I’ve worked at a few “agile” companies and they all end up the way WF is now. Agile is just like Six Sigma - failed ideology.

by
| | Reply
Post ID: @gll+1ph7bd9E

Any Software Development Lifecycle methodology not followed will lead to problems be it waterfall or agile. Wells Fargo leadership allowed Agile to be corrupted by making it 'Wells Fargo Agile' and not what is true agile. Add the business not supporting in all case and you have the recipe of failure.

by
| | Reply
Post ID: @zao+1ph7bd9E

Post a reply

: