To be truly Agile you split your teams
One does production support
One does development
This company is faking it ...
Making people support both and yelling at them for not meeting unachievable goals
Sr mgmt is either lying or being lied to..
No, to be truly Agile, you don't implement a one-size-fits none process across every team in your org. If you need a prod support team, you make one. If you don't, you don't. WF just implemented Scrumfall, and it fails at every single place that tries it. And the mountains of bu-----t documentation we now do have nothing to do with Agile. In fact, Agile processes typically view documentation as worthless cr-p that rots the moment it is written. It's certainly not doing the customer any good.
Agile was supposed to be the holy grail to get changes implemented ASAP. So they put in layers of people, meetings, documentation that no one is ever going to look at, and all this takes lots of people and time. It is incredibly painful for all involved, but especially production support resources who have little idea what they are looking at or how it's supposed to work, and who are called in to pick up the pieces things go wrong for customers.
Agree w/@vqi: With Agile we've gone backwards with productivity and efficiency.
Our team works the way we have always worked we just meet every day now at something called a sc-m, with a scrum master who is powerless and does nothing really. My manager has somehow become even less relevant.
There is no continuous delivery, that's clearly not going to be possible within five years if ever without drastic changes to the release process. There is perhaps some small level of CI.
Despite the sham of the whole thing the daily meetings do keep everyone more accountable to some extent, and that is actually refreshing.
Agile is a joke everywhere, not just WF. Biggest scam IT ever had.
Everything WF does is f’d up. Don’t limit this to Agile.
When I gave my notice, I told my manager that Agile at WF was total bu-----t. I called it Fragile - fraudlent agile. How are you agile when you still release on a quarterly basis? Wtf is that? Plus we were in charge of a Vendor application that we couldn't make coding changes to, so we had to have the vendor supply an enhancement or a hot fix. Agile is nothing more than an SvB term at WF on a fu----g buzzword bingo board.
Our transition from waterfall to Agile was extremely painful and took 3 full years. No more BRDs in Agile? How the *u-k do we have traceability then? JIRA is not a substitute for BRDs. We have tens of thousands of JIRA issues but only had ~200 BRDs. Prod support issue comes in? Better pray you have a developer that's been here for 15 years that remembers everything but we are approaching end-of-life, over half of those devs jumped shipped or transferred within Wells. With Agile we've gone backwards with productivity and efficiency.
They made us take a class online about agile, but we never use it in the dept. of IT I work in and never will. They are also making us take an Azure class and on top of that we are now required to take a MS exam. My dept. will never use azure. Upper mgmt. has no clue what they are doing and what it is that we in IT do. They think that the 30k plus it IT all do the same thing.
If it is any comfort, Agile is a pop management culture joke everywhere.
Good for growing low-quality vegetables in a garden - with the rotating and all.
That's about it.
So it's a universal manure fad, you could say.
Call teams ‘app support’ but don’t give them the knowledge or tools to fully support and this is what you get. They not involve in any part of the development cycle until app get deploy to prod and then ‘support this’.