Upper mgmt needs to get a clue. This new “model” they’re thrilled about is just making a mess with processes that don’t have any. How about upgrading our systems and maybe things will be better
9 replies (most recent on top)
From one of Dilbert comics on Agile:
"We're going to try something called agile programming. That means no more planning and no more documentation. Just start writing code and complaining."
Agile at BNYM is really only welfare for obsolete traditional waterfall Project Managers.
Good God… and this people is what we have for Roman Regelmann’s FIVE YEAR FAX automation. BNYM is still stuck in the 1970s.
@2pct, you likely are NOT agile. You probably have limited involvement from the business and users, tons of red tape and no incremental changes.
Agile has made a mess of development. We have been agile in our area since May 2023, and it has made an utter mess of our abilities to deliver.
Five years ago we were looking at an easier way to get transactions from faxes into our system. Our machine learning team had a solution that could learn how to identify most of the information on the faxes but we didn't have a way to get it into our systems yet and it was using a manual feed we created for a lot of the information. I suggested for starters to just put it in a spreadsheet format and use our existing functionality to import it into our system and eventually provide on an api for them to access our data and eventually even to insert the data. That was struck down because the first phase would have operations manually reviewing the spreadsheets and uploading them to our system. So instead of taking advantage of incremental improvements in the process we STILL don't have ANY of it implemented and operations has to do more work by processing the faxes from scratch.
Been on the Agile train for a while: trust big institutions such as ours to take something efficient, force it down inappropriate departments and processes and manufacture more work. Trying to fit a circular small peg in a massive square hole here and leaders are squirming over agile stats. The purpose gets lost when you want “numbers and stats” to look good. Bunch of ours are now implementing methods to make the numbers look good vs actual outcome/delivery. Betting on the fact that in the next 2 years quarters sh-t will hit the roof- excellent stats and numbers with poor execution and outcomes. Bring out the popcorn.
It’s all scrummed up.
At least in my department the current state was never documented and they haven’t even figured out what’s broken. Hope this agile methodology accounts for that. No one knows what they’re doing now or why to even grasp what needs to be fixed. And they better have some really expert Scrum Leaders on each team or we’re going to be unwinding all this in a year or so. Definitely McKinsey buzz words of the week. And a short while ago we were calling it POMs and PODs and now we’re forbidden to say those words. I guess giving us practice on agile shifts and iterations at the jump. Sure hope this is the miracle we need.